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

Autentifikacija

Ova je krajnja točka javna. Ne zahtijeva nikakve vjerodajnice ni organizaciju – to je ono što čitaju naše vlastite marketinške stranice i AI strojevi za odgovore.

Ova krajnja točka ne prihvaća ID organizacije. Vaš ključ već identificira organizaciju kojoj pripada, a odgovor je ograničen na nju.

Isprobajte

Zamijenite sve unutar šiljastih zagrada svojim vlastitim vrijednostima, a rezervirano mjesto za ključ s ključem iz vaše nadzorne ploče.

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

Prijavljeni ste? API konzola na vašoj nadzornoj ploči automatski unosi stvarni ID vaše organizacije i vaš vlastiti ključ te šalje zahtjev prema aktivnom API-ju kako biste mogli vidjeti stvarni odgovor. Otvori ovu krajnju točku u API konzoli

Pojedinosti

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.

Parametri

Tijelo zahtjeva

Odgovor

Pogreške koje ova krajnja točka može vratiti

404 · 422