Skip to content
OpenPlate

JSON-RPC 2.0 over HTTP POSTAgent tools

Six typed tools on one endpoint: two read tools, an analysis tool that runs the same engine the page runs, and two mutating tools that go through the same service layer the buttons use. Mutations are idempotent when given a key, and every call is scoped to this browser's anonymous session.

One click, real request

Endpoint

https://openplate-sigma.vercel.app/api/mcp

No plates in this session yet. Run file_plate to create one through the agent path.

Request
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "initialize",
  "params": {
    "protocolVersion": "2024-11-05",
    "capabilities": {},
    "clientInfo": {
      "name": "openplate-console",
      "version": "1.0.0"
    }
  }
}
Response
Send a request to see the raw JSON-RPC response.

Chain seals are 0000000000…000000-length SHA-384 digests over the canonical JSON of each event. Point any MCP client at the endpoint above, or read /mcp.json.

What the mutating tools actually wroteRecent agent-visible plates

No plates in this session yet

Run file_plate in the console above. It creates a real row and a real genesis event, and the response links straight to it.

Wiring a client up

{
  "mcpServers": {
    "openplate": {
      "type": "http",
      "url": "https://openplate-sigma.vercel.app/api/mcp"
    }
  }
}

This deployment serves the console at https://openplate-sigma.vercel.app. The live host is published in /mcp.json with the production endpoint already filled in. That manifest is generated at request time from the same configuration this page and the footer use, so it cannot name the wrong host.