cancel_all_orders
Cancels every open order for one trading pair, on mainnet or testnet
LABSCO SUMMARY
The testnet switch is the feature that makes the trading tools usable.
Because the same tools run against the testnet or the live exchange depending on one variable, a strategy or an assistant's behaviour can be exercised end to end — orders placed, checked, cancelled — before any of it touches real money. Two things worth setting up deliberately: cancel_all_orders clears every open order on the symbol with no confirmation step, and the Binance API key's own permissions are the real safety boundary, so a read-only key is the right choice for anything that should only be looking.
What it is
A Binance exchange server covering market data, account state and order placement. One environment variable decides whether it talks to the testnet or to the live exchange with real funds.
What you get
- get_price for a symbol's current price, and get_24hr_ticker for its 24-hour change statistics
- get_orderbook returns depth to the limit you set, and get_klines returns candles at an interval and length
- get_account_info returns account details and balances
- get_open_orders lists what is currently working, and get_order_history returns past orders for a symbol
- place_order supports order types with side, quantity and price; the tool itself notes that on mainnet this uses real funds
- cancel_order removes one order by id, and cancel_all_orders clears every open order on a symbol
- Both live and testnet endpoints, chosen at startup rather than per call
Requirements
A Binance account with API credentials: BINANCE_API_KEY and BINANCE_API_SECRET. BINANCE_TESTNET="true" points everything at the testnet — set to "false", orders are real. It runs as npx binance-mcp-server, or from a global npm install. What the key is permitted to do at Binance bounds the tools: a read-only key leaves market data and account reads working and orders failing. Documentation is available in English, Chinese and Japanese.
Setup effort
One command plus a key — npm install -g binance-mcp-server, then supply credentials
USE CASES
01
Checking where a market is before acting
Read the current price, the 24-hour statistics, and the order book depth for the pair.
02
Rehearsing an order flow without risking funds
Point it at the testnet, place the order, look at what is open, and cancel it — the same calls you would use live.
03
Seeing what you currently hold
Read the account balances alongside the orders still working.
04
Reviewing how past trades went
Pull the order history for the symbol and compare it against the candles from the same period.
05
Getting out of a position quickly
Cancel everything working on that symbol in one call, then confirm nothing is left open.
10 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
cancel_order
Cancels one order by ID, on mainnet or testnet
get_24hr_ticker
Returns 24-hour price change statistics for a trading pair
get_account_info
Returns account information and balances
get_klines
Returns historical candlestick data for a trading pair at a given interval
get_open_orders
Returns the currently open orders, optionally for one trading pair
get_order_history
Returns past orders for a trading pair, up to a requested limit
get_orderbook
Returns order book depth for a trading pair, up to the requested limit
get_price
Returns the current price for one trading pair
place_order
Places an order on either mainnet or testnet; mainnet orders use real funds
BEFORE YOU INSTALL
What to know first
Tools you get
10 tools when we connected. BINANCE_TESTNET="true" runs the three trading tools against virtual funds; "false" or unset trades real money. A Chinese design document calls trading testnet-only, but the shipped package supports mainnet.
Requires
- npx on PATH
- BINANCE_API_KEY in your environment
- BINANCE_API_SECRET in your environment
Where it runs
All 4 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 10 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g binance-mcp-serverMCP Clients
Claude Desktop, Cursor, Trae
JSON
{
"mcpServers": {
"binance": {
"command": "npx",
"args": [
"binance-mcp-server"
],
"env": {
"BINANCE_API_KEY": "<YOUR_BINANCE_API_KEY>",
"BINANCE_API_SECRET": "<YOUR_BINANCE_API_SECRET>",
"BINANCE_TESTNET": "false"
}
}
}
}Claude Code
CLAUDE CODE · TERMINAL
claude mcp add binance --env BINANCE_API_KEY=<YOUR_BINANCE_API_KEY> --env BINANCE_API_SECRET=<YOUR_BINANCE_API_SECRET> --env BINANCE_TESTNET=false -- npx -y binance-mcp-server
