MCP server

Chirpy's MCP server gives AI apps every action in this documentation as a tool.

Address	`https://mcp.chirpy.me/mcp`
Transport	Streamable HTTP. One JSON-RPC message per POST, answered with one JSON object.
Protocol versions	`2026-07-28` (stateless, per-request metadata), and `2025-11-25`, `2025-06-18`, `2025-03-26` (initialize handshake)
Sessions	None. Every request stands alone. `GET` and `DELETE` answer 405.
Methods	`initialize` (earlier versions), `server/discover` (2026-07-28), `tools/list`, `tools/call`, `ping`
Sign-in	OAuth, or an API key as a Bearer token. See Sign-in and API keys.

Tools

Each tool is one action, with the same name and inputs. tools/list returns only the tools your access level allows. Every tool has a title and the hints readOnlyHint, destructiveHint, idempotentHint and openWorldHint, so apps can ask before anything that publishes.

Every tool also takes an optional brandKitId (from list_brand_kits) to work with a Brand Kit other than your default.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "create_drafts",
    "arguments": {
      "posts": [
        {
          "content": "Weekend special: two coffees for the price of one.",
          "platforms": [
            "instagram"
          ]
        }
      ]
    }
  }
}

When something goes wrong

Problems the app can fix (a missing input, a daily limit, too few AI credits) come back as a tool result with isError: true and a plain explanation.
No or expired sign-in: HTTP 401. Not allowed on your plan, or a lower access level: 403. Too many requests a minute: 429 with Retry-After.