MCP over GET (not supported)
MCP here is request/response over POST. There is no SSE transport on this endpoint.
Authorization
bearerAuth Authorization for API
In: header
Path Parameters
Your app's unique id. Find it in the console under the app's Settings, or in the URL of any app page.
uuidResponse Body
application/json
curl -X GET "https://example.com/497f6eca-6276-4993-bfeb-53cbbbba6f08/mcp"{ "error": { "error": "That method is not allowed on this path.", "code": null, "requestId": "3f9a1c7e-2b54-4d8a-9f10-6c2e7b5a4d31" }, "requestId": "3f9a1c7e-2b54-4d8a-9f10-6c2e7b5a4d31"}MCP endpoint
A native Model Context Protocol server for this app. Point any MCP client at this URL with your api key as the bearer token and the agent's permitted surface appears as tools. One key is one server, scoped to that key's agent. There is no separate MCP configuration: the tools are the same policy-derived surface `GET /agent/tools` returns, over the same execution core, with the same halt on high-risk steps. Supported methods include `initialize`, `tools/list`, and `tools/call`.
Error codes
Every stable error code the API can return, and what each one means.