web3-docs
Provides access to Bitcoin Improvement Proposals (BIPs), enabling searches and retrieval of spec texts for proposals like BIP-340, and listing proposals activated by forks such as Taproot.
Integrates Cardano Improvement Proposals (CIPs), allowing queries about proposals like CIP-25 for native tokens and retrieval of their full spec bodies.
Offers canonical contract address lookups for Chainlink on multiple EVM chains, including Ethereum, Arbitrum, Base, and Optimism.
Provides access to Ethereum Improvement Proposals (EIPs) and ERCs, enabling searches for proposals like EIP-1559, EIP-4844, and listing all proposals activated by specific forks (e.g., Cancun, Pectra).
Supports querying of canonical contract addresses for protocols like Uniswap, USDC, and others on Optimism, alongside general proposal search across the web3-docs index.
Integrates Polkadot RFCs, allowing searches for proposals such as staking-related RFCs and retrieval of their specification texts.
Provides canonical contract address lookups for protocols on Polygon, including Aave, Uniswap, Chainlink, and others.
Integrates Solana Improvement Documents (SIPs), enabling searches for proposals and retrieval of spec content.
Offers access to Sui Improvement Proposals (SIPs), allowing searches and retrieval of proposal details.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@web3-docslook up EIP-1559"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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(providesuvx) · ~500 MB free disk for the index ·giton PATH (used by--sync).
Step 1 — build the index (one-time, ~2 min, ~500 MB in ~/.cache/web3-docs-mcp/)
uvx web3-docs-mcp --syncStep 2 — register the server with your agent
The 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."
What you can ask
Ask your agent… | Tool chain |
"What's the fee market in EIP-4844?" |
|
"Show me Cosmos ADR-001." |
|
"What's in Cancun?" |
|
"Which BIPs activated with Taproot?" |
|
"Uniswap router on Base?" |
|
"Cardano CIP for native tokens?" |
|
"ERC-4337 EntryPoint address on Arbitrum?" |
|
"Staking on Cosmos vs Polkadot?" |
|

Multi-chain canonical addresses, no etherscan tabs.
Tools
Tool | What it does |
| Fuzzy-find a proposal by keyword, fork name, opcode, or ID. Returns top-5 ranked hits with chain/status/fork. Pass |
| Read the full spec body. With |
| 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). |
| Look up canonical deployed addresses. 19 protocols × major EVM chains. Omit |

Fork → all proposals it shipped, then drill into one. Two tool calls instead of an afternoon of tab-hunting.
Sources
11 upstream repos, all synced via --sync:
Chain | Source |
Ethereum (EIPs) | |
Ethereum (ERCs) | |
Bitcoin | |
Solana | |
Cosmos |
|
Polkadot | |
Stacks | |
Avalanche | |
Cardano | |
Tezos | |
Sui |
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.
Why not …
…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.
Configuration
Env var | Default | Purpose |
|
| Where source repos and the SQLite index live |
Troubleshooting
"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.
Development
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 + sdistStatus
v0.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.
License
MIT — see LICENSE.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dioptx/web3-docs'
If you have feedback or need assistance with the MCP directory API, please join our Discord server