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

Uthibitishaji

Kituo hiki cha mwisho ni cha umma. Hakichukui kitambulisho wala shirika — ni kile ambacho tovuti yetu ya masoko na injini za majibu za AI zinasoma.

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/sites/{siteId}/ide-mcp \
  -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

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.

Vigezo

Mwili wa ombi

Majibu

Hitilafu ambazo mwisho huu unaweza kurudisha

404 · 422