mcp

POST `/v1/mcp`

The MCP JSON-RPC 2.0 protocol endpoint.

Autentifikatsiya

API kalitini bearer token sifatida yuboring. Ushbu yakuniy nuqta spetsifikatsiyada ma'lum bir ruxsatni ko'rsatmaydi, shuning uchun kalitingizga eng kam kerakli huquqni bering va taxmin qilish o'rniga javobni tekshiring.

Bu yakuniy nuqta hech qanday tashkilot identifikatorini qabul qilmaydi. Sizning kalitingiz unga tegishli tashkilotni allaqachon aniqlaydi va javob shunga qarab cheklanadi.

Sinab ko'rish

Qavslardagi har qanday narsani o'z qiymatlaringiz bilan, kalit pleysxolderini эsa boshqaruv panelingizdagi kalit bilan almashtiring.

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

Tizimga kirganmisiz? Boshqaruv panelingizdagi API konsoli haqiqiy tashkilot ID raqamingiz va shaxsiy kalitingizni avtomatik to'ldiradi hamda haqiqiy javobni ko'rishingiz uchun so'rovni jonli API orqali bajaradi. Ushbu yakuniy nuqtani API konsolida oching

Tafsilotlar

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.

Soʻrov tanasi

Nomi	Turi	Majburiy	Nima bu
`jsonrpc`	`string<2.0>`	Ha	—
`id`	`string \| integer`	Yo'q	Request id (string or number); omit for a notification.
`method`	`string`	Ha	—
`params`	`object`	Yo'q	—

Javob

Nomi	Turi	Majburiy	Nima bu
`jsonrpc`	`string<2.0>`	Ha	—
`id`	`string \| integer \| null`	Ha	—
`result`	`object`	Yo'q	—
`error`	`object`	Yo'q	—

Ushbu yakuniy nuqta qaytarishi mumkin bo'lgan xatolar

401 · 429

POST /v1/mcp