Skip to content

Model Context Protocol (MCP)

The Model Context Protocol is an open interface that lets AI agents and developer tools share a rich execution context. In practice, that means you can:

  • Ask natural‑language questions about on‑chain data or documentation.
  • Invoke blockchain‑aware tools (read‑only or state‑changing) without manual RPC calls.
  • Plug the same back‑end into multiple IDEs, CLIs or chat front‑ends.

Why use it? Unified access – instantly switch between chat, code, and terminal workflows. Extensibility – add your own prompts & tools. Open source – fork, self‑host, or just npx it.

1 Available MCP servers

Name Endpoint / Install Scope Typical usage
bnbchain‑mcp npx @bnb-chain/mcp@latest
or self-host via Docker		 Full toolkit: blocks, txs, wallets, Greenfield ops & more Build, test, or automate on-chain actions from your IDE or scripts.
ask‑ai‑mcp https://mcp.inkeep.com/bnbchainorg/mcp Read-only semantic search over BNB Chain docs, BEPs, blogs & FAQs Quick answers in chat panes or command palettes.

Both servers speak the same MCP schema, so you can swap them in your settings with a single JSON change.

2 What can MCP do?

Conversational queries

What is BEP‑20 and how does it differ from ERC‑20?

Answer arrives instantly with source links.

Tool execution (bnbchain‑mcp only)

get_block_by_number number=37000000 chain=bsc

Returns structured JSON for the requested block. Supply a PRIVATE_KEY to unlock write‑capable tools such as transfer_erc20 or write_contract.

IDE‑agnostic integration

  • VS Code, Cursor, JetBrains: add a servers.mcp entry in settings → choose the agent in your chat panel.
  • Terminal lovers: curl or your favourite HTTP client.
  • Custom apps: import @bnb-chain/mcp as a library.

Have questions? Join #ai‑tooling on Discord or open a GitHub issue. PRs welcome!