binance

This Binance MCP Server exposes Binance exchange functionality to Claude Code and other MCP-compatible tools. It wraps Binance API access behind an MCP-enabled interface, providing tools for market data, account information, and trading operations. With the configured MCP server, you can ask Claude or your MCP client to fetch prices, order books, or place and manage orders using the standardized MCP commands (e.g., get_price, get_orderbook, place_order). The server supports both Binance mainnet and testnet modes, controlled via BINANCE_TESTNET in the environment.

To use it, configure your MCP client with the binance server entry (binance) and provide your API credentials. You can also use the one-click setup with Claude Code to add the MCP entry and launch the server inline. Once running, you can issue natural-language prompts like: "Get the current price of BTCUSDT", "Show me the order book for ETHUSDT", or "Place a limit buy order for 0.001 BTC at $50,000". The server will translate these requests into Binance API calls and return structured results.

Prerequisites:

• Node.js and npm installed on your system
• Internet access to install the npm package

Step-by-step installation:

1. Install the Binance MCP Server globally via npm:

npm install -g binance-mcp-server

2. Ensure your environment is prepared with Binance API credentials. Create a .env file or export variables in your shell:

export BINANCE_API_KEY=your_api_key
export BINANCE_API_SECRET=your_api_secret
export BINANCE_TESTNET=true  # set to false for mainnet

3. Start the MCP server (as used in MCP configuration):

npx binance-mcp-server

4. If using Claude Code or another MCP client, add the server entry corresponding to the provided configuration (see mcp_config), and initialize it with your API keys if prompted.

Tips and common issues:

• Ensure BINANCE_API_KEY and BINANCE_API_SECRET are kept secure and not committed to source control.
• Use BINANCE_TESTNET=true during development to avoid risking real funds; switch to false for production trading.
• When running in mainnet mode, be aware of potential real-money trades and confirm actions where required by your MCP client.
• If you regenerate API keys, update the environment variables accordingly.
• The MCP configuration expects the server name to be binance; adjust your MCP client configuration if you use a different label.
• If you encounter authentication errors, verify that the API key has the correct permissions (trading and read access as needed) and that the system clock is synchronized to avoid signature issues.