The Model Context Protocol server: tools/list, tools/call, tools/call_batch and resources/read over JSON-RPC 2.0. Requires a workspace API key as a Bearer token. The available tools and their own typed schemas are discovered at runtime via tools/list, not enumerated here — see the MCP manifest for how a client finds this endpoint and what auth it needs before making its first call. Every key carries a scope (see the apiKey security scheme's x-scopes): workspace keys reach the full tool surface for one workspace; provisioning keys are operator-only and can call nothing except internal demo provisioning. Batching: tools/call_batch executes several tool calls in one HTTP round trip and returns their results as one JSON-RPC response — the batch/bulk pattern for this API, in JSON-RPC rather than a separate REST endpoint.

Pagination: list-shaped tools page with an opaque cursor — pass a previous result's next_cursor back as the cursor argument while has_more is true (see the CursorPage schema). The cursor is server-owned: its bytes mean nothing to the caller and may change shape between versions of the contract without notice.