The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the MCP Binance Futures listing page.
MCP server for Binance USDT-M Futures trading. Exposes tools for market data, account state, order management, and position/margin control — designed to give an LLM everything it needs to monitor, place, and manage futures trades.
| Tool | Description |
|---|---|
ping | Test API connectivity |
get_ticker | Price, 24 h stats, mark price, funding rate for a symbol |
get_order_book | Top N bids/asks for a symbol |
get_recent_trades | Latest public trades |
get_klines | OHLCV candlestick data (1m → 1w) |
get_symbol_info | Trading rules: tick size, lot size, min notional, order types |
| Tool | Description |
|---|---|
get_balance | Wallet balances (non-zero assets only) |
get_positions | Open positions with PnL, leverage, margin type — optionally scoped to one symbol |
get_account_summary | Total balance, unrealized PnL, margin usage, open position count |
| Tool | Description |
|---|---|
place_order | Place LIMIT, MARKET, STOP, STOP_MARKET, TAKE_PROFIT, TAKE_PROFIT_MARKET, TRAILING_STOP_MARKET |
modify_order | Change price or quantity of an open LIMIT order |
cancel_order | Cancel a single order by ID |
cancel_all_orders | Cancel all open orders for a symbol |
get_open_orders | List all open orders for a symbol |
get_order | Get a specific order by ID |
get_order_history | Recent order history (all statuses) |
get_trade_history | Personal fill history for a symbol |
| Tool | Description |
|---|---|
set_leverage | Set leverage multiplier (1–125×) for a symbol |
set_margin_type | Switch between ISOLATED and CROSSED margin |
adjust_isolated_margin | Add or remove margin from an isolated position |
set_position_mode | Switch between One-way and Hedge Mode |
get_position_mode | Get current position mode |
get_leverage_brackets | Leverage tiers with maintenance margin rates |
Create a Binance API key with Futures trading enabled. Set environment variables:
Security: Use IP whitelisting on your Binance API key. Never commit keys to version control.
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
Tests use respx to mock all HTTP calls — no real API keys or network required.
The client and server are intentionally kept in separate files: client.py handles all Binance API mechanics (HMAC signing, error parsing, HTTP verbs) while server.py contains only tool logic and MCP wiring. This makes both independently testable.