dioptx/web3-docs

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
## Why
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.
## Install
> Requires: Python 3.11+ · uv (provides uvx) · ~500 MB free disk for the index · git on PATH (used by --sync).
### Step 1 — build the index (one-time, ~2 min, ~500 MB in ~/.cache/web3-docs-mcp/)
bash
uvx web3-docs-mcp --sync
### Step 2 — register the server with your agent
The launch command is identical across clients:
text
uvx web3-docs-mcp
Claude Code
bash
claude mcp add web3-docs -- uvx web3-docs-mcp
Cursor · Windsurf · Cline · Continue · Zed · generic stdio MCP client
Add to the client's MCP config (~/.cursor/mcp.json, ~/.codeium/windsurf/mcpconfig.json, clinemcpsettings.json, the mcpServers block in your Zed settings.json, etc.):
json
"mcpServers": {
"web3-docs": {
"command": "uvx",
"args": ["web3-docs-mcp"]
OpenAI Codex CLI
bash
codex mcp add web3-docs -- uvx web3-docs-mcp
pip / pipx
bash
pip install web3-docs-mcp
# or:
pipx install web3-docs-mcp
From source (development)
bash
git 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 server
Restart your agent, then try "Use web3-docs to look up EIP-1559."
## What you can ask
| Ask your agent… | Tool chain |
| "What's the fee market in EIP-4844?" | resolveproposal → queryprotocoldocs(query="fee") |
| "Show me Cosmos ADR-001." | resolveproposal → queryprotocoldocs |
| "What's in Cancun?" | listforkproposals("Cancun") |
| "Which BIPs activated with Taproot?" | listforkproposals("Taproot") |
| "Uniswap router on Base?" | resolvecontract(protocol="uniswap", chainid="8453") |
| "Cardano CIP for native tokens?" | resolveproposal("native tokens", chain="cardano") → cip-25 |
| "ERC-4337 EntryPoint address on Arbitrum?" | resolvecontract("erc4337", "42161") |
| "Staking on Cosmos vs Polkadot?" | resolveproposal("staking", chain="cosmos") then chain="polkadot" |
Multi-chain canonical addresses, no etherscan tabs.
## Tools
| Tool | What it does |
| resolveproposal(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. |
| queryprotocoldocs(proposalid, query?) | Read the full spec body. With query, returns only the most relevant sections (token-budgeted). Includes metadata header (status, fork, activation date, authors). |