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.

Docs as context

Seven tools for searching, reading, and navigating your documentation.

Your API as tools

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

Octri hosts every project's server at one URL, so an assistant connects with nothing to install:

https://api.octri.dev/api/v1/public/mcp/YOUR_PROJECT_ID/mcp

The same tools also run on your own machine as @octri/mcp through npx, or on your own infrastructure through Docker or Cloudflare Workers. Each publish in MCP Studio updates all of them.

With a custom domain, the server gets an address of your own. Octri's own API is served this way at https://mcp.octri.dev/mcp: see AI assistants to connect it and try a published server for yourself.

Connect

Add the URL or the npx command to your MCP client. See Install.
Docs tools work immediately

Search, read, and navigate. Published content only.
Sign in for operation tools

Only if you want the agent to call your API. People sign in through OAuth or a key page on the hosted server, or set a credential locally. See Hosted server and sign-in.

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

Operation tools make real API calls

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.

Everything else in MCP Studio

From the CLI

Scoring, testing, hosting and packaging all work from a terminal. See MCP commands.

Hosted server and sign-in

OAuth, team installations, your own domain.

Permissions and limits

Approvals, tool groups, safety limits, the audit log.

Search and code mode

Large APIs in a small context.

Quality and test runs

Check the tools before an agent sees them.

Install

Claude Code, Claude Desktop, Cursor, VS Code.

Troubleshooting

When a tool doesn't show up.