hosting

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

The platform MCP server, reached from inside the site's web editor.

身份验证

此端点是公开的。它不需要任何凭据或组织——这是我们自己的营销网站和 AI 问答引擎所读取的内容。

此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。

免费试用

将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。

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

已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。在 API 控制台中打开此端点

详细信息

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.

参数

名称	类型	必填	内容简介
`siteId (path)`	`Uuid`	是	Site ID (UUIDv7).

请求正文

名称	类型	必填	内容简介
`jsonrpc`	`string<2.0>`	是	—
`id`	`string \| integer`	否	Request id (string or number); omit for a notification.
`method`	`string`	是	—
`params`	`object`	否	—

响应

名称	类型	必填	内容简介
`jsonrpc`	`string<2.0>`	是	—
`id`	`string \| integer \| null`	是	—
`result`	`object`	否	—
`error`	`object`	否	—

此端点可能返回的错误

404 · 422

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