POST /v1/sites/{siteId}/ide-mcp

Ìfàṣẹ́pọ̀

Ojú-wọ̀n yìí jẹ́ ti gbogbo ènìyàn. Kò gba àmì ìdánimọ̀ kankan tàbí àgbájọ kankan — ohun tí ojú-wọ̀n ìpolówó wa àti àwọn ẹ̀rọ ìdáhùn AI ǹkà kọ́ ni.

Ojú abánisọ̀rọ̀ yìí kò gba id ajọ kankan. Kọ́kọ́rọ́ rẹ ti mọ ajọ ti o jẹ ti e, a o si fèsì nipa rẹ̀.

Gbiyanju rẹ

Rọ́pọ̀ èyíkéyìí nínú àwọn àmì ìtọ́ka < > pẹ̀lú iye tirẹ̀, àti àmì ìdánimọ̀ bọ́tìnnì náà pẹ̀lú bọ́tìnnì kan láti inú dásibọ̀ọ̀dù rẹ.

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

Ṣé o ti wọlé? Iwọ̀n api ní nú ìgbékalẹ̀ rẹ kún id àjọ gidi rẹ ati bọtini tirẹ, o si nṣiṣẹ ibeere na lòdì si api gidi ki o le rii esi gidi na. Ṣí ojú abáná yìí sílẹ̀ nínú kọnsólù API

Àwọn kúlẹ̀kúlẹ̀

A JSON-RPC 2.0 MCP endpoint — the same server, registry, write gate, confirmation guard, audit trail and spend caps as /v1/mcp, reached through a different door. What differs is only the credential: this one accepts the editor's own signed grant, so the editor can be shipped with our MCP server already connected without a customer's hosting jail ever holding an McpConnection token. The editor's own MCP client is seeded to point at the session gate on the hosting box; the gate attaches the grant and relays here. One request, one response — a notification (no id) answers 202 with no body, and a JSON array is accepted as a batch. Deliberately narrower than a connection a customer mints themselves. An MCP token can never out-scope the human who created it, and an editor grant carries that person's name rather than their permissions — so this connection is scoped to what the editor already is: the customer's sites, their control panels and their cache. Opening an editor is not a privilege escalation.

Àwọn ìpìlẹ̀

Akoonu ibeere naa

Idahun

Awọn aṣiṣe ti ibudo ipari yii le da pada

404 · 422