Mcp Rpc

POST /mcp

One JSON-RPC message, or a batch of them.

Always 200 for anything the credential permits — including a tool that refused. JSON-RPC carries its own error channel, and a client that has to read both an HTTP status and an RPC error will read one of them wrongly. The exceptions are the two conditions that are not about a message at all: an unusable credential (401) and a body that is not JSON (400, with a JSON-RPC parse error inside it so a strict client still sees a valid frame).

No credential

This operation is public: it authenticates by its own mechanism — a webhook signature or a channel token — rather than by a platform credential.

Responses

Status	Description	Body
200	Successful Response	—

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

curl -X POST https://your-deployment.example.com/mcp