Skip to main content
POST
Send an MCP JSON-RPC message

Authorizations

Authorization
string
header
required

MCP credentials, distinct from v1 API keys. Either an MCP connection key (mcp_sk_..., created from the customer dashboard) or an OAuth 2.1 access token carrying the mcp:use scope. Credentials are never accepted in the query string. A refused request answers 401 with a WWW-Authenticate header naming the protected resource metadata, so OAuth-capable clients can discover the authorization server.

Body

application/json
jsonrpc
enum<string>
required
Available options:
2.0
method
string
required

Requests: initialize, ping, tools/list, tools/call, resources/list, resources/read, prompts/list; any other method with an id answers JSON-RPC -32601. Notifications (no id), such as notifications/initialized, are accepted whatever their method.

Example:

"tools/list"

id

Omit to send a notification, which is acknowledged with 202 and no body.

params
object

Response

JSON-RPC response

jsonrpc
enum<string>
required
Available options:
2.0
id
required
result
any
required

Method-specific result, as defined by the MCP specification.