
MCP server for Web3 protocol documentation — EIPs, ERCs, BIPs, SIMDs, Cosmos ADRs, Polkadot RFCs
MCP server for Web3 protocol documentation — EIPs, ERCs, BIPs, SIMDs, Cosmos ADRs, Polkadot RFCs, contract registry
·
One MCP server, eleven protocol-spec repos. Ask your coding agent about EIPs, BIPs, ADRs, CIPs, RFCs and canonical contract addresses — without ever leaving your editor. Works with any MCP-compatible client: Claude Code, Cursor, Windsurf, Cline, Zed, Continue, OpenCode, Codex, and more.
Or replay in your own terminal: asciinema play docs/assets/demo.cast
Specs for blockchain protocols live across eleven different upstream repos on three different forges. Every time you need to look up EIP-4844, BIP-340, CIP-25, or which fork shipped PUSH0, you're tab-hunting through GitHub. This MCP indexes them all locally with FTS5 ranking — 1,767 proposals across 10 chains plus addresses for 19 protocols on Ethereum, Arbitrum, Base, Optimism, Polygon, and more — so your agent answers with the actual spec text, not a hallucinated paraphrase.
Requires: Python 3.11+ ·
uv(providesuvx) · ~500 MB free disk for the index ·giton PATH (used by--sync).
~/.cache/web3-docs-mcp/)uvx web3-docs-mcp --syncThe launch command is identical across clients:
uvx web3-docs-mcpclaude mcp add web3-docs -- uvx web3-docs-mcpAdd to the client's MCP config (~/.cursor/mcp.json, ~/.codeium/windsurf/mcp_config.json, cline_mcp_settings.json, the mcpServers block in your Zed settings.json, etc.):
{
"mcpServers": {
"web3-docs": {
"command": "uvx",
"args": ["web3-docs-mcp"]
}
}
}codex mcp add web3-docs -- uvx web3-docs-mcppip install web3-docs-mcp
# or:
pipx install web3-docs-mcpgit clone https://github.com/dioptx/web3-docs.git && cd web3-docs
uv sync
uv run python server.py --sync # build index
uv run python server.py # run stdio serverRestart your agent, then try "Use web3-docs to look up EIP-1559."
| Ask your agent… | Tool chain |
|---|---|
| "What's the fee market in EIP-4844?" | resolve_proposal → query_protocol_docs(query="fee") |
| "Show me Cosmos ADR-001." | resolve_proposal → query_protocol_docs |
| "What's in Cancun?" | list_fork_proposals("Cancun") |
| "Which BIPs activated with Taproot?" | list_fork_proposals("Taproot") |
| "Uniswap router on Base?" | resolve_contract(protocol="uniswap", chain_id="8453") |
| "Cardano CIP for native tokens?" | resolve_proposal("native tokens", chain="cardano") → cip-25 |
| "ERC-4337 EntryPoint address on Arbitrum?" | resolve_contract("erc4337", "42161") |
| "Staking on Cosmos vs Polkadot?" | resolve_proposal("staking", chain="cosmos") then chain="polkadot" |
Multi-chain canonical addresses, no etherscan tabs.
| Tool | What it does |
|---|---|
resolve_proposal(query, chain?) | Fuzzy-find a proposal by keyword, fork name, opcode, or ID. Returns top-5 ranked hits with chain/status/fork. Pass chain= (ethereum, bitcoin, cosmos, …) to disambiguate when keywords match multiple chains. |
query_protocol_docs(proposal_id, query?) | Read the full spec body. With query, returns only the most relevant sections (token-budgeted). Includes metadata header (status, fork, activation date, authors). |
list_fork_proposals(fork_name) | List every proposal activated by a named fork. Answers "what's in Cancun?" / "BIPs activated with Taproot?". Handles aliases (Pectra → Prague, Dencun → Cancun, Shapella → Shanghai, The Merge → Paris). |
resolve_contract(protocol, chain_id?) | Look up canonical deployed addresses. 19 protocols × major EVM chains. Omit chain_id for all chains. |
Fork → all proposals it shipped, then drill into one. Two tool calls instead of an afternoon of tab-hunting.
11 upstream repos, all synced via --sync:
| Chain | Source |
|---|---|
| Ethereum (EIPs) | ethereum/EIPs |
| Ethereum (ERCs) | ethereum/ERCs |
| Bitcoin | bitcoin/bips |
| Solana | solana-foundation/solana-improvement-documents |
| Cosmos | cosmos/cosmos-sdk (docs/architecture) |
| Polkadot | polkadot-fellows/RFCs |
| Stacks | stacksgov/sips |
| Avalanche | avalanche-foundation/ACPs |
| Cardano | cardano-foundation/CIPs |
| Tezos | tezos/tzip |
| Sui | sui-foundation/sips |
Fork mappings come from ethereum/execution-specs plus canonical Bitcoin soft-fork activations (P2SH, SegWit, Taproot, …).
Contract registry covers: aave, across, chainlink, compound, create2_deployer, curve, ens, erc4337, gnosis_safe, lido, maker, multicall, oneinch, permit2, seaport, uniswap, usdc, usdt, weth.
…just gh search or WebFetch each spec on demand? You'd burn tokens on HTML markup and pay a network round-trip per query. web3-docs indexes everything once into local SQLite + FTS5 — sub-millisecond ranked search, plain-text bodies, no rate limits, works offline.
…one MCP per chain? You'd manage eleven separate servers and your agent wouldn't know which to call. One unified tool with a single resolve_proposal entry point lets the model find the right doc by concept (e.g. "blob transactions" → eip-4844) rather than guessing the source.
…ask the model directly without an MCP? Models hallucinate spec details — wrong fork, wrong gas costs, wrong opcode numbers. This server returns the actual upstream text with metadata (status, fork, activation date) so the agent can quote it verbatim.
…use a vector DB? Spec corpora are small (≈ 1.7K docs), domain vocabulary is precise (PUSH0, BLOBHASH, taproot), and exact-term matching beats embeddings here. FTS5 gives BM25 ranking with zero infrastructure.
| Env var | Default | Purpose |
|---|---|---|
WEB3_DOCS_DATA_DIR | ~/.cache/web3-docs-mcp (macOS/Linux) | Where source repos and the SQLite index live |
"Index is empty" on any tool call. You haven't run --sync yet. Run:
uvx web3-docs-mcp --syncuvx: command not found. Install uv: curl -LsSf https://astral.sh/uv/install.sh | sh.
Want to free disk space? Source repos (~/.cache/web3-docs-mcp/repos/) can be deleted after sync; only proposals.db is needed at runtime. Re-run --sync to update.
Stale data? Re-run --sync — it does a fast git pull and reindexes incrementally.
git clone https://github.com/dioptx/web3-docs.git && cd web3-docs
uv sync --extra test
uv run pytest # 98 tests, BDD + unit
uv build # build wheel + sdistv0.2.0 — adds Cardano CIPs, Tezos TZIPs, Sui SIPs (10 chains, 1,767 proposals). SQLite + FTS5, FastMCP stdio transport. See CHANGELOG.md for release history.
MIT — see LICENSE.
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add web3-docs -- uvx web3-docs-mcp{
"mcpServers": {
"web3-docs": {
"args": [
"web3-docs-mcp"
],
"command": "uvx"
}
}
}code --add-mcp '{"name":"web3-docs","args":["web3-docs-mcp"],"command":"uvx"}'[mcp_servers.web3-docs]
command = "uvx"
args = ["web3-docs-mcp"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/web3-docs to learn what the "Web3 Docs" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
uvx web3-docs-mcp --sync
uvx web3-docs-mcpclaude mcp add web3-docs -- uvx web3-docs-mcppip install web3-docs-mcppipx install web3-docs-mcpThis server runs locally, so we can't read its tool list over the web yet.
We could not run this server: it ships no npx package for our sandbox and no public endpoint. The four checks that need a live server are left out, and the grade tops out at B until one exists.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/web3-docs)Nothing comparable is listed yet.
v0.2.0v0.2.0 — Cardano · Tezos · Sui · fork lookupRelease notesConnect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "web3-docs" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.