POST /v1/mcp

Authentication

This endpoint does not take an API key. It takes its own credential, issued to the plugin or service that calls it, as a bearer token; see the description above.

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. The tool catalogue is additionally filtered by the connecting org's role (customer, reseller's client, agency, reseller, staff), in tools/list and tools/call alike — a role-hidden tool answers unknown tool, never forbidden. An entitlement refusal (a full plan, a feature not on the tier) is returned as a tool result carrying a structured upgrade offer, never as a JSON-RPC error.

Request body

Response

Errors this endpoint can return

401 · 429