MCP server
MCP server
Streamable HTTP at /api/mcp, the route most agents take into a memory.
Mitosis runs a Model Context Protocol server at
https://mitosislabs.ai/api/mcp over Streamable HTTP. It is the primary
integration surface: Claude, ChatGPT, Cursor, Grok and any MCP-speaking client
connect to it directly.
Servers
| Server | URL | Auth |
|---|---|---|
| Product | https://mitosislabs.ai/api/mcp | OAuth 2.1 for memory tools; public tools open |
| Docs | https://mitosislabs.ai/api/mcp/docs | None |
| Backups | https://mitosislabs.ai/api/mcp/backups | Bearer token |
| Sandbox | https://dev.mitosislabs.ai/api/mcp | Same, scoped to the sandbox |
Auth
The server supports OAuth 2.1 with dynamic client registration, so a client
needs no pre-registered client_id. Point it at the URL and the user approves
access in a browser. Full detail in authentication.
Public tools answer before any sign-in, which makes them a good connectivity
check: if get_platform_status returns and cortex_ask prompts for auth, the
transport is fine and you simply have not authorized yet.
Discovery
The server card mirrors tools/list exactly, so you can inspect the tool surface
without connecting:
curl -s https://mitosislabs.ai/.well-known/mcp/server-card.json | jq '.tools[].name'
It is generated from the same modules the live server serves, so it cannot drift
from what the server actually offers. Each tool carries its annotations
(readOnlyHint, destructiveHint, idempotentHint, openWorldHint) and, for
the memory tools, the scope it requires.
Resources
Beyond tools, the server exposes the machine-readable documents as MCP resources:
llms-txt, llms-full-txt, pricing-md, auth-md, and openapi, plus a
read_doc resource for individual documentation pages.