Public MCP documentation

Transport

Mode

Streamable HTTP in JSON-response mode:

  1. Client POSTs JSON-RPC 2.0 (Content-Type: application/json)
  2. Server responds with JSON-RPC result/error (or a batch array)
  3. No long-lived server→client SSE session

Shared protocol core: mcp-protocol.ts (web app + bot-service).

HTTP methods

MethodResult
POSTJSON-RPC handling
GET405MCP endpoint — POST JSON-RPC only
Other405

Notifications → 202

Notification-only POSTs (no JSON-RPC id, typically notifications/*) return:

  • HTTP 202
  • Empty body

Methods

MethodResponse
initializeprotocolVersion, capabilities.tools, serverInfo
ping{}
tools/list{ tools: [...] }
tools/callMCP tool result content blocks
notifications/*No JSON-RPC body; HTTP 202 when alone

Protocol version: `2025-06-18`.