Skip to content

Developers

The MCP connector

One endpoint for agents and model clients that speak MCP: free, read-only tools over the same key.

What it offers

  • POST /v1/mcp offers 17 free, read-only operations as tools over JSON-RPC 2.0. It takes the read scope and cannot spend, write or delete. Batched requests are refused.
  • Each tool calls the same handler as the route it names and returns that route’s own answer.
  • Give an agent a key with read and not spend: the connector needs only read, and such a key is refused on every route that spends or writes.
MethodPathScopeWhat it does
POST/v1/mcpreadThe MCP connector — call the free, read-only operations here as tools. callMcp

Try it

# Every tool, with its input schema.
curl -s -X POST "$BASE/v1/mcp" \
  -H "Authorization: Bearer $PT_KEY" -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

# One tool, called.
curl -s -X POST "$BASE/v1/mcp" \
  -H "Authorization: Bearer $PT_KEY" -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"whoami","arguments":{}}}'

Tools on this surface

2 of 17 tools
ToolRouteWhat it does
whoamiGET /v1/meWhat this key is, and what is left of its day.
list_case_modelsGET /v1/modelsEvery model this key can call — yours, helm-default, the case tasks.

15 more tools read the research, jobs, walkthroughs and cases routes, which these pages leave out; Developer, inside the app, lists every tool.

Next