Bnbchain Mcp

This connects Claude to BNB Chain's MCP server so you can query blocks, check balances, deploy contracts, and send transactions directly from conversation. It covers the full stack: EVM reads and writes, ERC20 and NFT operations, ERC-8004 agent registration (so your MCP server can register itself on-chain), and BNB Greenfield storage tools. You'll need a private key in the server environment for anything that changes state, but reads work fine without one. The skill is clear about one critical thing: writes require an explicit network parameter because defaulting to mainnet risks irreversible mistakes. Built on npx @bnb-chain/mcp, so no local installation needed.

skills.sh installs: 348
GitHub stars: 65
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add bnb-chain/bnbchain-skills --skill bnbchain-mcp --agent claude-code

Installs into .claude/skills of the current project.

Files

BNB Chain MCP Skill

How to connect to the BNB Chain MCP server and use its tools: blocks, transactions, contracts, tokens, NFTs, wallet, ERC-8004 agents, and Greenfield. Use this skill when working with BNB Chain / opBNB / EVM or Greenfield via MCP.

Connection and credentials

Run the server: npx @bnb-chain/mcp@latest (fetches from npm at runtime). Source: github.com/bnb-chain/bnbchain-mcp.
RPC: Default chains use built-in RPC; no config unless self-hosting or custom RPC.
PRIVATE_KEY: Omit or leave empty for read-only (blocks, balances, contract reads). Set in the MCP server env for state-changing tools (transfers, write_contract, approve_token_spending, ERC-8004 register/set_uri, Greenfield writes). Never log or expose private keys.
Read-only vs state-changing: Block/balance/contract-read tools work without a key; transfers and writes require PRIVATE_KEY in the server environment.