MegaETH tokens — LayerHop MCP Resource
MegaETH tokens
is one of 72 resources on the
LayerHop
MCP server. Connect the server and your client can attach it as context.
by client
How to attach MegaETH tokens from your client
- Claude Code LayerHop Resource/MegaETH tokens run in your project directory
- Claude Desktop LayerHop Resource/MegaETH tokens ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor LayerHop Resource/MegaETH tokens ~/.cursor/mcp.json
- VS Code LayerHop Resource/MegaETH tokens .vscode/mcp.json
- Zed LayerHop Resource/MegaETH tokens ~/.config/zed/settings.json
- Windsurf LayerHop Resource/MegaETH tokens ~/.codeium/windsurf/mcp_config.json
- Cline LayerHop Resource/MegaETH tokens ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI LayerHop Resource/MegaETH tokens ~/.gemini/settings.json
- Grok LayerHop Resource/MegaETH tokens .mcp.json (in your project root)
- ChatGPT LayerHop Resource/MegaETH tokens Settings → Connectors → Advanced → Developer mode
- Claude.ai LayerHop Resource/MegaETH tokens Settings → Connectors → Add custom connector
- LangChain LayerHop Resource/MegaETH tokens pip install langchain-mcp-adapters
Other resources on this server
- chains
- docs-llms-txt
- Ethereum tokens
- Base tokens
- Arbitrum tokens
- Solana tokens
- BNB Chain tokens
- Optimism tokens
- Polygon tokens
- Avalanche tokens
- Berachain tokens
- HyperEVM tokens
- Sonic tokens
- 0G Mainnet tokens
- Abstract tokens
- ApeChain tokens
- Arbitrum Nova tokens
- Arc tokens
- Blast tokens
- BOB tokens
- Boba Network tokens
- Celo tokens
- Cronos tokens
- Doma tokens
- Ethereal tokens
- Etherlink tokens
- Flare tokens
- Flow EVM tokens
- Fraxtal tokens
- FUSE tokens
- Gensyn tokens
- Gnosis tokens
- Gravity tokens
- Hemi tokens
- Immutable zkEVM tokens
- Injective tokens
- Ink tokens
- Kaia tokens
- Katana tokens
- Linea tokens
LayerHop also offers 1 prompt — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 18 October 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.