AI assistants

You can manage your Octri account from an AI assistant such as Claude, Cursor or VS Code: list your projects, push a spec, start an SDK build, read what changed. There are two ways to connect one, and they suit different jobs.

	Octri's hosted server	The CLI's server
Address	`https://mcp.octri.dev/mcp`	`octri mcp serve`, run on your machine
Install	Nothing	The Octri CLI
Sign-in	In your browser, the first time	Your CLI profile
Covers	Projects, specs, SDK builds, docs pages and the changelog	Your whole account, including docs settings, MCP and monitoring

Both are separate from the MCP server you publish for your own API, which is what the MCP Studio tab covers. In fact Octri's hosted server is one of those: Octri's own public API, published the same way you'd publish yours.

Octri's hosted server

Connect a client to this address:

https://mcp.octri.dev/mcp

The first time it connects, your client opens a browser page from Octri to sign in. After that it calls the Octri API for you.

Claude Code

claude mcp add --transport http octri https://mcp.octri.dev/mcp

Cursor

In .cursor/mcp.json:

{
  "mcpServers": {
    "octri": { "url": "https://mcp.octri.dev/mcp" }
  }
}

VS Code

In .vscode/mcp.json:

{
  "servers": {
    "octri": { "type": "http", "url": "https://mcp.octri.dev/mcp" }
  }
}

Claude Desktop

Open Settings, then Connectors, choose Add custom connector and paste the address.

Without signing in

A client that can send headers can pass an Octri API key instead, on every request. Octri doesn't store it:

claude mcp add --transport http octri https://mcp.octri.dev/mcp --header "x-octri-api-key: ifk_YOUR_KEY"

This suits a script or CI job. Give it a key made for that job, so you can revoke it on its own.

What it can do

Its tools are the Octri API's operations:

Area	Tools
Projects	`listProjects`, `getProject`, `createProject`, `updateProject`
Specs	`listSpecs`, `getSpecStatus`, `getCurrentSpecDocument`, `createSpecFromUrl`, `createSpecFromContent`
SDK builds	`listSdkBuilds`, `listSdkBuildArtifacts`, `triggerSdkBuild`, `retrySdkBuild`, `publishSdkBuild`
Docs	`listDocPages`, `getDocPage`, `listChangelogEntries`, `getChangelogEntry`

The tools that read run on their own. Every tool that creates, changes, builds or publishes asks you to approve each call, and a client that can't ask gets a refusal rather than an unapproved call. You can ask the assistant things like "push this spec to my Payments project and build the TypeScript SDK".

The CLI's server

octri mcp serve runs the CLI as an MCP server on your machine, so it can do everything the CLI does, for the profile you signed in with. Tools that publish or delete stay off until you turn them on with a flag. See octri mcp serve for its tools and setup.

{
  "mcpServers": {
    "octri": { "command": "octri", "args": ["mcp", "serve"] }
  }
}

Which to use

The hosted server when you want nothing to install, or an assistant that runs in the browser or on another machine.
The CLI's server when you need more than projects, specs and builds: docs settings, your MCP server's own settings, monitoring and incidents.

API keys: keys for Octri, and how to revoke one.
octri mcp serve: the CLI's server in full.
MCP Studio: publishing a server for your own API.