binance-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port when using MCP_TRANSPORT=http (default 8080) | 8080 |
| MCP_TRANSPORT | No | stdio (default) or http | stdio |
| BINANCE_API_KEY | No | Required for account/trade tools (public tools work without) | |
| BINANCE_BASE_URL | No | Defaults to https://api.binance.com (override for testnet) | https://api.binance.com |
| BINANCE_API_SECRET | No | Required for account/trade tools | |
| BINANCE_RECV_WINDOW | No | RecvWindow in ms (default 5000) | 5000 |
| BINANCE_TRADE_ENABLED | No | Set to false to disable trade tools entirely | false |
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 |
|---|---|
| binance_market_priceC | Get the latest price for a symbol (e.g. BTCUSDT). |
| binance_market_klinesC | Get historical klines/candles for a symbol and interval. |
| binance_market_exchangeInfoB | Get exchange information including filters per symbol. |
| binance_account_balancesB | Get account balances (requires API key & secret). |
| binance_account_openOrdersC | List open orders for a symbol. |
| binance_trade_placeOrderC | Place a spot order. Example: {symbol:'BTCUSDT', side:'BUY', type:'MARKET', quoteOrderQty:'50'} |
| binance_trade_cancelOrderC | Cancel a spot order by symbol and orderId. |
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 7 tools
Each tool has a clearly distinct purpose targeting different aspects of the Binance API: account balances, open orders, market data (exchange info, klines, price), and trade operations (place/cancel orders). There is no overlap or ambiguity between tools, making it easy for an agent to select the right one.
All tools follow a consistent 'binance_<category>_<action>' naming pattern (e.g., binance_account_balances, binance_market_klines). This structured approach makes the tool set predictable and easy to understand, with no deviations in style or convention.
With 7 tools, this server is well-scoped for its purpose of interacting with the Binance API. It covers essential areas like account management, market data, and trading without being overwhelming or too sparse, making each tool earn its place in the set.
The tool set provides strong coverage for core Binance operations, including account info, market data, and basic trading (place/cancel orders). A minor gap is the lack of tools for more advanced trading features like order history or portfolio management, but agents can still handle most common workflows effectively.