Skip to main content
This page is the HTTP reference. If you are connecting Claude.ai, ChatGPT, Manus, or remote Cursor, start with Cloud apps. Stay here when your own server calls /mcp.
Never call /mcp from browser JavaScript. The API key would be exposed to end users. Use your backend or a trusted worker.

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:
You can also pass ?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 send initialize 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 /mcp POSTs: 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

Last modified on August 8, 2026