MCP Server CCXT
Provides access to cryptocurrency exchange APIs through CCXT, enabling market data retrieval, account balance checks, and trading operations across multiple exchanges like Binance, Coinbase, and Kraken with built-in security features.
README
MCP Server CCXT
⚠️ Work in Progress: This project is currently under active development. Features and APIs may change without notice. Use in production environments at your own risk.
MCP (Model Context Protocol) server that exposes CCXT cryptocurrency exchange APIs via Server-Sent Events (SSE). This server provides 24 comprehensive tools for interacting with multiple cryptocurrency exchanges.
🔒 Security First
IMPORTANT: This server includes multiple layers of security to prevent accidental or malicious trading operations:
- 🛡️ SAFE_MODE: Disable all trading operations, only read-only access
- ⏱️ Rate Limiting: Prevent burst of orders (max 10 orders/minute per session)
- 📝 Enhanced Logging: Full audit trail of all trading operations
- 🔍 Tool Classification: Clear separation between safe vs dangerous tools
- 🚨 Security Checks: Multiple validation layers before executing trades
See SECURITY.md for complete security documentation.
Quick Start - Safe Mode
For maximum security (recommended for production):
# .env
SAFE_MODE=true # Disables ALL trading operations
With SAFE_MODE enabled:
- ✅ Can read: balances, markets, prices, orders, history
- ❌ Cannot: place orders, cancel orders, transfer funds
Features
- 🌐 Web-based MCP server using SSE transport
- 💱 Multiple exchange support: Binance, Coinbase, Kraken, Bitfinex, Bybit
- 🔧 24 comprehensive tools (13 public + 11 private)
- 🔐 Environment-based credentials management
- 🛡️ Advanced security features (SAFE_MODE, rate limiting, audit logs)
- 📊 Public APIs: Market data, tickers, orderbooks, OHLCV, trades, funding rates
- 💰 Private APIs: Account balance, order management, futures trading, fund transfers
- 🔄 Session-based transport with UUID tracking
- 📝 Detailed logging for debugging
Installation
npm install
Configuration
Create a .env file in the root directory:
# ==========================================
# Security Configuration
# ==========================================
# SAFE_MODE: Disable ALL trading operations
# Recommended: true for production
SAFE_MODE=false
# ==========================================
# Server Configuration
# ==========================================
HOST=0.0.0.0
PORT=3000
LOG_LEVEL=info
DEFAULT_EXCHANGE=coinbase
# ==========================================
# Exchange API Credentials
# ==========================================
# Only needed for private tools (balance, orders, etc)
# Leave empty to use public tools only
BINANCE_API_KEY=your_binance_api_key
BINANCE_SECRET=your_binance_secret
COINBASE_API_KEY=your_coinbase_api_key
COINBASE_SECRET=your_coinbase_secret
KRAKEN_API_KEY=your_kraken_api_key
KRAKEN_SECRET=your_kraken_secret
# Add credentials for other exchanges as needed
Security Recommendations:
- Always enable SAFE_MODE unless trading is explicitly required
- Use separate API keys for read-only vs trading operations
- Enable IP restrictions on exchange API keys
- Never commit
.envfile to version control - See SECURITY.md for complete security guide
Running the Server
npm start
The server will start on http://0.0.0.0:3000 (or your configured HOST/PORT).
Available Endpoints
- SSE Stream:
GET http://localhost:3000/sse- Establishes SSE connection - Messages:
POST http://localhost:3000/message?sessionId=<uuid>- Handles MCP messages - Health Check:
GET http://localhost:3000/health- Server health status - Info:
GET http://localhost:3000/- Server information - Stats:
GET http://localhost:3000/stats- Server statistics
Available Tools
Public Tools (13 tools - No authentication required)
- list_exchanges - List all available exchanges
- get_ticker - Get current ticker for a trading pair
- batch_get_tickers - Get multiple tickers at once
- get_orderbook - Get market order book
- get_ohlcv - Get candlestick data
- get_trades - Get recent trades
- get_markets - List all available markets
- get_exchange_info - Get exchange information
- get_leverage_tiers - Get futures leverage tiers
- get_funding_rates - Get perpetual futures funding rates
- get_positions - Get open positions (public data)
- get_open_orders - Get open orders (public data)
- get_order_history - Get order history (public data)
Private Tools (10 tools - Require API credentials)
- account_balance - Get account balance
- place_market_order - Place market order ⚠️
- place_limit_order - Place limit order ⚠️
- cancel_order - Cancel specific order
- cancel_all_orders - Cancel all orders
- set_leverage - Set futures leverage
- set_margin_mode - Set margin mode (isolated/cross)
- place_futures_market_order - Place futures market order ⚠️
- place_futures_limit_order - Place futures limit order ⚠️
- transfer_funds - Transfer funds between accounts
⚠️ Warning: Trading tools execute real operations with real money!
Testing
Basic Test
npm test
Extended Test
node test-extended.js
Tool Examples
Get Ticker
{
"name": "get_ticker",
"arguments": {
"symbol": "BTC/USDT",
"exchange": "binance"
}
}
Batch Get Tickers
{
"name": "batch_get_tickers",
"arguments": {
"symbols": ["BTC/USDT", "ETH/USDT", "BNB/USDT"]
}
}
List Exchanges
{
"name": "list_exchanges",
"arguments": {
"certified": false
}
}
Get Account Balance (requires credentials)
{
"name": "account_balance",
"arguments": {
"exchange": "binance"
}
}
Place Limit Order (requires credentials) ⚠️
{
"name": "place_limit_order",
"arguments": {
"symbol": "BTC/USDT",
"side": "buy",
"amount": 0.001,
"price": 50000
}
}
Architecture
mcp-server-ccxt/
├── index.js # Main server
├── src/
│ ├── mcpServer.js # MCP server
│ ├── config/
│ │ └── config.js # Configuration
│ ├── tools/
│ │ ├── publicTools.js # 13 public tools
│ │ └── privateTools.js # 10 private tools
│ └── utils/
│ └── exchangeManager.js # Exchange manager
├── test-mcp-client.js # Basic tests
├── test-extended.js # Extended tests
└── .env # Environment variables
MCP Integration
Using with n8n
- Install MCP connector in n8n
- Configure server URL:
http://your-server:3000 - Use tools in workflows
Custom Integration
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { SSEClientTransport } from "@modelcontextprotocol/sdk/client/sse.js";
const client = new Client({
name: "my-client",
version: "1.0.0",
}, { capabilities: {} });
const transport = new SSEClientTransport(
new URL("http://localhost:3000/sse")
);
await client.connect(transport);
const result = await client.callTool({
name: "get_ticker",
arguments: { symbol: "BTC/USDT" },
});
console.log(result.content[0].text);
Security
⚠️ Important Security Notes:
- Never commit
.envfile to version control - Trading tools execute real trades with real money
- Use HTTPS in production
- Restrict access with firewall rules
- Be aware of rate limits on exchanges
Supported Exchanges
- Coinbase (default)
- Binance
- Kraken
- Bitfinex
- Bybit
CCXT supports 100+ exchanges. Add credentials in .env to enable more.
Troubleshooting
Server won't start
- Check port 3000 is not in use
- Verify
.envfile exists - Check logs for errors
Tools not showing
- Restart server after code changes
- Check tool definitions
- Review server logs
Authentication errors
- Verify API keys in
.env - Check exchange name (lowercase)
- Ensure proper API permissions
License
MIT
Contributing
Contributions welcome! Please:
- Fork the repository
- Create feature branch
- Add tests
- Submit pull request
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.