CCXT Crypto Trading

Interact with over 100 cryptocurrency exchange APIs using the CCXT library.

CCXT MCP Server is a server that allows AI models to interact with cryptocurrency exchange APIs through theModel Context Protocol (MCP). This server uses theCCXT libraryto provide access to more than 100 cryptocurrency exchanges and their trading capabilities.

# Install the package globally npm install -g @lazydino/ccxt-mcp # Run with default settings ccxt-mcp # or run without installation npx @lazydino/ccxt-mcp

# Install the package globally npm install -g @lazydino/ccxt-mcp

# Using default settings npx @lazydino/ccxt-mcp # Using custom configuration file npx @lazydino/ccxt-mcp --config /path/to/config.json

{ "mcpServers": { "ccxt-mcp": { "command": "npx", "args": ["-y", "@lazydino/ccxt-mcp"], "mcpBearerToken": "YOUR_MCP_TOKEN", "accounts": [ { "name": "bybit_main", "exchangeId": "bybit", "apiKey": "YOUR_API_KEY", "secret": "YOUR_SECRET_KEY", "defaultType": "spot" }, { "name": "bybit_futures", "exchangeId": "bybit", "apiKey": "YOUR_API_KEY", "secret": "YOUR_SECRET_KEY", "defaultType": "swap" } ] } } }

Using this method, you don't need a separate configuration file. All settings are integrated into the Claude Desktop configuration file.

Option 2: Using a Separate Configuration File (Advanced Method)

To separate account information into a separate configuration file, set up as follows:
- Create a Separate Configuration File(e.g.,ccxt-config.json):

{ "mcpBearerToken": "YOUR_MCP_TOKEN", "accounts": [ { "name": "bybit_main", "exchangeId": "bybit", "apiKey": "YOUR_API_KEY", "secret": "YOUR_SECRET_KEY", "defaultType": "spot" }, { "name": "bybit_futures", "exchangeId": "bybit", "apiKey": "YOUR_API_KEY", "secret": "YOUR_SECRET_KEY", "defaultType": "swap" } ] }

Important: The configuration file must contain anaccountsarray at the root level, as shown above.

Important: If you run the server in HTTP+SSE mode (--sse), setmcpBearerTokenin the same config file. Clients must sendAuthorization: Bearer <mcpBearerToken>on requests.
- Specify the Configuration File Path in Claude Desktop Settings:

{ "mcpServers": { "ccxt-mcp": { "command": "npx", "args": [ "-y", "@lazydino/ccxt-mcp", "--config", "/path/to/ccxt-config.json" ] } } }

Note: When using a separate configuration file with the--configoption, the server will look for theaccountsarray directly in the root of the JSON file, not inmcpServers.ccxt-mcp.accountspath.
- Running with External Configuration File from Command Line:

# Using custom configuration file npx @lazydino/ccxt-mcp --config /path/to/ccxt-config.json

You can find an example configuration file atconfig/ccxt-config.example.jsonin the repository.

Reasons to Use a Separate Configuration File:

- Prevents recursive reference issues
- Separates sensitive information like API keys
- Easier multi-environment configuration (development, testing, production)
- Improved configuration file version control

- List exchanges
- View market information by exchange
- Get price information for specific symbols
- View order book information for specific symbols
- Search historical OHLCV data

- Create market/limit orders
- Cancel orders and check status
- View account balances
- Check trading history

- Daily/weekly/monthly performance analysis
- Win rate calculation (last 7 days, 30 days, all time)
- Average profit/loss ratio (R-multiple)
- Maximum consecutive loss/profit series analysis
- Asset variation tracking
- Comprehensive performance metrics
- Trade pattern recognition
- Period-based return calculations

- Capital ratio trading (e.g., enter with 5% of account capital)
- Futures market leverage setting (1-100x)
- Dynamic position sizing (volatility-based)
- Split buy/sell strategy implementation

- Technical indicator-based stop loss setting (e.g., lowest point among 10 candles on 5-minute chart)
- Volatility-based stop loss/take profit (ATR multiples)
- Maximum allowable loss limit (daily/weekly)
- Dynamic take profit setting (trailing profit)

User <--> AI Model(Claude/GPT) <--> MCP Protocol <--> CCXT MCP Server <--> Cryptocurrency Exchange API

- User: Requests like "Tell me the Bitcoin price" or "Buy Ethereum on my Binance account"
- AI Model: Understands user requests and determines which MCP tools/resources to use
- MCP Protocol: Standardized communication between AI and CCXT MCP server
- CCXT MCP Server: Communicates with cryptocurrency exchange APIs using the CCXT library
- Exchange API: Provides actual data and executes trade orders

When registered with Claude Desktop, you can make the following types of requests to AI models:

When using AI models, consider the following cautions and use the prompt below for effective trading:

