binance

This Binance MCP Server provides an MCP interface to access Binance spot and futures trading, account management, and market data through Claude Desktop. It exposes a structured set of 35 tools across five categories (account management, spot trading, futures trading, market data, and advanced analysis) with Chinese UI output and actionable guidance. You can run the server in stdio mode locally and connect via Claude Desktop using the generated MCP config. Typical workflows include querying balances, placing market/limit orders, managing futures positions and leverage, obtaining real-time prices and K-line data, and performing risk and portfolio analysis. The 35 tools are organized in dedicated namespaces such as binance_account_info, binance_spot_buy, binance_futures_buy, binance_get_price, and binance_analyze_portfolio_risk, enabling you to chain queries and actions in natural language prompts.

To use it, configure Claude Desktop to connect via the provided MCP endpoint (stdio in this setup). Supply your Binance API credentials in the environment variables (or via the connection method you choose). Once connected, you can ask the assistant to: fetch your spot/futures balances, place orders, fetch order history, request market data for BTCUSDT, run risk analyses on your unified account, and explore arbitrage opportunities. The system supports multiple modes (STDIO, SSE, Streamable HTTP, and multi-mode) in the README, so you can tailor deployment to your environment.

Prerequisites:

• Node.js v18 or newer installed on your system
• npm or yarn for dependencies
• A Binance API key with appropriate permissions (spot, futures, unified account, and read access)

Step-by-step installation:

1. Clone the repository: git clone <repository-url>\n cd binance-mcp-server

2. Install dependencies: npm install

3. Build the project (if applicable for production build): npm run build

4. Start in multi-mode development (or use your preferred mode): npm run dev:multi-mode

5. Verify the server is running by visiting the configured endpoint or checking the console for startup messages. For stdio usage, ensure your MCP config points to the built index.js file as shown in the mcp_config example.

6. Optional: run tests and format checks: npm test npm run format

Prerequisites recap:

• Node.js >= 18
• Access to Binance API keys with necessary permissions
• Knowledge of the path to your built MCP server (index.js) when using stdio mode

Tips and common considerations:

• For production, use the Streamable HTTP or multi-mode deployment as recommended in the README to improve reliability and performance.
• Set BINANCE_TESTNET to true to use the test network for safe practice.
• Adjust LOG_LEVEL to debug/info/warn/error as needed during troubleshooting.
• Keep your API keys secure; prefer environment-based key injection and avoid hard-coding keys in code.
• If you encounter API rate limits, implement backoff handling or switch to higher-throughput modes like Streamable HTTP.
• The mcp_config example uses a absolute path placeholder; replace it with the actual path to your built server file.
• Ensure Claude Desktop configuration matches the selected mode (STDIO, SSE, or Streamable HTTP) and that API credentials are provided in the correct place per mode.