mcp

POST `/v1/mcp`

The MCP JSON-RPC 2.0 protocol endpoint.

Authentication

Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/mcp \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "jsonrpc": <string<2.0>>, "method": <string> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

The Model Context Protocol endpoint (`initialize`, `tools/list`, `tools/call`, `resources/list`, `resources/read`, `ping`). Authenticated **only** by a `zmcp_…` connection token (`Authorization: Bearer zmcp_…`); a missing/invalid token returns `401` with a `WWW-Authenticate` challenge pointing at the resource-metadata document. Each call runs under the connecting org's RLS scope and is gated by the connection's RBAC scopes; a batch (JSON array) is accepted.

Request body

Name	Type	Required	What it is
`jsonrpc`	`string<2.0>`	Yes	—
`id`	`string \| integer`	No	Request id (string or number); omit for a notification.
`method`	`string`	Yes	—
`params`	`object`	No	—

Response

Name	Type	Required	What it is
`jsonrpc`	`string<2.0>`	Yes	—
`id`	`string \| integer \| null`	Yes	—
`result`	`object`	No	—
`error`	`object`	No	—

Errors this endpoint can return

401 · 429

POST /v1/mcp