Skip to main content
Glama

binance-mcp

Binance Spot REST MCP server providing market data, account state, and guarded trading tools. Built with FastMCP so it can run over stdio (local agents) or HTTP (Glama inspection / Docker deployments).

Features

  • Latest ticker price, klines, and exchangeInfo for any symbol.

  • Account tools (balances, open orders) with recvWindow helper.

  • Trading helpers (place/cancel) protected by BINANCE_TRADE_ENABLED toggle.

  • Works with Glama thanks to HTTP transport + glama.yaml/Dockerfile metadata.

Related MCP server: binance-futures-mcp

Getting started

  1. Install dependencies (Node 20+ recommended):

    npm install
  2. Copy the example env file and fill in your Binance key/secret (testnet keys work too):

    cp .env.example .env
    # BINANCE_TRADE_ENABLED=false keeps the server in read-only mode
  3. Build + run (stdio transport by default):

    npm run build
    npm start
  4. Development / watch mode:

    npm run dev

HTTP transport

Set MCP_TRANSPORT=http and optionally PORT to expose the tools over HTTP (required for Glama inspection):

MCP_TRANSPORT=http PORT=8080 npm run dev

The provided Dockerfile bakes this configuration automatically.

Tools

name

description

binance_market_price

Latest ticker price for a symbol.

binance_market_klines

Candles (symbol + interval, configurable limit).

binance_market_exchangeInfo

Full exchange metadata + filters.

binance_account_balances

Account snapshot (requires API key/secret).

binance_account_openOrders

Open orders for a symbol.

binance_trade_placeOrder

Places MARKET/LIMIT orders with guardrails.

binance_trade_cancelOrder

Cancels an order by symbol + orderId.

All tools return JSON payloads stringified for LLM consumption.

Environment variables

key

description

BINANCE_API_KEY

Required for account/trade tools (public tools work without).

BINANCE_API_SECRET

Required for account/trade tools.

BINANCE_BASE_URL

Defaults to https://api.binance.com (override for testnet).

BINANCE_RECV_WINDOW

RecvWindow in ms (default 5000).

BINANCE_TRADE_ENABLED

Set to false to disable trade tools entirely.

MCP_TRANSPORT

stdio (default) or http.

PORT

HTTP port when using MCP_TRANSPORT=http (default 8080).

Glama & Docker

  • glama.yaml / glama.json define build/start commands and required env vars.

  • Dockerfile builds a production image, exposes port 8080, and defaults to HTTP transport for inspection support.

License

Released under the MIT License (see LICENSE).

Available Tools

7 tools
binance_account_balancesB

Get account balances (requires API key & secret).

Inputs: no named parameters.

binance_account_openOrdersC

List open orders for a symbol.

Inputs: symbol (required).

binance_market_exchangeInfoB

Get exchange information including filters per symbol.

Inputs: no named parameters.

binance_market_klinesC

Get historical klines/candles for a symbol and interval.

Inputs: symbol (required), interval (required), limit.

binance_market_priceC

Get the latest price for a symbol (e.g. BTCUSDT).

Inputs: symbol (required).

binance_trade_cancelOrderC

Cancel a spot order by symbol and orderId.

Inputs: symbol (required), orderId (required).

binance_trade_placeOrderC

Place a spot order. Example: {symbol:'BTCUSDT', side:'BUY', type:'MARKET', quoteOrderQty:'50'}

Inputs: symbol (required), side (required), type (required), quantity, +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting different aspects of the Binance API: account balances, open orders, market data (exchange info, klines, price), and trade operations (place/cancel orders). There is no overlap or ambiguity between tools, making it easy for an agent to select the right one.

    Naming Consistency5/5

    All tools follow a consistent 'binance_<category>_<action>' naming pattern (e.g., binance_account_balances, binance_market_klines). This structured approach makes the tool set predictable and easy to understand, with no deviations in style or convention.

    Tool Count5/5

    With 7 tools, this server is well-scoped for its purpose of interacting with the Binance API. It covers essential areas like account management, market data, and trading without being overwhelming or too sparse, making each tool earn its place in the set.

    Completeness4/5

    The tool set provides strong coverage for core Binance operations, including account info, market data, and basic trading (place/cancel orders). A minor gap is the lack of tools for more advanced trading features like order history or portfolio management, but agents can still handle most common workflows effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      This server provides a robust interface for Binance spot trading operations, including secure management of API credentials, execution and management of spot orders, and monitoring of account balances and open orders.
      13
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Comprehensive Binance Futures trading MCP server with 41 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.
      88 PyPI
      4
      Python
      MIT