Provides comprehensive access to Binance Futures API endpoints, including trading operations, account management, market data retrieval, risk management, and trading history analysis. Features 41 trading tools for placing/managing orders, monitoring positions, retrieving market data, and accessing trading history.
Binance MCP Server
A Model Context Protocol (MCP) server that provides comprehensive access to Binance Futures API endpoints. This server implements all major trading, account management, and market data functionality as documented in the Binance Futures API.
📋 Table of Contents
🚀 Quick Start
Install the package:
pip install binance_futures_mcpRun the server:
uvx binance_futures_mcp --binance-api-key "your_key" --binance-secret-key "your_secret"Configure in your MCP client (see Configuration section for detailed setup)
✨ Features
11 essential trading tools across 2 categories (Account Information and Market Data)
Proper authentication handling (rejects unauthenticated requests)
Error handling and graceful degradation
Real-time market data access
📦 Installation
Option 1: PyPI Installation (Recommended)
Install the package from PyPI:
Option 2: Docker Deployment
For containerized deployment:
Docker Compose (Optional)
Create a docker-compose.yml
:
Then run:
Development Installation
For development, you can install from source:
⚙️ Configuration
API Requirements
Your Binance API key needs the following permissions:
Futures Trading: For order placement and management
Futures Reading: For account and market data access
MCP Client Setup
This server can be integrated with various MCP clients. Here are configuration examples:
VS Code
Add to your VS Code settings.json
:
Cursor
Add to your Cursor configuration file (.cursor/mcp.json
):
Windsurf
Add to your Windsurf configuration (.windsurf/mcp.json
):
Claude Desktop
Add to your Claude Desktop configuration file:
On macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
Configuration Notes
No path needed: With PyPI installation, you don't need to specify paths or working directories
Set API credentials: Replace
your_api_key
andyour_secret_key
with your actual Binance API credentialsAlternative commands: You can also use
uvx binance_futures_mcp
orpython -m binance_mcp
Security: For production use, consider storing credentials in environment variables
🛠️ Available Tools
The server provides 11 essential tools organized into the following categories:
Account Information
(5 tools)
get_account_info
- Get account informationget_balance
- Get account balanceget_position_info
- Get position informationget_position_mode
- Get position mode (Hedge vs. One-way)get_commission_rate
- Get commission rate
Market Data
(6 tools)
get_exchange_info
- Get exchange trading rulesget_book_ticker
- Get best price/qty on the order bookget_price_ticker
- Get latest price for a symbolget_order_book
- Get order book depthget_klines
- Get candlestick dataget_mark_price
- Get mark price and funding rate
💡 Example Usage
Place a Market Order
Place a Limit Order
Get Account Information
Get Market Data
Get 24hr Price Statistics
Get Taker Buy/Sell Volume Ratio
🔒 Security
API Key Security
🔐 Your Binance API key and secret remain completely local to your computer. The MCP server runs entirely on your machine; neither the package author nor any third-party remote service can access your credentials.
Key Security Points:
✅ Store credentials in environment variables (recommended) or local config files
✅ Keys are never transmitted unless you publish them
❌ Never commit credentials to version control
❌ Never share screenshots/logs containing credentials
✅ Use API keys with minimal required permissions
✅ IP-whitelist your keys when possible
✅ Consider using Binance Testnet for development
How It Works:
Local Launch: Your editor/terminal launches the MCP server locally:
uvx binance_futures_mcp --binance-api-key $BINANCE_API_KEY --binance-secret-key $BINANCE_SECRET_KEYKeys Stay Local: Your credentials exist only:
In your environment variables or local config file
On your computer's command line/process table
In MCP process memory during HTTPS calls to Binance
No Telemetry: The package contains zero telemetry or analytics code
Rate Limiting & Error Handling
⚡ Respects Binance's weight-based rate limits
🔄 Automatic order placement rate limiting
🔐 Automatic HMAC SHA256 signature generation
🛡️ Comprehensive error handling with clear messages
✅ Parameter validation before API calls
📚 API Reference
This server implements all endpoints documented in the Binance Futures API:
Base URL:
https://fapi.binance.com
API Type: Binance USD-S Margined Futures
Authentication: API Key + HMAC SHA256 Signature
Rate Limits: Respected automatically
For detailed parameter specifications, see the Binance Futures API Documentation.
🔧 Development
Project Structure
Architecture Overview
Modular Design: Separated concerns across multiple components
Authentication: Secure API key handling with environment variables
Error Handling: Graceful degradation and comprehensive error management
Running Tests
Code Formatting
❗ Error Codes
Common Binance API error codes you might encounter:
Code | Description |
| Invalid symbol |
| Margin is insufficient |
| Invalid orderType |
| Filter failure (PRICE_FILTER, LOT_SIZE, etc.) |
| Mandatory parameter was not sent |
| Too many requests (rate limit exceeded) |
For a complete list, see the Binance API Error Codes.
🤝 Contributing
Fork the repository
Create a feature branch
Make your changes
Add tests if applicable
Submit a pull request
📄 License
MIT License - see LICENSE file for details.
⚠️ Disclaimer
⚠️ IMPORTANT: This software is for educational and development purposes. Trading cryptocurrencies involves substantial risk. Use at your own risk and never trade with money you cannot afford to lose.
💬 Support
For issues and questions:
Check the Binance API Documentation
Review the error codes in the API documentation
Ensure your API credentials have the correct permissions
This server cannot be installed
remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
Comprehensive Binance Futures trading MCP server with professional trading tools across account management, order execution, market data, and risk management. Features smart ticker caching, secure authentication, and Docker support for seamless integration with MCP clients.
Related MCP Servers
- -securityAlicense-qualityAn MCP server that integrates with the Freqtrade cryptocurrency trading bot.Last updated -80MIT License
- AsecurityFlicenseAqualityA Model Control Protocol (MCP) server that provides cryptocurrency trading interfaces for Binance exchange, enabling functions like real-time price fetching, account balance queries, order placement/cancellation, and automated arbitrage strategies.Last updated -99
- AsecurityAlicenseAqualityProvides an MCP server that allows large language models to access real-time and historical Bitcoin market data from Binance, including current prices, order book data, recent trades, and price history through a standardized interface.Last updated -103MIT License
- AsecurityAlicenseAqualityMCP service that provides real-time access to Binance cryptocurrency market data, allowing AI agents to fetch current prices, order books, candlestick charts, and trading statistics through natural language queries.Last updated -123330Apache 2.0