MCP Server Ccxt

What doggybee/mcp-server-ccxt MCP server does

The doggybee/mcp-server-ccxt MCP server connects MCP-compatible clients to cryptocurrency exchanges through the CCXT library. It presents exchange operations as MCP tools instead of requiring an agent to implement each exchange API separately. The README describes support for more than 20 exchanges and for spot, futures, and swap market types.

Public operations include listing exchanges, retrieving ticker and batch ticker data, reading OHLCV candles and recent trades, inspecting markets, checking exchange status, viewing funding rates, and retrieving futures leverage tiers. An order book tool is also documented in the project README. Private operations cover balances, open orders, order history, order cancellation, spot and futures order placement, leverage and margin configuration, and transfers between account types.

How it works

An MCP client sends tool requests to the server. The server manages exchange instances and passes exchange operations through CCXT's unified API. Its internal modules separate exchange and credential handling from utility functions and MCP tool implementations.

The server includes caching and request-rate controls. The documented cache durations include 10 seconds for ticker data, 5 seconds for order book data, and one hour for market data. Rate handling can adapt to exchange responses, back off after errors, and manage concurrent requests for an exchange. Utility tools expose cache statistics, cache clearing, logging controls, proxy settings, default exchange selection, and default market type selection.

Setup and configuration

The doggybee/mcp-server-ccxt MCP server can be installed from npm as @mcpfun/mcp-server-ccxt. The README shows global installation followed by the mcp-server-ccxt command, or direct execution with npx. It also documents cloning the repository, installing dependencies, building it, and starting it with npm.

Configuration is supplied through environment variables. DEFAULT_EXCHANGE and DEFAULT_MARKET_TYPE can select defaults. Exchange-specific credentials use variables such as BINANCE_API_KEY, BINANCE_SECRET, KUCOIN_API_KEY, KUCOIN_SECRET, and KUCOIN_PASSPHRASE. Proxy access can be enabled with USE_PROXY and configured with PROXY_URL. Credentials are optional for public market data, but private account and trading tools require appropriate exchange API permissions.

Claude Desktop can launch the globally installed server through a mcpServers entry whose command is mcp-server-ccxt. The project also documents a manual Node.js configuration that points to the built server file.

Tools and capabilities

Available tool groups include:

• Market data: exchanges, tickers, batch tickers, order books, OHLCV, trades, and markets.
• Exchange and derivatives data: exchange status, leverage tiers, funding rates, positions, open orders, and order history.
• Private actions: balances, market and limit orders, futures orders, cancellations, leverage, margin mode, and fund transfers.
• Runtime controls: cache inspection and clearing, log level, proxy configuration, market type, default exchange, and system information.

Limitations and notes

Exchange behavior and supported operations depend on the specific exchange and its CCXT implementation. Trading and account tools require API credentials with suitable permissions. The project recommends restricting permissions, avoiding withdrawal access when unnecessary, using IP allowlists where available, and keeping credentials out of source control.

Using the doggybee/mcp-server-ccxt MCP server to trade carries cryptocurrency and API-key security risks. The README states that the software is informational, provides no investment advice, and comes without a warranty.