account-balance
Get your account balance from a crypto exchange
LABSCO SUMMARY
Market data with no credentials at all, and trading only when you hand over keys per call.
The split is the useful part: everything needed to research a market is public, and the credentials only appear on the four tools that touch an account — passed as arguments, so a research session can run with none configured anywhere. Two things to note before trading through it: the order tools are market orders, so there is no limit price to protect you against a thin book, and leverage and margin mode are separate calls that have to land before the futures order does.
What it is
A CCXT-backed bridge to cryptocurrency exchanges. Every call names the exchange, so one connection covers many venues, with spot, futures and swap markets selected per call through marketType.
What you get
- list-exchanges and get-exchange-info tell you what is reachable and what state it is in; get-market-types and get-markets enumerate what each exchange trades, paginated
- get-ticker for one pair and batch-get-tickers for many at once, which is what keeps a multi-pair question to a single call
- get-orderbook with a depth limit, get-trades for recent prints, and get-ohlcv for candles at the timeframe you name
- Derivatives data as its own tools: get-funding-rates for perpetuals and get-leverage-tiers for the tiers a pair allows
- account-balance, place-market-order and place-futures-market-order take the API key and secret as call arguments, so credentials can stay out of the server configuration entirely
- set-leverage and set-margin-mode configure a futures position before the order goes in
- Proxy support as first-class tools: read the configuration, set it with a URL and credentials, and test the connection against a named exchange before relying on it
- cache-stats and clear-cache expose the response cache, clear-exchange-cache reloads exchange instances after a configuration change, and set-log-level turns up detail when something misbehaves
Requirements
Nothing at all for market data — tickers, order books, candles and funding rates are public. Trading needs that exchange's API key and secret, which can either be passed on the call or set in the environment as BINANCE_API_KEY and BINANCE_SECRET style pairs, with KUCOIN_PASSPHRASE for exchanges that need a passphrase. DEFAULT_EXCHANGE and DEFAULT_MARKET_TYPE set the fallbacks. It runs as npx @mcpfun/mcp-server-ccxt, or from a global install as mcp-server-ccxt. USE_PROXY and PROXY_URL route requests through a proxy where an exchange is otherwise unreachable.
Setup effort
One command — npx @mcpfun/mcp-server-ccxt
USE CASES
01
Comparing a coin's price across exchanges
Pull tickers for the same pair from several venues in a batch and read them side by side, no account anywhere.
02
Judging whether a market is deep enough to trade
Look at the order book to the depth you care about and the recent trades that actually printed, rather than at the headline price.
03
Studying price history for a pair
Pull candles at the timeframe and length you need, and check which markets and market types that exchange offers first.
04
Working out the carry on a perpetual
Read current funding rates and the leverage tiers for the contract before sizing anything.
05
Opening a futures position with your own keys
Set the leverage and margin mode for the symbol, place the order, then read the balance back.
06
Reaching an exchange that blocks your network
Point the client at a proxy, test the connection against that exchange, and reload the cached exchange instances so the new setting takes effect.
24 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
batch-get-tickers
Get ticker information for multiple trading pairs at once
cache-stats
Get CCXT cache statistics
clear-cache
Clear CCXT cache
clear-exchange-cache
Clear exchange instance cache to apply configuration changes
get-exchange-info
Get exchange information and status
get-funding-rates
Get current funding rates for perpetual contracts
get-leverage-tiers
Get futures leverage tiers for trading pairs
get-market-types
Get market types supported by an exchange
get-markets
Get all available markets for an exchange
get-ohlcv
Get OHLCV candlestick data for a trading pair
get-orderbook
Get market order book for a trading pair
get-proxy-config
Get the current proxy configuration
get-ticker
Get current ticker information for a trading pair
get-trades
Get recent trades for a trading pair
list-exchanges
List all available cryptocurrency exchanges
place-futures-market-order
Place a futures market order
place-market-order
Place a market order on an exchange
set-leverage
Set leverage for futures trading
set-log-level
Set logging level
set-margin-mode
Set margin mode for futures trading
set-market-type
Set default market type for all exchanges
set-proxy-config
Configure proxy settings for all exchanges
test-proxy-connection
Test the proxy connection with a specified exchange
BEFORE YOU INSTALL
What to know first
Tools you get
24 tools when we connected. Documented tools for limit orders, cancels, positions, order history and fund transfers (place-limit-order, cancel-order, cancel-all-orders, get-positions, transfer-funds) do not appear, and no documented setting enables them.
Requires
npx on PATH
Optional
- BINANCE_API_KEY in your environment
- BINANCE_SECRET in your environment
- KUCOIN_API_KEY in your environment
- KUCOIN_SECRET in your environment
- KUCOIN_PASSPHRASE in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 24 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @mcpfun/mcp-server-ccxtMCP Clients
Claude Desktop — Global npm
CLAUDE DESKTOP — GLOBAL NPM · TERMINAL
npm install -g @mcpfun/mcp-server-ccxtCLAUDE DESKTOP — GLOBAL NPM · JSON
{
"mcpServers": {
"ccxt": {
"command": "mcp-server-ccxt"
}
}
}The configuration on this page does not set BINANCE_API_KEY, BINANCE_SECRET, KUCOIN_API_KEY, KUCOIN_SECRET and KUCOIN_PASSPHRASE; the project's instructions put them in a .env file. Check which folder the server reads that file from before you rely on it.
Claude Desktop — Local build
CLAUDE DESKTOP — LOCAL BUILD · TERMINAL
git clone https://github.com/doggybee/mcp-server-ccxt.git
cd mcp-server-ccxt
npm install
npm run buildCLAUDE DESKTOP — LOCAL BUILD · JSON
{
"mcpServers": {
"ccxt": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_SERVER_CCXT>/build/index.js"
]
}
}
}<YOUR_PATH_TO_MCP_SERVER_CCXT> is the full path of your clone.
The configuration on this page does not set BINANCE_API_KEY, BINANCE_SECRET, KUCOIN_API_KEY, KUCOIN_SECRET and KUCOIN_PASSPHRASE; the project's instructions put them in a .env file. Check which folder the server reads that file from before you rely on it.
Claude Desktop — Debug build
CLAUDE DESKTOP — DEBUG BUILD · TERMINAL
git clone https://github.com/doggybee/mcp-server-ccxt.git
cd mcp-server-ccxt
npm install
npm run buildCLAUDE DESKTOP — DEBUG BUILD · JSON
{
"mcpServers": {
"ccxt": {
"command": "bash",
"args": [
"-c",
"node <YOUR_PATH_TO_MCP_SERVER_CCXT>/build/index.js 2> /tmp/ccxt-debug.log"
],
"env": {
"NODE_ENV": "production"
}
}
}
}<YOUR_PATH_TO_MCP_SERVER_CCXT> is the full path of your clone. The server's error output goes to /tmp/ccxt-debug.log.
The configuration on this page does not set BINANCE_API_KEY, BINANCE_SECRET, KUCOIN_API_KEY, KUCOIN_SECRET and KUCOIN_PASSPHRASE; the project's instructions put them in a .env file. Check which folder the server reads that file from before you rely on it.
