mcp

POST `/v1/mcp`

The MCP JSON-RPC 2.0 protocol endpoint.

Tabbatar da Asali

Aiko da maɓallin API a matsayin bearer token. Wannan ma'anar ba ta bayyana takamaiman izini ba a cikin ƙayyadaddun bayanai, don haka ba wa maɓallin ku mafi ƙarancin abin da yake buƙata kuma ku bincika amsar maimakon yin zato.

Wannan wurin ƙarewa ba ya buƙatar ID na ƙungiya. Maɓallin ku ya riga ya gano ƙungiyar da yake ciki, kuma an iyakance amsa a kanta.

Gwada

May gurbin komai da ke cikin kusurwa da ƙimar ka, kuma may gurbin maballi da maballi daga allon sarrafa ka.

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> }'

An shiga? Na'urar sarrafa API da ke cikin sashin kulawarka tana cika ainihin lambar ƙungiyarka da maɓallinka naka, sannan tana gudanar da buƙatar a kan ainihin API don haka zaka iya ganin amsar gaske. Buɗe wannan tashar a cikin na'urar kula da API

Bayani

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.

Jikin buƙata

Suna	Nau'i	Ana buƙata	Abin da yake
`jsonrpc`	`string<2.0>`	Eh	—
`id`	`string \| integer`	A'a	Request id (string or number); omit for a notification.
`method`	`string`	Eh	—
`params`	`object`	A'a	—

Martani

Suna	Nau'i	Ana buƙata	Abin da yake
`jsonrpc`	`string<2.0>`	Eh	—
`id`	`string \| integer \| null`	Eh	—
`result`	`object`	A'a	—
`error`	`object`	A'a	—

Kuskuren da wannan matsaya za ta iya maido wa

401 · 429

POST /v1/mcp