mcp

POST /v1/mcp

The MCP JSON-RPC 2.0 protocol endpoint.

Vituo vyote vya mcp

Uthibitishaji

Tuma ufunguo wa API kama tokeni ya kubeba. Sehemu hii ya mwisho haitaji ruhusa maalum katika maelezo, kwa hivyo ipe ufunguo wako kiwango cha chini kabisa kinachohitajika na uangalie jibu badala ya kukisia.

Endpoint hii haichukui kitambulisho cha shirika. Ufunguo wako tayari unalitambua shirika linalohusika, na jibu limewekewa kikomo kwa shirika hilo pekee.

Jaribu

Badilisha chochote kilicho ndani ya mabano ya pembe na maadili yako mwenyewe, na kishikiliaji cha ufunguo na ufunguo kutoka kwa dashibodi yako.

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

Umeingia kwenye akaunti? Dashibodi yako ya kiweko cha API inajaza kitambulisho chako halisi cha shirika na ufunguo wako mwenyewe, na kuendesha ombi dhidi ya API ya moja kwa moja ili uweze kuona jibu halisi. Fungua sehemu hii ya mwisho (endpoint) kwenye konsole ya API

Maelezo

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.

Mwili wa ombi

JinaAinaInayohitajikaKilicho hiki
jsonrpcstring<2.0>Ndiyo
idstring | integerHapanaRequest id (string or number); omit for a notification.
methodstringNdiyo
paramsobjectHapana

Majibu

JinaAinaInayohitajikaKilicho hiki
jsonrpcstring<2.0>Ndiyo
idstring | integer | nullNdiyo
resultobjectHapana
errorobjectHapana

Hitilafu ambazo mwisho huu unaweza kurudisha

401 · 429