Mcp Memory Rpc

POST /mcp/memory

The memory door (D-5304): the same transport over the five-tool subset.

Its own route because it is its own audience: a token minted for this resource is refused at /mcp and vice versa, which is what lets the memory product be granted, promoted and revoked as a thing of its own. The credential rules are identical — a service key opens both doors, bounded by the subset each one publishes.

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/memory