MCP Server
Overview
The Octri MCP server connects your API to Claude, Cursor, and any MCP-compatible assistant. The agent reads your documentation as live context instead of guessing from memory, and it can call your API directly.
Seven tools for searching, reading, and navigating your documentation.
One executable tool per endpoint, shaped by your SDK Studio config.
Why it matters
An agent asked to integrate your API without MCP does one of two things: recites an API it saw during training, or guesses from the name. Both produce code that looks right and doesn't run.
With MCP, the agent reads your actual endpoints, your actual parameters, and your actual guides, at the version you published.
What ships
The server is @octri/mcp and runs through npx, so there's nothing to install ahead of time. You need your project id.
- Install
Add it to your MCP client's config. See Install.
- Docs tools work immediately
Search, read, and navigate. Published content only.
- Add credentials for operation tools
Only if you want the agent to call your API. See Configuration.
Two kinds of tool
| Documentation tools | Operation tools | |
|---|---|---|
| What they do | Read your docs | Call your API |
| Need credentials | No | Yes |
| Side effects | None | Real |
| Derived from | Published pages | Your SDK Studio config |
They are not previews. A tool call hits your live API with the credentials you configure, and a write endpoint will write. Point them at staging while you're evaluating. See Operation tools.