Skip to main content
POST
Call an MCP tool

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
name
string
required

Tool name, as returned by GET /v1/mcp/tools.

arguments
object

Response

The tools/call result. A tool that ran and failed still answers 200: its result carries isError: true and the failure text in content, per the MCP specification.

data
object
required

The result of the equivalent JSON-RPC call.