Call the MCP server
POST/mcp
Streamable HTTP transport for the Model Context Protocol, in stateless mode: one JSON-RPC 2.0 request in, one response out. There is no session id and no SSE stream, so any request can be served by any worker.
The account is never in the URL — it is resolved from the API key — so an
external AI client only ever configures this single endpoint. The server has to
be enabled for the account (mcp_server feature) and the key has to belong to
a user who is still a member of it.
Implemented methods: initialize, ping, tools/list and tools/call.
Protocol versions accepted: 2025-06-18, 2025-03-26 and 2024-11-05.
Request
Responses
- 200
- 202
- 401
JSON-RPC response. A protocol failure lands here too, carrying error
instead of result — that is what JSON-RPC asks for.
Notification accepted. No body.
Missing, unknown or no longer valid API key.