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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbnbchain-mcpExecute the skills CLI command in your project's root directory to begin installation:
Fetches bnbchain-mcp from bnb-chain/bnbchain-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate bnbchain-mcp. Access via /bnbchain-mcp in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
60
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
60
stars
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.
npx @bnb-chain/mcp@latest (fetches from npm at runtime). Source: github.com/bnb-chain/bnbchain-mcp.env for state-changing tools (transfers, write_contract, approve_token_spending, ERC-8004 register/set_uri, Greenfield writes). Never log or expose private keys.PRIVATE_KEY in the server environment.Add the bnbchain-mcp server to the MCP client config (e.g. Cursor MCP settings, Claude Desktop claude_desktop_config.json).
Default (stdio):
{
"mcpServers": {
"bnbchain-mcp": {
"command": "npx",
"args": ["-y", "@bnb-chain/mcp@latest"],
"env": {
"PRIVATE_KEY": ""
}
}
}
}
SSE mode: "args": ["-y", "@bnb-chain/mcp@latest", "--sse"] (and client SSE URL if required). Local dev server (e.g. bun dev:sse in bnbchain-mcp): "url": "http://localhost:3001/sse" with the same env.
Restart or reload the MCP client after changing config so the server starts.
env when state-changing tools are needed; leave empty for read-only. Do not commit or echo keys.register_erc8004_agent (see references/erc8004-tools-reference.md).network is optional; default is bsc. Use get_supported_networks to list options.transfer_native_token, transfer_erc20, transfer_nft, transfer_erc1155, approve_token_spending, write_contract, register_erc8004_agent, set_erc8004_agent_uri, Greenfield writes): network is REQUIRED. There is no default for writes. If the user does not specify the network, you MUST ask before calling the tool. Do not assume or default to mainnet (bsc); accidental mainnet execution causes irreversible financial loss.| Category | Examples | Needs PRIVATE_KEY? |
|---|---|---|
| Blocks | get_latest_block, get_block_by_number, get_block_by_hash |
No |
| Transactions | get_transaction, get_transaction_receipt, estimate_gas |
No (estimate only) |
| Network | get_chain_info, get_supported_networks |
No |
| Wallet / balance | get_native_balance, get_erc20_balance, get_address_from_private_key |
Balance: optional address or privateKey |
| Transfers / writes | transfer_native_token, transfer_erc20, transfer_nft, transfer_erc1155, approve_token_spending, write_contract |
Yes |
| Contracts | read_contract, is_contract |
No for read |
| Tokens / NFT | get_erc20_token_info, get_nft_info, get_erc1155_token_metadata, check_nft_ownership, get_nft_balance, get_erc1155_balance |
No for read |
| ERC-8004 | register_erc8004_agent, set_erc8004_agent_uri, get_erc8004_agent, get_erc8004_agent_wallet |
Register/set_uri: Yes |
| Greenfield | gnfd_* bucket/object/payment tools |
Writes: Yes |
Use the MCP prompt names when the user wants analysis or guidance:
For parameter names, examples, and detailed usage of each tool, use:
| Reference | Content |
|---|---|
| references/evm-tools-reference.md | Blocks, transactions, network, wallet, contracts, tokens, NFT — all EVM tools |
| references/erc8004-tools-reference.md | register_erc8004_agent, set_erc8004_agent_uri, get_erc8004_agent, get_erc8004_agent_wallet |
| references/greenfield-tools-reference.md | Buckets, objects, folders, payment accounts — all Greenfield tools |
| references/prompts-reference.md | All MCP prompts and when to use them |
transfer_*, write_contract, or approve_token_spending, confirm recipient, amount, and network before calling the tool.write_contract, approve_token_spending, ERC-8004 register/set_uri), you MUST have an explicit network from the user. If not specified, ask — do not default to mainnet. Do not use advisory language like "prefer testnet" as a substitute; the constraint is: no network specified → do not call the write tool until the user confirms.env; never in chat or logs.npx @bnb-chain/mcp@latestPrerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
aradotso/trending-skills
davila7/claude-code-templates
intellectronica/agent-skills
am-will/codex-skills
sickn33/antigravity-awesome-skills
myzy-ai/dokie-ai-ppt
bnbchain-mcp reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: bnbchain-mcp is focused, and the summary matches what you get after install.
bnbchain-mcp has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend bnbchain-mcp for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: bnbchain-mcp is the kind of skill you can hand to a new teammate without a long onboarding doc.
bnbchain-mcp reduced setup friction for our internal harness; good balance of opinion and flexibility.
bnbchain-mcp is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend bnbchain-mcp for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added bnbchain-mcp from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
bnbchain-mcp fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 41