CCXT

What CCXT MCP server does

CCXT MCP server exposes CCXT's exchange connectivity through MCP tools for public market data, private account data, trading, funds movement, and live streams. It supports more than 100 cryptocurrency exchanges and prediction markets, including Polymarket, Kalshi, Hyperliquid, Limitless, and Myriad.

The interface uses CCXT's unified concepts where possible. Agents can work with exchange IDs, unified symbols, market types, timeframes, order records, balances, positions, and trades without constructing each exchange's API request. Prediction-market workflows use event discovery first, then pass returned outcome handles as symbols for market-data or order operations.

How it works

Exchange discovery starts with list_exchanges, describe_exchange, and describe_method. These tools expose supported unified methods, market types, timeframes, credential fields, sandbox availability, documentation links, method signatures, exchange-specific parameters, and implicit endpoint names.

Public data tools cover tickers, order books, OHLCV candles, recent trades, and market search. search_markets is paginated and intentionally resolves markets rather than returning an unbounded exchange-wide list. Prediction venues use search_events, which requires a query, tags, event ID, or slug to scope the search.

For data outside the dedicated tools, call_read_method accepts only unified fetch* and load* methods, while call_implicit_get invokes exchange-specific REST GET endpoints and returns their raw payloads. Read-only WebSocket subscriptions use watch_subscribe, watch_read, watch_list, and watch_unsubscribe. State streams return the current merged snapshot; event streams return cursor-based updates, allowing an agent to wait for changes such as fills or position updates.

Account operations refer to locally configured named accounts. list_accounts and get_safety_status expose aliases, capability flags, environments, caps, journal details, and configuration status without exposing credentials. Trading operations include order creation, editing, cancellation, leverage, margin mode, selected write methods, withdrawals, and internal transfers.

Tools and capabilities

• Discover supported exchanges, unified methods, market types, timeframes, credentials, sandbox support, and documentation URLs.
• Search spot, derivatives, and other exchange markets, or find prediction-market events and outcome handles.
• Retrieve tickers, order books, OHLCV, public trades, balances, orders, private trades, and positions.
• Subscribe to live tickers, order books, candles, balances, positions, trades, orders, liquidations, and related CCXT Pro streams where supported.
• Place, edit, cancel, and bulk-cancel orders; configure leverage and margin mode; dispatch supported account write methods.
• Withdraw assets, transfer funds between wallets on one exchange account, and call exchange-specific read endpoints.

Limitations and notes

Exchange support differs by method and market type, so inspect capabilities before relying on a feature. WebSocket availability also varies by exchange, and inactive streams stop automatically after 10 minutes without a read.

Order behavior depends on the account's environment and confirmation policy. Live orders may require a preview and confirmation, while sandbox or demo orders can execute immediately under the default policy. Order creation is checked against market precision, limits, and configured notional caps. Editing may be emulated as cancel-then-replace, which can lose queue position or leave only the cancellation successful.

Cancellation does not require confirmation. Withdrawals are irreversible after dispatch; the destination address and network should be checked against the preview. Conditional orders may not appear in get_orders on some exchanges, so a returned stop-order result should not automatically be treated as guaranteed protection.