Search an Octri project's API docs and call its endpoints as tools, shaped by its SDK Studio config.
The publisher's own command. Not a PlugMCP endpoint.
npx -y @octri/[email protected]
OCTRI_PROJECT_ID=<value> OCTRI_API_BASE_URL=<value> OCTRI_API_TOKEN=<secret> OCTRI_API_KEY=<secret> OCTRI_API_KEY_HEADER=<value> OCTRI_API_USERNAME=<value> OCTRI_API_PASSWORD=<secret> claude mcp add dev.octri-mcp -- npx -y @octri/[email protected]
Run in a terminal.
{
"mcpServers": {
"dev.octri-mcp": {
"command": "npx",
"args": [
"-y",
"@octri/[email protected]"
],
"env": {
"OCTRI_PROJECT_ID": "<value>",
"OCTRI_API_BASE_URL": "<value>",
"OCTRI_API_TOKEN": "<secret>",
"OCTRI_API_KEY": "<secret>",
"OCTRI_API_KEY_HEADER": "<value>",
"OCTRI_API_USERNAME": "<value>",
"OCTRI_API_PASSWORD": "<secret>"
}
}
}
}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchSearch an Octri project's API docs and call its endpoints as tools, shaped by its SDK Studio config.
README is not crawled yet. Open the repository
No tool list yet. Remote servers get one after the first health check.