⛽ EVM MCP Server

Complete EVM JSON-RPC access in your AI workflow. Query any EVM-compatible network (Ethereum, Polygon, Arbitrum, Optimism, BSC, and more) through any node provider. Works with Infura, Alchemy, QuickNode, local nodes, and more.

An MCP (Model Context Protocol) server that provides comprehensive access to Ethereum Virtual Machine (EVM) JSON-RPC methods for AI coding environments like Cursor and Claude Desktop.

Why Use EVM MCP?

• 🌐 Any EVM Network – Ethereum, Polygon, Arbitrum, Optimism, BSC, Avalanche, and more
• 🔌 Any Node Provider – Infura, Alchemy, QuickNode, local nodes, or custom RPC
• 📊 20+ RPC Methods – Complete access to blockchain data, transactions, and contracts
• ⚡ Easy Setup – One-click install in Cursor or simple manual setup
• 🔧 Flexible Configuration – Works with any JSON-RPC compatible endpoint

Quick Start

Ready to interact with EVM blockchains? Install in seconds:

Install in Cursor (Recommended):

🔗 Install in Cursor

Or install manually:

npm install -g @jamesanz/evm-mcp
# Or from source:
git clone https://github.com/JamesANZ/evm-mcp.git
cd evm-mcp && npm install && npm run build

Features

🔢 Blockchain Data

• eth_blockNumber – Get latest block number
• eth_getBalance – Get account balance
• eth_getTransactionCount – Get transaction count (nonce)
• eth_getBlockByNumber – Get block information
• eth_getTransactionByHash – Get transaction details
• eth_getTransactionReceipt – Get transaction receipt
• eth_getCode – Get contract bytecode
• eth_getStorageAt – Get storage value

🔄 Transactions

• eth_call – Execute contract call
• eth_estimateGas – Estimate gas for transaction
• eth_sendRawTransaction – Send signed transaction
• eth_gasPrice – Get current gas price

🧪 Transaction Simulation (read-only, never broadcasts)

Craft transactions in natural language and simulate them against forked/overridden EVM state. Reports whether a transaction would succeed or revert, the revert reason in plain English, estimated gas, and balance/state changes. Supports address aliases and ENS names (e.g. alice.eth). By default the sender is funded with virtual ETH so a simulation can run "from" any address; set fund: false to use real balances.

• simulate_native_transfer – Simulate sending native currency (e.g. "Transfer 100 ETH from A to B")
• simulate_erc20_transfer – Simulate an ERC20 transfer with human amounts (e.g. "Transfer 10 USDC to alice.eth from fun.eth")
• simulate_contract_call – Encode a function signature + args and simulate the call
• simulate_transaction – Simulate a raw transaction (from/to/value/data)
• encode_function_data – Encode calldata from a human-readable signature (pure helper, no RPC)

These tools only use eth_call, eth_estimateGas, and debug_traceCall (when the provider supports it). They never sign or send a real transaction. Real state diffs are used when debug_traceCall is available; otherwise changes are inferred from the decoded intent.

📊 Events & Logs

• eth_getLogs – Get event logs

🌍 Network

• list_supported_networks – List configured networks and providers
• list_known_addresses – List configured wallet aliases and known token/contract addresses
• eth_chainId – Get chain ID
• net_version – Get network version
• net_listening – Check if listening
• net_peerCount – Get peer count

🌐 Web3

• web3_clientVersion – Get client version
• web3_sha3 – Hash data with Keccak-256

Installation

Cursor (One-Click)

Click the install link above or use:

cursor://anysphere.cursor-deeplink/mcp/install?name=evm-mcp&config=eyJldm0tbWNwIjp7ImNvbW1hbmQiOiJucHgiLCJhcmdzIjpbIi15IiwiQGphbWVzYW56L2V2bS1tY3AiXX19

Manual Installation

Requirements: Node.js 18+ and npm

# Clone and build
git clone https://github.com/JamesANZ/evm-mcp.git
cd evm-mcp
npm install
npm run build

# Set provider API keys
export INFURA_API_KEY="your-infura-api-key"
export DEFAULT_NETWORK="ethereum"
export DEFAULT_PROVIDER="infura"

# Run server
npm start

Claude Desktop

Add to claude_desktop_config.json:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "evm-mcp": {
      "command": "node",
      "args": ["/absolute/path/to/evm-mcp/build/index.js"],
      "env": {
        "INFURA_API_KEY": "your-infura-api-key",
        "DEFAULT_NETWORK": "ethereum",
        "DEFAULT_PROVIDER": "infura",
        "RPC_PROVIDER_ORDER": "infura,alchemy"
      }
    }
  }
}

Restart Claude Desktop after configuration.

Configuration

Environment Variables

*At least one provider API key, custom provider, or custom network with rpcUrl is required.

Built-in Providers (Infura / Alchemy)

Set an API key and the server builds RPC URLs automatically for supported networks:

{
  "INFURA_API_KEY": "your-infura-key",
  "DEFAULT_NETWORK": "ethereum",
  "DEFAULT_PROVIDER": "infura",
  "RPC_PROVIDER_ORDER": "infura,alchemy"
}

Each RPC tool accepts an optional network parameter (slug, name, or chain ID). When omitted, DEFAULT_NETWORK is used.

{
  "tool": "eth_chainId",
  "arguments": { "network": "polygon" }
}

Use list_supported_networks to discover configured networks and providers.

Custom Providers (CUSTOM_PROVIDERS)

Register any RPC provider by supplying a base URL template and network-specific URLs:

"CUSTOM_PROVIDERS": "[{\"slug\":\"quicknode\",\"apiKeyEnv\":\"QUICKNODE_API_KEY\",\"baseUrl\":\"https://rpc.example.com/v1/{apiKey}\",\"networkUrls\":{\"ethereum\":\"https://eth.quiknode.pro/{apiKey}/\",\"polygon\":\"https://polygon.quiknode.pro/{apiKey}/\"}}]"

• Absolute networkUrls values are used directly (with {apiKey} substitution).
• Relative paths (starting with /) are appended to baseUrl.

Custom Networks (CUSTOM_NETWORKS)

Register arbitrary chains by name:

"CUSTOM_NETWORKS": "[{\"name\":\"HyperEVM\",\"slug\":\"hyperevm\",\"chainId\":999,\"rpcUrl\":\"https://rpc.hyperliquid.xyz/evm\"}]"

Or route through a provider by setting provider and adding the network slug to that provider's networkUrls.

Known Addresses (KNOWN_ADDRESSES)

Register tokens and contracts by name so tools accept aliases like USDC instead of raw hex addresses. Each entry is scoped to a network:

"KNOWN_ADDRESSES": "[{\"name\":\"USDC\",\"address\":\"0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48\",\"network\":\"ethereum\",\"type\":\"token\",\"decimals\":6,\"aliases\":[\"usd-coin\"]}]"

When eth_getBalance is called with a token alias, the server uses the first configured wallet in WALLET_ADDRESSES as the token holder.

Wallet Addresses (WALLET_ADDRESSES)

Register personal wallets and contracts by alias so you can say "check my personal wallet" instead of pasting hex:

"WALLET_ADDRESSES": "[{\"name\":\"my-wallet\",\"address\":\"0x42ea529282DDE0AA87B42d9E83316eb23FE62c3f\",\"aliases\":[\"personal\",\"my wallet\"],\"description\":\"Main EOA\"}]"

Address aliases work in eth_getBalance, eth_getCode, eth_call, eth_getLogs, and other tools that accept address parameters. Use list_known_addresses to discover configured aliases.