High-performance CCXT MCP server for cryptocurrency exchange integration
Configuration
View docs{
"mcpServers": {
"doggybee-mcp-server-ccxt": {
"command": "mcp-server-ccxt",
"args": [],
"env": {
"PROXY_URL": "http://username:[email protected]:8080",
"USE_PROXY": "false",
"KUCOIN_SECRET": "your_kucoin_secret",
"BINANCE_SECRET": "your_api_secret",
"KUCOIN_API_KEY": "your_kucoin_api_key",
"BINANCE_API_KEY": "your_api_key",
"DEFAULT_EXCHANGE": "binance",
"KUCOIN_PASSPHRASE": "your_passphrase",
"DEFAULT_MARKET_TYPE": "spot"
}
}
}
}You can connect language models to multiple cryptocurrency exchanges through a high‑performance MCP server that wraps CCXT. This server enables real‑time market data access and trading actions across many exchanges via a unified interface, making it easier to build intelligent trading assistants and analytics tools.
Use the CCXT MCP Server to bridge MCP clients with crypto exchange data and trading capabilities. You will run the server locally or remotely, then point your MCP client to its command or URL. The server exposes a set of tools to fetch market data, place orders, manage accounts, and retrieve exchange information, all through MCP endpoints.
Prerequisites: you need Node.js installed on your machine. You can verify your Node and npm versions after installation.
Option 1: Install via npm package (recommended)
# Install globally
npm install -g @mcpfun/mcp-server-ccxt
# Start the server
mcp-server-ccxtOption 2: Run directly with npx (no global install)
# Run the server without installing globally
npx @mcpfun/mcp-server-ccxtOption 3: Manual installation from source (clone, install, build, run)
# Clone the repository
git clone https://github.com/doggybee/mcp-server-ccxt.git
cd mcp-server-ccxt
# Install dependencies
npm install
# Build the server
npm run build
# Start the server
npm startCreate and customize environment settings to control which exchanges you connect to and how you authenticate. A typical environment file may define a default exchange, a default market type, and API keys for exchanges you plan to access.
Example startup note: you can start with the default exchange and market type, then rely on your API keys and optional proxy settings for production use.
Create and populate your environment configuration to enable exchange connections and optional proxy usage.
Basic environment you may copy and adapt is shown here for reference.
# Copy default environment example
cp .env.example .env
# Edit the environment file to add your credentials and preferences
# Default exchange (optional)
DEFAULT_EXCHANGE=binance
# Default market type (optional)
DEFAULT_MARKET_TYPE=spot
# API credentials (optional)
BINANCE_API_KEY=your_api_key
BINANCE_SECRET=your_api_secret
# For exchanges requiring passphrase (e.g., KuCoin)
KUCOIN_API_KEY=your_kucoin_api_key
KUCOIN_SECRET=your_kucoin_secret
KUCOIN_PASSPHRASE=your_kucoin_passphrase
# Proxy configuration (optional)
USE_PROXY=false
PROXY_URL=http://username:password@your-proxy-server:portIf you encounter issues with MCP communication, restart the server after updating environment variables. Check that your API keys have the correct permissions and that your network allows outbound connections to the exchanges.
Treat API keys with care. Create dedicated keys per application, restrict permissions to read-only where possible, and avoid exposing keys in version control. Store credentials in a secure environment or vault and rotate keys periodically.
The CCXT MCP Server uses an optimized caching layer and adaptive rate limiting to provide fast, reliable access to market data and trading operations across multiple exchanges.
List all available cryptocurrency exchanges that the server can connect to via CCXT.
Fetch current ticker information for a trading pair on a specified exchange.
Retrieve the market order book for a trading pair on a given exchange.
Obtain OHLCV candlestick data for a trading pair over a specified timeframe.
Get recent trades for a trading pair on an exchange.
Place a market order on an exchange (requires API keys).
Place a limit order on an exchange (requires API keys).
Cancel an existing order on an exchange (requires API keys).
Retrieve account balance from a connected exchange (requires API keys).
Get status and information about a connected exchange.
Configure proxy settings for outbound requests.
Set the default exchange used when none is specified in requests.