Skip to main content

Invoke a Model Context Protocol tool.

POST 
/v1/mcp

Lets an AI agent operate the gateway the way an operator would: inspect health, send a notification, query delivery state, list workspace templates and check subscriber channel eligibility.

tools/list enumerates the catalog with each tool's JSON Schema, and tools/call executes one by name. A body that is not valid JSON is a JSON-RPC -32700 parse error and a missing or non-string method is a -32600 invalid request, both carried in a 200 response as the protocol requires; unsupported methods and invalid parameters likewise return a JSON-RPC 2.0 error object. A missing or invalid API key still returns 401 before the handler runs.

Point an MCP-capable client at this endpoint with your API key as a bearer token. Every tool is confined to the workspace that owns the key.

Request​

Responses​

Tool result, or a JSON-RPC 2.0 error object