CCXT MCP Server

Add to your client

Copy the config for your MCP client and paste it into its config file.

{
  "mcpServers": {
    "ccxt-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@mcpfun/mcp-server-ccxt"
      ],
      "env": {
        "BINANCE_SECRET": "<your-binance-secret>",
        "BINANCE_API_KEY": "<your-binance-api-key>",
        "DEFAULT_EXCHANGE": "binance"
      }
    }
  }
}

Before you start

• Node.js (install via npm/npx)
• Exchange API keys only if you want to trade or read private account data — public market data needs none
• Per-exchange credentials set as environment variables, e.g. `BINANCE_API_KEY` / `BINANCE_SECRET`, or `KUCOIN_API_KEY` / `KUCOIN_SECRET` / `KUCOIN_PASSPHRASE` for exchanges that require a passphrase
• An MCP-compatible client (Claude Desktop, Cursor, etc.)

About CCXT MCP Server

Tools & capabilities (12)

When to use it

• You want one unified interface to pull tickers, order books, and OHLCV across many crypto exchanges
• You're building an AI agent that analyzes spot and futures market data in real time
• You want to place and cancel spot or futures orders on an exchange via natural language
• You need funding rates, leverage tiers, or positions data for perpetuals
• You want exchange data without writing per-exchange API integration code
• You need caching and rate-limit handling so frequent LLM queries don't get throttled

Quick setup

1. 1Run the server with `npx @mcpfun/mcp-server-ccxt` (or install globally with npm)
2. 2For trading, gather API keys from each exchange you'll use
3. 3Set per-exchange env vars like `BINANCE_API_KEY` and `BINANCE_SECRET` (add a passphrase var where required)
4. 4Add the server to your MCP client config with the npx command and env block
5. 5Restart your MCP client and confirm the CCXT tools load
6. 6Verify by listing exchanges or fetching a ticker

CCXT MCP Server FAQ