Binance Futures 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 with Futures trading enabled. | |
| BINANCE_SECRET_KEY | Yes | Your Binance secret key. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| new-orderB | Create a new order on Binance USDⓈ-M Futures. Supports all order types: LIMIT, MARKET, STOP, STOP_MARKET, TAKE_PROFIT, TAKE_PROFIT_MARKET, TRAILING_STOP_MARKET. Essential for executing trades on futures markets. |
| query-orderB | Query the status of a specific order on Binance USDⓈ-M Futures. Use this to check if an order was filled, pending, or cancelled. |
| cancel-orderA | Cancel an existing order on Binance USDⓈ-M Futures. Use this to cancel pending orders that haven't been executed yet. |
| get-accountA | Get current account information including balances, margin, and positions for Binance USDⓈ-M Futures. Essential for risk management and portfolio tracking. |
| get-positionB | Get current position information for Binance USDⓈ-M Futures. Returns details about open positions including entry price, size, PnL, and margin used. |
| get-open-ordersB | Get all current open orders for Binance USDⓈ-M Futures. Useful for monitoring pending orders and managing active trades. |
| cancel-all-ordersA | Cancel all open orders for a specific symbol on Binance USDⓈ-M Futures. Use with caution as this will cancel all pending orders. |
| modify-orderA | Modify an existing order on Binance USDⓈ-M Futures. Useful for updating price or quantity of pending orders without canceling and recreating them. |
| change-leverageB | Change the initial leverage of a symbol for Binance USDⓈ-M Futures. Critical for risk management and position sizing. |
| change-position-modeB | Change position mode between One-way Mode and Hedge Mode for Binance USDⓈ-M Futures. Hedge Mode allows holding both LONG and SHORT positions simultaneously. |
| change-margin-typeB | Change margin type between Cross and Isolated for a symbol on Binance USDⓈ-M Futures. Isolated margin limits risk to the specific position. |
| modify-position-marginA | Modify isolated position margin for Binance USDⓈ-M Futures. Add or reduce margin to adjust position risk and prevent liquidation. |
| get-all-ordersA | Get all orders (open, filled, cancelled) for a symbol on Binance USDⓈ-M Futures. Useful for order history and auditing. |
| get-trade-historyB | Get account trade list (executed trades) for Binance USDⓈ-M Futures. Returns detailed information about filled orders including price, quantity, and fees. |
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 14 tools
Each tool targets a distinct action (create, cancel, modify, query) and resource (order, position, account, leverage, margin). However, the read-side tools for orders (get-open-orders, get-all-orders, query-order, get-trade-history) have some conceptual overlap that could occasionally confuse an agent, though descriptions help clarify.
All tool names follow a consistent lowercase-hyphenated verb-noun pattern (e.g., new-order, cancel-order, get-position, change-leverage). The verbs vary appropriately by action, but the convention is uniform throughout.
With 14 tools, the set is well-scoped for a futures trading server. It covers order lifecycle, position management, account info, and margin/leverage settings without excessive redundancy.
Core CRUD for orders and key position/margin operations are present, covering most trading workflows. Minor gaps exist, such as an explicit close-position tool or getter for current leverage, but these can be worked around with existing tools.