Connecting an MCP client

Every client below connects to the same URL, https://mitosislabs.ai/api/mcp, over Streamable HTTP, and authorizes through the same OAuth flow. Only the registration syntax differs.

Claude

claude mcp add --transport http mitosis https://mitosislabs.ai/api/mcp

Settings → Connectors → Add custom connector → paste the server URL.

Cursor and other config-file clients

{
  "mcpServers": {
    "mitosis": {
      "url": "https://mitosislabs.ai/api/mcp"
    }
  }
}

ChatGPT

Add it as a custom connector with the same URL. ChatGPT requires a server to expose search and fetch, which Mitosis does. See tool reference.

Local stdio bridge

If a client can only speak stdio, the SDK ships a bridge binary:

npx -y -p @mitosislabs/sdk@latest mi-cortex-mcp

It resolves a credential from MI_API_KEY, then MITOSIS_API_KEY.

After connecting

Confirm the surface is live before debugging anything deeper:

1. Call a public tool

   get_platform_status needs no auth. If it answers, transport is fine.

2. Call a memory tool

   cortex_manifest returns counts and source names. If it prompts for auth, complete the browser flow.

3. Ask a real question

   cortex_ask against something you know is in the graph.

Tool lists are cached

Clients cache tools/list. When a connector's tools change, a client may keep calling the old surface until the connector is removed and re-added. If a tool you know exists is invisible, re-add before investigating the server.