MCP Binance Futures

What muvon/mcp-binance-futures MCP server does

The muvon/mcp-binance-futures MCP server connects an MCP client to Binance USDT-M Futures. It covers both public market information and authenticated futures-account operations. Market tools can return ticker data, mark price, funding rate, order-book levels, recent trades, candlesticks, and symbol trading rules such as tick size, lot size, minimum notional, and supported order types.

Signed tools expose non-zero wallet balances, open positions, account totals, unrealized PnL, margin usage, and the number of open positions. Trading operations support creating several Binance order types, changing or cancelling orders, reviewing open and historical orders, and reading personal fills. Position controls include leverage, margin type, isolated-margin adjustments, and one-way or hedge mode.

Tools and capabilities

The available tools fall into four practical groups:

• Market inspection: get_ticker, get_order_book, get_recent_trades, get_klines, get_symbol_info, and ping.
• Account state: get_balance, get_positions, and get_account_summary.
• Order handling: place_order, modify_order, cancel_order, cancel_all_orders, get_open_orders, get_order, get_order_history, and get_trade_history.
• Position and risk settings: set_leverage, set_margin_type, adjust_isolated_margin, set_position_mode, get_position_mode, and get_leverage_brackets.

Order creation supports LIMIT, MARKET, STOP, STOP_MARKET, TAKE_PROFIT, TAKE_PROFIT_MARKET, and TRAILING_STOP_MARKET orders. Leverage can be set from 1× through 125×, and margin can be switched between ISOLATED and CROSSED.

Setup and configuration

The muvon/mcp-binance-futures MCP server requires Python 3.11 or newer. The repository recommends uv, although installation with pip is also documented. Start the stdio server with python server.py, or use the installed mcp-binance-futures script after setting up the project.

Authenticated operations require two environment variables: BINANCE_API_KEY and BINANCE_API_SECRET. The Binance API key must have Futures trading enabled. Public market-data tools do not require authentication. A Claude Desktop configuration can launch the server with Python and pass these variables through its env section.

The project uses FastMCP for MCP wiring and httpx for HTTP requests. Its client layer handles request signing, transport, and error parsing, while the server layer defines the tools.

Limitations and notes

This server is specifically for Binance USDT-M Futures rather than general Binance products. Public and signed operations have different credential requirements, so account and trading calls cannot be used without valid Binance credentials. Because the tools can place orders, change leverage, alter margin settings, and close positions, API-key permissions should be restricted and IP whitelisting should be considered.

The documented examples use local stdio execution. The repository’s tests mock HTTP calls with respx, so they do not require real API keys or network access. No claim is provided here about support for MCP clients other than the documented Claude Desktop setup.