Skip to content
Binance

BinanceMCP Server

by Binance
Released
Docs
Payments & Commerce

Summary

Binance's official MCP server, part of Agent OS — spot and futures trading, live market data and account access, with per-agent permissions and funding limits.

Features

  • Spot and futures trading, order books, price feeds, balances and positions
  • HTTP transport at https://agent.binance.com/mcp/agentic
  • Browser-redirect authorisation — no Binance API keys stored locally
  • Per-agent feature toggles and funding limits, scoped through Sub Accounts
  • Disconnect and emergency stop available at any time

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Binance" tools will be available.
{
  "mcpServers": {
    "binance-mcp": {
      "command": "claude",
      "args": [
        "mcp",
        "add",
        "binance-mcp-server",
        "--transport",
        "http",
        "https://agent.binance.com/mcp/agentic"
      ]
    }
  }
}

Description

Announced on 20 August 2026 alongside Binance Agent OS, this is the exchange's own MCP server: a connection layer between MCP-compatible clients and Binance trading, market data and account functions.

Connecting

HTTP transport against https://agent.binance.com/mcp/agentic:

claude mcp add binance-mcp-server --transport http https://agent.binance.com/mcp/agentic

Binance lists Claude Code, Cursor, Codex, ChatGPT and self-built agents as supported clients.

Authorisation — the notable part

You do not store Binance API keys locally. Authentication runs through a browser redirect against your Binance account, where you select the agent and set granular permissions: per-feature toggles and funding limits, scoped through Sub Accounts. Access stays manageable from Sub Accounts settings, with disconnect and an emergency stop available at any time.

For a surface where a mistaken tool call moves real money, that consent model — explicit scopes, spending caps and a kill switch, rather than a long-lived key in a config file — is the thing to evaluate before the tool list.

Current scope

Spot and futures trading, live market data (order books and price feeds), account access (balances and positions), and trading analysis. Onchain transactions and machine-to-machine payments exist elsewhere in Agent OS, with MCP support for them stated as planned.

A caution

This server can place trades with real funds. Set funding limits and feature toggles deliberately before connecting an autonomous agent, and treat market data from any source as untrusted input to a model that can act on it.

Related MCP Servers

MCP: Xero MCP Server

by Xero

New

Official Xero MCP server that lets an agent read and write a real accounting ledger — invoices, contacts, payments, payroll timesheets and financial reports — over the Xero API.

Payments & Commerce
1 views

MCP: Ramp

by Ramp

New

Ramp's official remote MCP server for corporate spend — read transactions, bills and reimbursements, and with the right role edit, approve and lock cards.

Payments & Commerce

MCP: Adyen MCP Server

by Adyen

New

Adyen's official MCP server (alpha) — create checkout sessions and payment links, refund or cancel payments, and manage merchant accounts and terminals.

Payments & Commerce
2 views
Browse all MCP servers →