Skip to main content
GET
List MCP tools

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.

Response

The tools/list result

data
object
required

The result of the equivalent JSON-RPC call.