Binance MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level | info |
| BINANCE_API_KEY | Yes | Your Binance API key | |
| BINANCE_TESTNET | No | Enable testnet mode | false |
| MCP_SERVER_NAME | No | Server name | binance-mcp-server |
| BINANCE_API_SECRET | Yes | Your Binance API secret | |
| MCP_SERVER_VERSION | No | Server version | 1.0.0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_priceC | 获取指定交易对的当前价格 |
| get_orderbookC | 获取订单簿深度数据 |
| get_klinesC | 获取K线历史数据 |
| get_24hr_tickerC | 获取24小时价格变动统计 |
| get_account_infoB | 获取账户信息和余额 |
| get_open_ordersC | 获取当前挂单 |
| get_order_historyC | 获取历史订单记录 |
| place_orderB | 下单交易 - 支持主网和测试网（主网将使用真实资金） |
| cancel_orderC | 取消指定订单 - 支持主网和测试网 |
| cancel_all_ordersB | 取消指定交易对所有挂单 - 支持主网和测试网 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool has a distinct purpose with clear boundaries: cancel_all_orders vs. cancel_order (batch vs. single), get_24hr_ticker vs. get_price (statistics vs. spot), get_open_orders vs. get_order_history (current vs. past), and others like get_account_info, get_klines, get_orderbook, and place_order all target unique operations. No ambiguity exists between tools.
All tools follow a consistent verb_noun naming pattern (e.g., cancel_all_orders, get_account_info, place_order). The pattern is uniform across all 10 tools, using snake_case throughout with clear action-object pairs, making them predictable and easy to parse.
With 10 tools, this server is well-scoped for cryptocurrency trading on Binance. It covers essential operations like account management, market data, order placement, and order management without being overwhelming or sparse, fitting typical MCP server ranges.
The toolset provides complete coverage for a trading bot or analysis agent: account info and balance retrieval, market data (price, ticker, klines, orderbook), and full order lifecycle (place, cancel, view open/history orders). No gaps exist for core trading workflows.