Binance Integration for AI Agents

Access cryptocurrency market data, portfolios and trading operations on Binance. Monitor assets, retrieve market information and automate crypto trading workflows.

v1.0.012 toolsAPI KeyGitHub Report an issue

Open in ChatGPTChatGPT

Open in ClaudeClaude

Playground

VS Code

Connected to Binance via MewCP.

Encrypted at rest, isolated from the model

Resolved from an AES-256-GCM vault at the moment of the call and attached to the request — the model never sees the secrets.

Try asking

Everything Binance can do

Tools12

binance_ping

write

Test connectivity to Binance API. Returns True if connection is successful. No authentication required.

binance_server_time

write

Get Binance server time. No authentication required.

binance_exchange_info

write

Get exchange information including trading rules, symbol information, and rate limits. No authentication required.

binance_orderbook

write

Get current order book for a trading pair. Shows bids and asks with prices and quantities. No authentication required.

binance_klines

write

Get candlestick/kline data for a trading pair. Returns OHLCV data for charting. No authentication required.

binance_ticker_price

write

Get current price for a trading pair. If no symbol provided, returns prices for all symbols. No authentication required.

binance_account_info

write

Get account information including balances, commissions. Requires API key and secret.

binance_create_order

write

Create a new order. Supports LIMIT and MARKET orders. Requires API key and secret.

binance_cancel_order

write

Cancel an existing order. Requires API key and secret.

binance_open_orders

write

Get all open orders. Optionally filter by symbol. Requires API key and secret.

binance_my_trades

write

Get your trade history for a symbol. Requires API key and secret.

binance_health_check

write

Check server readiness and basic connectivity.

Missing a tool, or found a bug?

Binance MCP Server is open source. Tell the MewCP maintainers.

Open GitHub Issues

Connect Binance to your agent

One endpoint, the same key, whichever client you use.

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (Mac) · %APPDATA%\Claude\claude_desktop_config.json (Windows)

JSON

{
  "mcpServers": {
    "mewcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://gateway.mewcp.com/personal/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer API_KEY"
      }
    }
  }
}

Replace API_KEY with your own key.

Already have an "mcpServers" section in your config? Just add the server entry inside it.

01Open Claude Desktop → Settings → Developer → "Edit Config"
02Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one)
03Save the file, then quit Claude Desktop completely and reopen it
04Start a new conversation — your tool will be available

One endpoint. Every service.

Any agent

One Gateway

Polymarket

API Key

Coinfuty MCP

No auth

Upstox

OAuth

Binance

API Key

Discovery, routing, credentials, tool scoping and execution logs all happen at the gateway→connections stay ACTIVE with no work from you

Separate connections41 tool definitions ~3.5k tokensWith MewCP4 meta-tools ~1.4k tokens

Built for AI agents

Binance runs through a gateway that holds the credentials, scopes the access and records every call.

Managed credentials

Binance API keys are encrypted at rest and never shown again after you save them.
One credential per end user, not one shared key across your users.
Rotate a key without touching your agent's config.

Credentials stay out of context

Binance credentials are resolved at the gateway and attached to the outbound call.
The agent sees tool results, never a token.
Revoke an account and the next call stops working — no redeploy.

Scoped access, fully logged

Choose exactly which Binance tools an agent is allowed to call.
Every call is logged with its outcome, latency and which account it ran as.
Catalog changes are reviewed before they ship, so tool descriptions cannot shift under you.

One endpoint for every server

Reach Binance through the same MCP endpoint as the rest of your toolset.
Tools are discovered on demand, so 12 tools do not fill the context window.
Stateless: no sessions to keep alive and no reconnect logic.

Ready to connect Binance?

Managed auth, hosted MCP servers, and every Binance tool your agent needs.

Free to start.

Everything Binance can do

Tools12

binance_ping

write

Test connectivity to Binance API. Returns True if connection is successful. No authentication required.

binance_server_time

write

Get Binance server time. No authentication required.

binance_exchange_info

write

Get exchange information including trading rules, symbol information, and rate limits. No authentication required.

binance_orderbook

write

Get current order book for a trading pair. Shows bids and asks with prices and quantities. No authentication required.

binance_klines

write

Get candlestick/kline data for a trading pair. Returns OHLCV data for charting. No authentication required.

binance_ticker_price

write

Get current price for a trading pair. If no symbol provided, returns prices for all symbols. No authentication required.

binance_account_info

write

Get account information including balances, commissions. Requires API key and secret.

binance_create_order

write

Create a new order. Supports LIMIT and MARKET orders. Requires API key and secret.

binance_cancel_order

write

Cancel an existing order. Requires API key and secret.

binance_open_orders

write

Get all open orders. Optionally filter by symbol. Requires API key and secret.

binance_my_trades

write

Get your trade history for a symbol. Requires API key and secret.

binance_health_check

write

Check server readiness and basic connectivity.

Connect Binance to your agent

One endpoint, the same key, whichever client you use.

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (Mac) · %APPDATA%\Claude\claude_desktop_config.json (Windows)

JSON

{
  "mcpServers": {
    "mewcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://gateway.mewcp.com/personal/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer API_KEY"
      }
    }
  }
}

Replace API_KEY with your own key.

Already have an "mcpServers" section in your config? Just add the server entry inside it.

01Open Claude Desktop → Settings → Developer → "Edit Config"
02Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one)
03Save the file, then quit Claude Desktop completely and reopen it
04Start a new conversation — your tool will be available

Built for AI agents

Binance runs through a gateway that holds the credentials, scopes the access and records every call.

Managed credentials

Binance API keys are encrypted at rest and never shown again after you save them.
One credential per end user, not one shared key across your users.
Rotate a key without touching your agent's config.

Credentials stay out of context

Binance credentials are resolved at the gateway and attached to the outbound call.
The agent sees tool results, never a token.
Revoke an account and the next call stops working — no redeploy.

Scoped access, fully logged

Choose exactly which Binance tools an agent is allowed to call.
Every call is logged with its outcome, latency and which account it ran as.
Catalog changes are reviewed before they ship, so tool descriptions cannot shift under you.

One endpoint for every server

Reach Binance through the same MCP endpoint as the rest of your toolset.
Tools are discovered on demand, so 12 tools do not fill the context window.
Stateless: no sessions to keep alive and no reconnect logic.