Your goal is to execute trades using the ccxt tools as much as possible Cautions: - Accurately identify whether it's a futures market or spot market before proceeding with trades - If there's no instruction about percentage of capital or amount to use, always calculate and execute trades using the entire available capital

- AI models sometimes confuse futures trading with spot trading.
- Without clear guidance on trading capital size, AI might get confused.
- Using the above prompt helps clearly communicate your trading intentions.

Check and compare the current Bitcoin price on binance and coinbase.

Open a long position on BTC/USDT futures market in my Bybit account (bybit_futures) with 5% of capital using 10x leverage. Enter based on moving average crossover strategy and set stop loss at the lowest point among the 12 most recent 5-minute candles.

Analyze my Binance account (bybit_main) trading records for the last 7 days and show me the win rate, average profit, and maximum consecutive losses.

Analyze my trading performance on the bybit_futures account for BTC/USDT over the last 30 days. Calculate win rate, profit factor, and identify any patterns in my winning trades.

Show me the monthly returns for my bybit_main account over the past 90 days and identify my best and worst trading months.

Analyze my consecutive wins and losses on my bybit_futures account and tell me if I have any psychological patterns affecting my trading after losses.

# Clone repository git clone https://github.com/lazy-dinosaur/ccxt-mcp.git # Navigate to project directory cd ccxt-mcp # Install dependencies npm install # Build npm run build

cp config/ccxt-config.example.json config/ccxt-config.json

Then fill in your real API keys inconfig/ccxt-config.json. Also setmcpBearerTokenin that same config file. 2. Build image:
- Start the MCP server in background (SSE mode on localhost:2298):

curl -H "Authorization: Bearer YOUR_MCP_TOKEN" http://127.0.0.1:2298/healthz

This Compose setup runs MCP over HTTP+SSE (/sse+/messages) on localhost:2298 for reverse proxying.

If your MCP client runs on another host, use an Nginx reverse proxy on this machine.
- Copyccxt-mcp.nginxto your Nginx config location and update certificate paths:

sudo cp ccxt-mcp.nginx /etc/nginx/conf.d/ccxt-mcp.conf

- Edit/etc/nginx/conf.d/ccxt-mcp.confand set:

- ssl_certificate
- ssl_certificate_key
- Authorization header forwarding (already included in this file)

sudo nginx -t && sudo systemctl reload nginx

- In your MCP client, configure the MCP server URL to your TLS endpoint:

- SSE URL:https://YOUR_HOSTNAME_OR_IP:42299/sse
- Messages URL:https://YOUR_HOSTNAME_OR_IP:42299/messages
- Header:Authorization: Bearer YOUR_MCP_TOKEN

{ "mcpBearerToken": "YOUR_MCP_TOKEN", "accounts": [ { "name": "bybit_main", "exchangeId": "bybit", "apiKey": "YOUR_API_KEY", "secret": "YOUR_SECRET_KEY" } ] }

- 42298is HTTP (redirect only)
- 42299is HTTPS
- 2298comes fromCCXTon a phone keypad

If your MCP client accepts command-based MCP servers instead of URL configuration, configureccxt-mcpwith:

[ "run", "--rm", "-i", "-p", "127.0.0.1:2298:2298", "-v", "/absolute/path/to/ccxt-mcp/config/ccxt-config.json:/config/ccxt-config.json:ro", "ccxt-mcp:local", "--sse", "--host", "0.0.0.0", "--port", "2298", "--config", "/config/ccxt-config.json" ]

Build the image first withdocker compose build.

Contributions are welcome! Please feel free to submit a Pull Request.

Distributed under the MIT License. See the LICENSE file for more information.

If you find this project useful, please consider giving it a ⭐️ on GitHub!

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Access prediction market data from the PolyMarket API.

WunderTrading MCP connects AI agents to live crypto trading execution on 20+ supported exchanges through a single MCP integration. Use it to turn AI-driven signals, market analysis, sentiment, screenshots, and custom strategy logic into real trades on exchanges including Binance, Bybit, Coinbase, Bitget, OKX, KuCoin, Hyperliquid, and BingX. Supports MCP and REST API workflows for order execution, trade management, and AI-powered automation.

Manage stock and crypto portfolios, place trades, and access market data via the Alpaca Trading API.

Provides seamless access to the Binance exchange API. Requires Binance API credentials to be configured.

Interact with the Binance API to view portfolios, convert tokens, and execute trades with minimal market impact.

Access the Binance Futures API for trading, account management, and market data.

Access market data, manage accounts, and execute trades on the Upbit Cryptocurrency Exchange via its OpenAPI.

Real-time and historical FX/crypto signal API for AI agents. Pay-per-call via x402 protocol on Base. No subscription, no API key. Correlation, regime, momentum, volatility across 10 instruments.

Interact with Alchemy's blockchain APIs to query data without writing code.

Integrate AI with high-frequency cryptocurrency trading systems.