MCP Server

​

What is the Compass MCP server?

https://api.compasslabs.ai/mcp

​

Connect a client

claude mcp add --transport http compass https://api.compasslabs.ai/mcp \
  --header "X-API-Key: YOUR_API_KEY"

{
  "mcpServers": {
    "compass": {
      "url": "https://api.compasslabs.ai/mcp",
      "headers": { "X-API-Key": "YOUR_API_KEY" }
    }
  }
}

{
  "mcpServers": {
    "compass": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://api.compasslabs.ai/mcp",
        "--header", "X-API-Key:${COMPASS_API_KEY}"
      ],
      "env": { "COMPASS_API_KEY": "YOUR_API_KEY" }
    }
  }
}

curl -X POST https://api.compasslabs.ai/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-API-Key: YOUR_API_KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

​

What you get

​

The non-custodial flow

1. Read — markets, positions, and balances tools return data directly.
2. Account — Earn, Credit, and Tokenized Equities act through a per-owner product account: call that product’s *_create_account tool first. It is idempotent and returns transaction: null if the account already exists.
3. Build — action tools return an unsigned transaction {to, data, value, ...}.
4. Sign & broadcast — with your own key, for example with Foundry’s cast:
   cast send <to> <data> --value <value> --rpc-url $RPC_URL --account my-keystore
   

• Global Markets perps (Hyperliquid): build the order with v2_global_markets_perps_market_order (or limit_order, withdraw, …) → sign the returned typed data → submit via v2_global_markets_perps_execute. Fund first with v2_global_markets_perps_deposit; perps need no product account.
• Tokenized Assets: v2_tokenized_assets_order → sign → v2_tokenized_assets_order_submit. RWA yield assets (e.g. mTBILL) can also be bought or sold directly with v2_tokenized_assets_transact_buy/_sell, which return a regular unsigned transaction.
• Gas sponsorship: call an action with gas_sponsorship: true → sign the returned EIP-712 → submit signature and typed data to v2_gas_sponsorship_prepare → a sponsor broadcasts, and the owner pays no gas. See Gas Sponsorship.
• On-ramp (browser handoff): a fiat card + KYC flow can only render in a browser, so an agent cannot complete it inline. Call v2_onramp_create → present the returned checkout_url and user_instructions to the user so they can pay by card → then poll v2_onramp_status (with the payment_id) until delivered. USDC lands in the user’s own wallet (non-custodial); continue with the tokenized buy. See On-Ramp.

​

Good to know

• Amounts are decimal token units ("1.5" means 1.5 USDC), never wei. "ALL" is not supported — pass an explicit amount.
• Tokens go by symbol (USDC, WETH) or 0x address; pass the address when a symbol isn’t recognized.
• Chains vary by product: Earn and Credit cover Ethereum, Base, Arbitrum, HyperEVM, and Tempo; CCTP bridges Ethereum, Arbitrum, and Base; Tokenized Assets settle on Ethereum (RWA buy/sell swaps also on Base); perps run on Hyperliquid.
• The server is stateless: every request is self-contained — no sessions to manage, and a 5xx is safe to retry once.
• Errors: 4xx bodies are actionable (for example Unknown token symbol) — surface them as-is. A 401 means the X-API-Key header is missing or invalid.