This MCP server exposes Ethereum and other EVM-compatible networks to AI agents via the Model Context Protocol, enabling natural language queries to retrieve on-chain data. It supports multi-chain access, balance checks, contract detection, and gas price monitoring across Ethereum, Base, Arbitrum, Avalanche, and Binance Smart Chain. Once the server is running, you can interact with it through MCP-enabled tools in your VS Code environment, asking questions like: What is the balance of a given address on Ethereum? Is a particular address a contract or an externally owned account? What are the current gas prices on Arbitrum? The server translates these requests into RPC calls to your configured providers and returns structured results suitable for AI planning and reasoning. By configuring QuickNode or other RPC endpoints in your environment, you enable real-time blockchain data access for AI agents within your development workflow.

Prerequisites:

• Node.js 18.x or higher
• npm or pnpm
• VS Code with MCP support
• RPC endpoints (e.g., QuickNode) or other Ethereum-compatible RPC providers

Installation steps:

1. Clone the repository
2. Install dependencies: npm install

   or

   pnpm install
3. Create a .env file (as described in the Configuration section) and populate RPC endpoints and credentials
4. Build the project (if required by the repository structure): npm run build

   or

   pnpm build
5. Start the server: npm start

   or

   pnpm start
6. Ensure the MCP server is reachable by your VS Code MCP setup and verify the environment variables are correctly loaded

Note: If your project has a different entry point, adjust the node command in mcp_config accordingly and point args to the actual server startup script.

Tips and common issues:

• Ensure your RPC endpoints (QN_ENDPOINT_NAME, QN_TOKEN_ID, and optional ETHEREUM_RPC, BASE_RPC, ARBITRUM_RPC, AVALANCHE_RPC, BSC_RPC) are correctly set in the .env file. Missing credentials will prevent blockchain access.
• If you see authentication or rate-limit errors from your RPC provider, consider upgrading your plan or adding additional RPC endpoints to distribute load.
• The server is designed to work with VS Code's MCP extension; make sure the extension is installed and configured to connect to the MCP server at the correct URL/port.
• When testing, start with a single chain (e.g., Ethereum) to verify balance, contract detection, and gas price queries before enabling multi-chain support.
• The available tools documented in the README (e.g., eth_getBalance, eth_getCode, eth_gasPrice) map to on-chain RPC calls. Ensure your client sends the expected JSON payloads as shown in the examples.
• If you encounter build issues, ensure your Node.js version matches the repository's stated prerequisites and reinstall dependencies.

Environment variables:

• QN_ENDPOINT_NAME: QuickNode endpoint name
• QN_TOKEN_ID: QuickNode token id
• ETHEREUM_RPC, BASE_RPC, ARBITRUM_RPC, AVALANCHE_RPC, BSC_RPC: optional RPC URLs for additional networks