Connect an MCP client

Both of Octo’s MCP servers speak Streamable HTTP and accept a workspace API key as a bearer token — the same key you’d use for the OpenAI-compatible API. See Get an API key if you don’t have one yet.

Server URLs

Server	URL	Tools your agent sees
Delegate to Octo (recommended)	https://api.omniocto.com/mcp	3
Full tool catalog	https://api.omniocto.com/mcp/tools	all of them

The short path is the simple one: point a client at /mcp and Octo picks its own tools, pausing for a human YES before anything that spends money. Reach for /mcp/tools only when your own loop should own the plan.

https://api.omniocto.com/mcp/octo is a permanent alias for /mcp — it was the delegate’s public name before the short path took it over.

Changed: /mcp used to serve the full catalog. A client still pointed there will not error — it will simply see 3 tools instead of the whole catalog. If that is you, switch to /mcp/tools.

Example client config

Most MCP clients accept a JSON config block naming the server, its URL, and headers. The exact file/format varies by client, but the shape is the same everywhere:

{
  "mcpServers": {
    "octo": {
      "url": "https://api.omniocto.com/mcp",
      "headers": {
        "Authorization": "Bearer sk-octo_..."
      }
    }
  }
}

The config above points at the recommended delegate surface. To reach the full tool catalog instead, point url at https://api.omniocto.com/mcp/tools and use the same Authorization: Bearer header.

OAuth clients

A workspace API key in the Authorization: Bearer header is the only way to authenticate against Octo’s MCP servers. There is no OAuth authorization server: the hosted API does not publish .well-known/oauth-protected-resource, .well-known/oauth-authorization-server, or .well-known/openid-configuration, and those discovery documents return 404.

Most MCP clients that support OAuth fall back to the bearer token you configure when discovery is unavailable, so the config block above is all you need. If your client insists on completing a discovery flow before it will connect, configure it with a static bearer token instead.

Verifying the connection

Once connected, ask your MCP client to list available tools. Against /mcp you should see exactly three tools — send_message, list_conversations, and get_conversation — for driving a conversation with Octo. Against /mcp/tools you should see Octo’s workspace tool catalog, filtered by your key’s role.

If the connection is rejected, double-check:

• The Authorization: Bearer header carries a valid, non-revoked key (see Get an API key).
• You’re pointed at the right path (/mcp vs /mcp/octo) for the tools you expect to see.