etherscan-explorer-dashboard — Etherscan MCP Resource
etherscan-explorer-dashboard
is one of 1 resource on the
Etherscan
MCP server. Connect the server and your client can attach it as context.
by client
How to attach etherscan-explorer-dashboard from your client
- Claude Code Etherscan Resource/etherscan-explorer-dashboard run in your project directory
- Claude Desktop Etherscan Resource/etherscan-explorer-dashboard ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Etherscan Resource/etherscan-explorer-dashboard ~/.cursor/mcp.json
- VS Code Etherscan Resource/etherscan-explorer-dashboard .vscode/mcp.json
- Zed Etherscan Resource/etherscan-explorer-dashboard ~/.config/zed/settings.json
- Windsurf Etherscan Resource/etherscan-explorer-dashboard ~/.codeium/windsurf/mcp_config.json
- Cline Etherscan Resource/etherscan-explorer-dashboard ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Etherscan Resource/etherscan-explorer-dashboard ~/.gemini/settings.json
- Grok Etherscan Resource/etherscan-explorer-dashboard .mcp.json (in your project root)
- ChatGPT Etherscan Resource/etherscan-explorer-dashboard Settings → Connectors → Advanced → Developer mode
- Claude.ai Etherscan Resource/etherscan-explorer-dashboard Settings → Connectors → Add custom connector
- LangChain Etherscan Resource/etherscan-explorer-dashboard pip install langchain-mcp-adapters
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.