Skip to main content
The Docs MCP server lets an AI agent search and read this documentation, so it can find the right endpoint, its parameters, and an example before writing code or making a call. It is the knowledge counterpart to the Etherscan MCP: one answers questions about the API, the other returns live onchain data.
Docs MCP is for AI agents that search these docs while they build. No API key is needed, since it only reads public documentation.

Connection details

Point your MCP client at the server with these values. For guided, per-client setup, see Get started below.
  • Transport: Streamable HTTP.
  • Authentication: none. The server reads only public documentation.

Get started

Pick your client below and follow it end to end.
Claude Desktop is Anthropic’s desktop chat app.
1

Add Docs MCP to your config

In Claude Desktop, open Settings > Developer > Edit Config to open the claude_desktop_config.json file.
Claude Desktop Settings > Developer, showing the Edit Config button
In the file that opens, add the etherscan-docs server:
claude_desktop_config.json
Requires Node.js.
2

Confirm it's connected

Save, then fully quit Claude Desktop and reopen it. Open Settings > Developer and look for etherscan-docs under Local MCP servers with a running badge.
Claude Desktop Settings > Developer showing the etherscan-docs MCP server with a running badge
3

Ask the docs

Ask a documentation question and let the agent search these pages:
It calls search_etherscan to find the account module’s addresstokenbalance action, reads its parameters and example, and answers with the correct request shape instead of guessing.
Claude Desktop answering a documentation question via the Etherscan Docs MCP, citing the addresstokenbalance action

Example prompts

Ask a documentation question and let the agent search these pages. Copy one to try it:

Tools

The server exposes 3 tools. The agent selects and calls them for you.

Good to know

  • No API key. The server reads only public documentation, so no key or auth header is needed.
  • Read-only, with one exception. The search and query tools only read the docs. submit_feedback sends a report to the docs team. Nothing else writes.
  • Pair it with the data tools. The Docs MCP finds the right call. The Etherscan MCP or CLI makes it.
  • Guard against prompt injection. Enable your client’s confirmation prompts, and be cautious when combining Docs MCP with other MCP servers in the same session.
No MCP client? You can point an agent at any docs page in Markdown by appending .md to its URL, or load the llms.txt index, with the complete export at llms-full.txt.