mcp-binance-futures
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BINANCE_API_KEY | Yes | Binance API key with Futures trading enabled. | |
| BINANCE_API_SECRET | Yes | Binance API secret. |
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": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Test connectivity to the Binance Futures API. Returns {} on success. |
| get_tickerB | Get latest price, 24 h stats, and mark/index prices for a symbol. Returns a merged dict with:
|
| get_order_bookA | Get order book bids and asks for a symbol. Returns top |
| get_recent_tradesB | Get the most recent public trades for a symbol. |
| get_klinesA | Get OHLCV candlestick data for a symbol. Returns list of dicts with: openTime, open, high, low, close, volume, closeTime, quoteVolume, trades, takerBuyVolume, takerBuyQuoteVolume. |
| get_symbol_infoB | Get trading rules for a symbol: tick size, lot size, min notional, max leverage, etc. |
| get_balanceA | Get futures wallet balances for all assets with non-zero balance. Returns list of: asset, balance, availableBalance, crossWalletBalance, unrealizedProfit. |
| get_positionsA | Get current open positions (non-zero size). Per position: symbol, side, size, entryPrice, markPrice, unrealizedPnl, percentage, leverage, marginType, isolatedMargin, liquidationPrice. |
| get_account_summaryB | Get account-level summary: total balance, unrealized PnL, margin ratio, positions count. |
| get_open_ordersA | Get open orders for a symbol. Returns list of: orderId, clientOrderId, symbol, status, type, side, positionSide, price, origQty, executedQty, avgPrice, stopPrice, timeInForce, reduceOnly, closePosition, updateTime. Algo (conditional) orders also include '_isAlgo': True. |
| get_orderB | Get details of a specific order by orderId or clientOrderId. |
| get_order_historyB | Get recent order history for a symbol (all statuses). |
| place_orderA | Place a new futures order. ORDER TYPE GROUPS — choose the right one: Immediate orders (fill now or queue at price): MARKET: side=BUY, quantity=0.01 LIMIT: side=SELL, quantity=0.01, price=50000, time_in_force=GTC Conditional orders (wait for stop_price trigger, then execute): Stop-loss full close: side=SELL, type=STOP_MARKET, stop_price=45000, close_position=True Take-profit full close: side=SELL, type=TAKE_PROFIT_MARKET, stop_price=60000, close_position=True Stop-loss partial: side=SELL, type=STOP_MARKET, stop_price=45000, quantity=0.01, reduce_only=True Trailing stop: side=SELL, type=TRAILING_STOP_MARKET, stop_price=45000, quantity=0.01, callback_rate=1.0 IMPORTANT — close_position=True vs quantity+reduce_only: close_position=True → closes the ENTIRE position, no quantity needed, max 1 SL + 1 TP active at a time. reduce_only=True → closes a PARTIAL quantity, multiple allowed simultaneously. Never mix both on the same order. |
| modify_orderA | Modify price or quantity of an existing open LIMIT order (PUT /fapi/v1/order). |
| cancel_orderA | Cancel a single open order by orderId or clientOrderId. For algo (conditional) orders returned by get_open_orders with '_isAlgo': True, set is_algo=True — this routes to the Algo API using algoId. |
| cancel_all_ordersA | Cancel all open orders for a symbol. With source='all' (default), cancels both regular and algo (conditional) orders in parallel. |
| get_trade_historyB | Get your personal trade execution history for a symbol (fills). |
| set_leverageB | Set leverage for a symbol. Returns the new leverage and max notional value. |
| set_margin_typeA | Switch margin type for a symbol between ISOLATED and CROSSED. Note: Cannot change margin type while a position or open order exists. |
| adjust_isolated_marginA | Add or remove margin from an isolated position. Only valid when the symbol is in ISOLATED margin mode with an open position. |
| set_position_modeA | Switch between One-way Mode and Hedge Mode for the account. Note: Cannot change while any positions or open orders exist. |
| get_position_modeB | Get current position mode: Hedge Mode or One-way Mode. |
| get_leverage_bracketsA | Get leverage brackets for a symbol: max leverage per notional tier with maintenance margin rates. |
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 23 tools
Most tools have distinct purposes targeting specific futures trading operations like orders, positions, account info, and market data. However, some overlap exists between get_order and get_order_history (specific vs. recent orders) and between get_ticker and get_symbol_info (price stats vs. trading rules), though descriptions help clarify their differences.
Tool names follow a highly consistent verb_noun pattern throughout, such as get_account_summary, cancel_order, set_leverage, and adjust_isolated_margin. All tools use snake_case with clear, descriptive verbs, making the set predictable and easy to navigate.
With 23 tools, the count is borderline high for a single server, though it covers a comprehensive range of futures trading operations. It feels slightly heavy but is justifiable given the complexity of the domain, including orders, positions, account management, and market data.
The tool set provides complete coverage for Binance Futures trading, including full CRUD/lifecycle operations for orders (place, modify, cancel, get), positions (get, adjust margin), account settings (leverage, margin type, position mode), and market data (klines, ticker, order book). No obvious gaps are present for core trading workflows.