Call an MCP tool over HTTP
The Model Context Protocol endpoint. Send a JSON-RPC 2.0 request and receive a JSON-RPC response. Two protocol eras are served: a current-era request carries the protocol version claim in params._meta and is answered with a JSON body, while a 2025-era request is answered with the same JSON-RPC payload framed as server-sent events. The available tools, their inputs, their results, and their error codes are published in the x-aicd-mcp section of this document. Access requires a customer API key with the MCP scope; a signed-in browser session is not accepted.
Request
- Base URL: https://aicdapi.com
- URL: https://aicdapi.com/api/v1/mcp
- Auth: HTTP bearer
Headers
Required for a 2025-era request: it must list both application/json and text/event-stream, otherwise the request is refused with 406. A current-era request does not check this header.
Optional. When present it must name a supported revision. On a current-era request it selects the revision and must equal the version claimed in the body, and it must be sent whenever the body carries that claim. A mismatch is refused with 400.
Required for a current-era request: it must repeat the JSON-RPC method from the body. Absent or disagreeing values are refused with 400.
Required for a current-era tools/call: it must repeat the tool name from params.name. Absent or disagreeing values are refused with 400. Send none on tools/list.
Request body
Response
The JSON-RPC response. A current-era request receives it as a JSON body; a 2025-era request receives the same payload framed as server-sent events, one data: frame per message. A batch array of requests is accepted only on the 2025-era path.
Changes
No recorded changes to this operation across all 1 revision of this API.