Practical overview
When it fits
Use WEB3 Docs when protocol research or a supported contract-address lookup needs to happen through an MCP-compatible coding assistant, after building its local index.
Who it is for
- Blockchain developers using MCP-compatible coding assistants
- Developers who need to consult protocol proposals or fork contents while working in an editor
- Developers looking up canonical addresses for supported protocols on EVM chains
Documented uses
- Find a proposal by identifier, topic, fork name or opcode, with an optional chain filter.
- Read a full protocol specification or retrieve relevant sections for a query.
- List proposals activated by a named fork, including supported fork aliases.
- Look up a supported protocol’s canonical deployed address, optionally for a specific chain ID.
Requirements & limits
The repository is public and MIT-licensed. The documented local setup requires Python 3.11 or later, uv, about 500 MB of free disk space and Git on PATH for synchronization.
- The server uses MCP stdio transport, so the coding assistant must support MCP.
- The local index must be built with
--syncbefore lookup tools can return data. - The index is drawn from 11 upstream repositories; address coverage is for a documented set of protocols and major EVM chains.
- SQLite with FTS5 ranking powers the local index.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up WEB3 Docs in an MCP coding assistant
Build the local protocol index and register the server with an MCP-compatible client.
Before you start
- Python 3.11 or later
- uv, which provides uvx
- About 500 MB of free disk space for the index
- Git on PATH for synchronization
- An MCP-compatible coding assistant
Steps
Build the local index with
uvx web3-docs-mcp --sync.Register
uvx web3-docs-mcpas an MCP server in the client configuration; the README provides client-specific examples for Claude Code, Codex CLI and several stdio MCP clients.Restart the assistant and ask it to use web3-docs for a protocol lookup.
Expected outcome
The assistant can access WEB3 Docs’ proposal, specification, fork and contract-address lookup tools.
Guide limitations
- The initial index is approximately 500 MB and is stored under
~/.cache/web3-docs-mcp/by default on macOS and Linux. - The index must be built before lookup tools can return data; rerun
--syncto update it.
Compare options for AI coding assistance
These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.
| Project | Documented purpose | Platform | Access and requirements |
|---|---|---|---|
| WEB3 Docs | Find a proposal by identifier, topic, fork name or opcode, with an optional chain filter. | CLI, Self-hosted, Server | The repository is public and MIT-licensed. The documented local setup requires Python 3.11 or later, uv, about 500 MB of free disk space and Git on PATH for synchronization. |
| Overture | Inspect a coding agent’s planned steps and branches before code is written. | Self-hosted, Server, Web | Open-source software under the MIT license. The documented setup runs the MCP server locally and opens its web interface at `http://localhost:3031` by default. |
| Wigolo | Search the web and fetch pages for an agent’s research task. | CLI, Self-hosted, Server | The quickstart lists macOS, Linux and Windows, and requires Node.js 20 or later with about 1.5 GB of free disk space. The repository labels the project public beta. |
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 14 October 2026
- Original website title
- dioptx/web3-docs · Official homepage title · retained in its source language

