Docs
    Guide

    MCP server setup

    Expose the Token API to LLM-based clients (Claude Desktop, Cursor, Cline, and any MCP-compatible app) so the model can call balances, transfers, prices, and DEX endpoints directly.

    What this enables

    • Conversational portfolio review across EVM, SVM, and TVM chains
    • Live token prices, liquidity, and OHLCV via natural language
    • Swap, transfer, and DEX activity lookups with citation back to chain data
    • Any MCP client driving the Token API as a tool, with no glue code

    Requirements

    • An MCP-compatible client — Claude Desktop, Cursor, Cline, or the Anthropic SDK.
    • Node 18+ on the host running the client (the bridge runs over stdio).
    • A Pinax JWT — issue one from /keys after signing in.
    • Roughly 5 minutes.

    Endpoint

    The MCP server is served over Streamable HTTP at:

    https://mcp.pinax.network

    The @pinax/mcp bridge client connects a stdio-based client (like Claude Desktop) to this remote server and attaches your JWT as a Authorization: Bearer header.

    Claude Desktop configuration

    Edit your claude_desktop_config.json — on macOS at ~/Library/Application Support/Claude/claude_desktop_config.json — and add the server:

    {
  "mcpServers": {
    "pinax": {
      "command": "npx",
      "args": [
        "@pinax/mcp",
        "--remote-url",
        "https://mcp.pinax.network",
        "--access-token",
        "YOUR_JWT_HERE"
      ]
    }
  }
}

    Restart Claude Desktop. The Token API tools appear in the tools menu once the bridge connects. Cursor and Cline use the same command — consult each client's MCP configuration docs for where to paste it.

    Example prompt patterns

    Wallet and portfolio
    • “Show me every token 0xabc... holds, grouped by chain, with USD values.”
    • “What were the largest inflows to this wallet in the last 30 days?”
    Trading analysis
    • “Plot daily OHLCV for the WETH/USDC pool on Uniswap V3 over the last 14 days.”
    • “Which DEXes routed the most volume on Base today?”

    Best practices & troubleshooting

    • MCP usage is billed identically to plain HTTP requests — every tool call resolves to one Token API request. Watch spend on /usage.
    • Tool calls cap at 10 seconds — break heavy multi-hop queries into smaller calls.
    • ENOENT: the client can't find node. Install Node 18+ and make sure it's on the PATH the desktop client launches with (or use an absolute path).
    • Server disconnected: usually a stale JWT or wrong URL. Re-issue your JWT from /keys and confirm the URL is exactly https://mcp.pinax.network.
    • Run the bridge with -v true to print verbose logs to stderr when diagnosing connection issues.

    Related