Connect to Thirdfy MCP

Thirdfy MCP is a managed Cloudflare Workers endpoint. You connect your agent host to it and call tools directly. There is no public open-source MCP repository to clone or self-host.

Production endpoint

Use GET /health and GET /tools as smoke checks after you add the connector. The live manifest is the source of truth for tool names on the shipping endpoint.

HTTP surfaces

Claude Managed Agents

1. Open Claude Console and add an MCP connector (streamable HTTP).
2. Set the URL to https://mcp.thirdfy.com/mcp.
3. Complete onboarding with bootstrap or agent_api_key per Authentication.
4. Start with getActionsCatalog and getProviderActions before any write.

See also Claude Managed Agents.

Cursor and OpenClaw

Add Thirdfy MCP to your host MCP config with streamable HTTP transport pointing at https://mcp.thirdfy.com/mcp.

Example Cursor mcp.json entry:

{
  "mcpServers": {
    "thirdfy": {
      "url": "https://mcp.thirdfy.com/mcp"
    }
  }
}

Pass agentApiKey on credentialed tools. For hosted runtimes, optional executionContext (runtimeId, orgId) on walletExecute, executeIntent, and agentRun attributes credits to the correct runtime.

Prefer getProviderActions (not the legacy getTradingProviderActions alias) for venue discovery.

Direct tool calls (no MCP host)

Agents and scripts can call tools over HTTP without an MCP session:

curl -s https://mcp.thirdfy.com/health
curl -s https://mcp.thirdfy.com/tools

curl -s -X POST https://mcp.thirdfy.com/tool/getActionsCatalog \
  -H "Content-Type: application/json" \
  -d '{}'

curl -s -X POST https://mcp.thirdfy.com/tool/getProviderActions \
  -H "Content-Type: application/json" \
  -d '{"provider":"hyperliquid","view":"concise"}'

Credentialed writes pass the agent key in the JSON body and/or Authorization: Bearer <agent-api-key>:

curl -s -X POST https://mcp.thirdfy.com/tool/executeIntent \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer agent-..." \
  -d '{"agentApiKey":"agent-...","action":"preflight","chainId":8453}'

Full tool list and auth profiles: Tools reference.

Recommended first session

GET /tools
  → describeOnboardingPath
  → startEmailOnboarding / completeEmailOnboarding (bootstraps agent API key)
  → getWalletProfile / agentWalletBootstrap
  → getActionsCatalog
  → getProviderActions
  → preflight or walletExecute

Optional later: agentRegister (directory profile) or Creator Platform (web UI).

Chapter guides: Discovery · Onboarding · Execution

Security reminder

MCP is a public edge surface, not a trust boundary. Never paste operator or full platform API keys into agent prompts. Use agent_api_key or bootstrap tokens scoped to your agent. See Authentication.

Related

• Discovery tools
• Execution sequence
• Agent CLI install for shell parity