Solrouter

Integrations

Use Solrouter from Claude Code, Cursor, Claude Desktop, your own TypeScript code, and your Notion and GitHub accounts. Each page says what is sealed.

Solrouter reaches your tools three ways: anything that speaks MCP, your own code through the TypeScript SDK, and your workspace through Agent mode in the chat app.

IntegrationKindHowSealed
Claude CodeCoding agentMCP, one commandYes, for chat tools
CursorCoding agentMCP, ~/.cursor/mcp.jsonYes, for chat tools
Claude DesktopChat appMCP, claude_desktop_config.jsonYes, for chat tools
TypeScript SDKYour codenpm install @solrouter/sdkYes
NotionWorkspaceAgent mode connectorNo
GitHubCodeAgent mode connectorNo

What sealed means

Sealed means the prompt is encrypted on your machine to the enclave's key (X25519 per request plus Arcium RescueCipher) and opened only inside the Intel TDX enclave on Phala. Each sealed call writes a compressed receipt to Solana. The Notion and GitHub connectors need Agent mode's Extended tools switch, which runs on Solrouter's backend, outside the enclave. The MCP server's web and market lookups go from your machine to those services in plaintext. See What is private here.

Before you start

  1. Sign in at solrouter.com with email or a Solana wallet.
  2. Create an API key on the keys page. It starts with sk_solrouter_.
  3. Pick a plan, or add USDC balance. Calls made with an API key draw on the plan first, then the balance at $0.02 a call. See Pricing.

Pick one

On this page