BNBChain MCP (Model Context Protocol)

What is BNBChain MCP?

BNBChain MCP is a Model Context Protocol (MCP) server that enables AI-powered interaction with BNB Chain and other EVM-compatible networks. It provides tools and resources for blockchain development, smart contract interaction, and network management through natural language.

How to use BNBChain MCP?

Install and configure with your MCP client (Cursor, Claude Desktop) by adding a JSON entry that runs npx -y @bnb-chain/mcp@latest with optional environment variables PRIVATE_KEY and BNBCHAIN_MCP_SKIP_TRANSFER_CONFIRMATION. For local development, clone the repo, install dependencies with bun install, and run bun dev:sse.

Key features of BNBChain MCP

• Query blocks, transactions, and native/ERC20 balances
• Transfer native tokens, ERC20, NFTs, and ERC1155 tokens
• Interact with smart contracts (read/write)
• Support for Greenfield file operations and ERC-8004 AI agent identities
• Preview-then-confirm flow for all transfer and payment tools
• Available as stdio or SSE transport

Use cases of BNBChain MCP

• Analyze an EVM address, block, or transaction through natural language prompts
• Transfer BNB, ETH, or ERC20 tokens with a confirmation step
• Check NFT ownership and retrieve token metadata
• Register and resolve on-chain AI agent identities (ERC-8004)
• Compare different EVM-compatible networks

FAQ from BNBChain MCP

How do I set up BNBChain MCP with Claude Desktop?

Open Claude Desktop Settings, go to Developer, click “Edit Config”, and add the JSON configuration with command: "npx" and args: ["-y", "@bnb-chain/mcp@latest"]. Optionally set PRIVATE_KEY and BNBCHAIN_MCP_SKIP_TRANSFER_CONFIRMATION in the env object.

How does the transfer confirmation flow work?

By default, calling a transfer or payment tool returns a preview with a short-lived confirmToken. No transaction is sent until you call confirm_transfer with that token and your private key. You can skip confirmation per call with skipConfirmation: true or server‑wide by setting BNBCHAIN_MCP_SKIP_TRANSFER_CONFIRMATION=true.

Is it safe to deploy this server publicly?

No. The SSE endpoint has no built‑in authentication, so anyone who can reach it can use the server. If public deployment is required, add an authentication layer (API keys, JWT, reverse proxy) or deploy a keyless version with only read‑only tools.

What are the system requirements?

You need Node.js v17 or higher and bun v1.2.10 or higher for local development. The server itself runs on any platform where Node.js is available.

Can I use BNBChain MCP with other clients besides Cursor and Claude Desktop?

Yes. The repository contains an examples directory that demonstrates how to set up an MCP client, authenticate, make API calls, and handle responses. You can integrate it into any custom client that supports the Model Context Protocol.