Sign in

v4

latestOpenAPI 3.0.02026-07-316584128.0 KB
MCP

Send an MCP message

Handle a single JSON-RPC 2.0 message from an MCP client, per the MCP Streamable HTTP transport.

The server is stateless: every request is self-contained and carries the caller's credential, so there is no session to establish or resume. GET and DELETE on this path return 405 Method Not Allowed.

Requests (messages with an id) are answered with the JSON-RPC response, either as application/json or as a text/event-stream carrying the response and any notifications emitted while it runs. Requests must accept both. Notifications and responses (messages without an id) are answered with 202 Accepted and an empty body.

post/mcp

Headers

Acceptstring required

Must list both application/json and text/event-stream.

MCP-Protocol-Versionstring
Example:2025-06-18

Protocol revision negotiated during initialize, echoed on every subsequent request. Omitted on the initialize request itself.

Request body

jsonrpc'2.0' required

JSON-RPC protocol version. Always 2.0.

methodstring required

MCP method, such as initialize, tools/list, or tools/call.

paramsobject

Method parameters as defined by the MCP specification.

Response

JSON-RPC response to the request

jsonrpc'2.0' required

JSON-RPC protocol version. Always 2.0.

resultobject

Method result as defined by the MCP specification.