Binance MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BINANCE_API_KEY | Yes | Your Binance API key | |
| BINANCE_TESTNET | No | Use testnet (set to 'false' for mainnet) | true |
| BINANCE_API_SECRET | Yes | Your Binance API secret | |
| ENABLE_WITHDRAWALS | No | Enable withdrawal functionality (not recommended) | 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_priceA | Precio actual de un simbolo. Ej: symbol='BTCUSDT'. |
| get_24h_statsA | Estadisticas de 24h de un simbolo (volumen, cambio %, high/low). Ej: 'ETHUSDT'. |
| get_klinesB | Velas (candlesticks) de un simbolo. interval: 1m,5m,15m,1h,4h,1d,1w, etc. limit: max 1000. |
| get_order_bookB | Libro de ordenes (bids/asks) de un simbolo. limit: 5,10,20,50,100,500,1000. |
| get_accountA | Balances y permisos de tu cuenta spot. Requiere firma. |
| get_open_ordersC | Ordenes abiertas. Si pasas symbol, filtra por ese par. |
| get_my_tradesB | Historial de trades tuyos para un simbolo. Requiere firma. |
| place_orderA | Crea una orden de compra/venta. symbol: ej 'BTCUSDT' side: 'BUY' o 'SELL' order_type: 'MARKET' o 'LIMIT' quantity: cantidad del activo base price: requerido solo para LIMIT time_in_force: GTC / IOC / FOK (solo LIMIT) |
| cancel_orderA | Cancela una orden por su orderId en el simbolo dado. |
| cancel_all_ordersB | Cancela TODAS las ordenes abiertas de un simbolo. |
| withdrawA | Retira fondos a una direccion externa. DESACTIVADO por defecto. Para usarlo: ENABLE_WITHDRAWALS=true y la API key debe tener permiso de retiro. Entende el riesgo antes de activarlo. |
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 11 tools
Each tool targets a distinct resource and action (market data, account, orders, withdrawals). The slight conceptual overlap between get_price and get_24h_stats is easily resolved by their descriptions, and cancel_order vs cancel_all_orders is clearly differentiated by scope.
All tools use a consistent verb_noun snake_case pattern (withdraw, get_price, place_order, cancel_order). Even get_24h_stats fits the convention. No mixed naming styles or ambiguous verbs.
With 11 tools, the server is well-scoped for a Binance trading API: market data queries, account information, order management, and withdrawals are all covered without unnecessary bloat. This is within the ideal range for a focused exchange integration.
The core spot trading lifecycle is well covered: price/klines/order book for market data, account balance/open orders/trades for status, and order placement/cancellation for trading actions. A notable missing piece is a specific get_order_status endpoint, but agents can use open orders or trade history as a workaround. Withdrawal history and deposit info are also absent but not essential for the main use case.