/mcp.
When to use hosted
Authentication
Send the same credential as GraphQL:x-api-key: kz_live_… is equivalent. Clients that sign the user in (Claude.ai, ChatGPT) use OAuth instead of a pasted key: give them the MCP URL and they complete login and consent. A legacy x-app-token still works until 31 March 2027.
Optional: x-subdomain when your gateway routes workspaces by header.
Packs (tool subsets)
Prefer a pack so agents get a focused tool list:
List packs:
?pack=customer-support or header x-mcp-pack: customer-support on /mcp.
Transport
Hosted MCP is stateless Streamable HTTP (JSON responses). Official MCP clients still sendinitialize then tools/list / tools/call as separate POSTs — no sticky mcp-session-id is required across gateway pods.
Initialize example
List tools
Call a tool
Architecture pattern
Store tokens in a secrets manager; inject per tenant if you operate multi-tenant SaaS.Limits
- Same GraphQL permissions and rate behavior as direct API calls
- Hosted
/mcpPOSTs: default 120 req/min per credential (MCP_RATE_LIMIT_PER_MIN) - GraphQL fetch timeout: default 30s (
KARZOUN_MCP_FETCH_TIMEOUT_MS) - Default 512 KB tool response cap (configurable on self-hosted gateway mounts)
- See Security for rotation and scoping
Next steps
- AI app connectors — Claude, Manus, ChatGPT, Cursor remote
- Agent patterns — Hosted worker prompts
- How it works — Error and size limits
- Troubleshooting — Auth and connection errors