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.
- 🌐 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
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 buildeth_blockNumber– Get latest block numbereth_getBalance– Get account balanceeth_getTransactionCount– Get transaction count (nonce)eth_getBlockByNumber– Get block informationeth_getTransactionByHash– Get transaction detailseth_getTransactionReceipt– Get transaction receipteth_getCode– Get contract bytecodeeth_getStorageAt– Get storage value
eth_call– Execute contract calleth_estimateGas– Estimate gas for transactioneth_sendRawTransaction– Send signed transactioneth_gasPrice– Get current gas price
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 callsimulate_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, anddebug_traceCall(when the provider supports it). They never sign or send a real transaction. Real state diffs are used whendebug_traceCallis available; otherwise changes are inferred from the decoded intent.
eth_getLogs– Get event logs
list_supported_networks– List configured networks and providerslist_known_addresses– List configured wallet aliases and known token/contract addresseseth_chainId– Get chain IDnet_version– Get network versionnet_listening– Check if listeningnet_peerCount– Get peer count
web3_clientVersion– Get client versionweb3_sha3– Hash data with Keccak-256
Click the install link above or use:
cursor://anysphere.cursor-deeplink/mcp/install?name=evm-mcp&config=eyJldm0tbWNwIjp7ImNvbW1hbmQiOiJucHgiLCJhcmdzIjpbIi15IiwiQGphbWVzYW56L2V2bS1tY3AiXX19
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 startAdd 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.
| Variable | Required | Description |
|---|---|---|
INFURA_API_KEY |
One of* | Infura project API key (built-in preset) |
ALCHEMY_API_KEY |
One of* | Alchemy app API key (built-in preset) |
DEFAULT_NETWORK |
No | Default chain slug or chain ID (default: ethereum) |
DEFAULT_PROVIDER |
No | Provider slug to prefer (infura, alchemy, or custom) |
RPC_PROVIDER_ORDER |
No | Comma-separated provider fallback order (default: infura,alchemy) |
CUSTOM_PROVIDERS |
One of* | JSON array of user-defined providers |
CUSTOM_NETWORKS |
One of* | JSON array of user-defined networks |
KNOWN_ADDRESSES |
No | JSON array of known tokens/contracts (network-scoped) |
WALLET_ADDRESSES |
No | JSON array of personal wallet and contract aliases |
*At least one provider API key, custom provider, or custom network with rpcUrl is required.
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.
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
networkUrlsvalues are used directly (with{apiKey}substitution). - Relative paths (starting with
/) are appended tobaseUrl.
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.
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\"]}]"| Field | Required | Description |
|---|---|---|
name |
yes | Primary lookup key |
address |
yes | Checksummed contract address |
network |
yes | Chain slug, name, chain ID, or network alias |
type |
no | token or contract (default: contract) |
decimals |
no | Token decimals for formatted balances |
aliases |
no | Extra lookup keys |
When eth_getBalance is called with a token alias, the server uses the first configured wallet in WALLET_ADDRESSES as the token holder.
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\"}]"| Field | Required | Description |
|---|---|---|
name |
yes | Primary lookup key |
address |
yes | Wallet or contract address |
network |
no | Scope alias to one chain (default: all chains) |
aliases |
no | Extra lookup keys |
description |
no | Human-readable note |
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.
- "RPC_URL": "https://mainnet.infura.io/v3/KEY"
- "CHAIN_ID": "1"
+ "INFURA_API_KEY": "KEY"
+ "DEFAULT_NETWORK": "ethereum"
+ "DEFAULT_PROVIDER": "infura"Configuration changes require restarting the MCP server.
- Ethereum: Mainnet, Sepolia
- Polygon: Mainnet, Amoy
- Arbitrum: One, Sepolia
- Optimism: Mainnet, Sepolia
- BNB Smart Chain: Mainnet, Testnet
- Avalanche: C-Chain
- Base: Mainnet, Sepolia
- Any EVM-compatible chain via
CUSTOM_NETWORKS
Query the current block number:
{
"tool": "eth_blockNumber",
"arguments": {}
}Check an address balance using a hex address or configured alias:
{
"tool": "eth_getBalance",
"arguments": {
"address": "personal",
"blockNumber": "latest"
}
}View transaction information:
{
"tool": "eth_getTransactionByHash",
"arguments": {
"txHash": "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef"
}
}Execute a contract call:
{
"tool": "eth_call",
"arguments": {
"to": "0xA0b86a33E6441c8C06DDD46C310c0eF8D9441C8F",
"data": "0x70a08231000000000000000000000000742d35Cc6634C0532925a3b8D6Ac6e2F0C4C9B7C"
}
}Query contract events:
{
"tool": "eth_getLogs",
"arguments": {
"fromBlock": "0x1234567",
"toBlock": "latest",
"address": "0xA0b86a33E6441c8C06DDD46C310c0eF8D9441C8F",
"topics": [
"0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"
]
}
}- Blockchain Analytics – Query transaction data, balances, and contract states
- DeFi Applications – Monitor token balances, transaction receipts, and smart contract calls
- NFT Projects – Track transfers, metadata, and collection statistics
- Development Tools – Debug transactions, estimate gas, and test smart contracts
- Monitoring – Watch for specific events and transaction patterns
- Research – Analyze blockchain data across multiple EVM networks
Built with: Node.js, TypeScript, MCP SDK, Ethers.js
Dependencies: @modelcontextprotocol/sdk, ethers, zod
Platforms: macOS, Windows, Linux
Environment Variables: See Configuration above.
⭐ If this project helps you, please star it on GitHub! ⭐
Contributions welcome! Please open an issue or submit a pull request.
MIT License – see LICENSE.md for details.
If you find this project useful, consider supporting it:
⚡ Lightning Network
lnbc1pjhhsqepp5mjgwnvg0z53shm22hfe9us289lnaqkwv8rn2s0rtekg5vvj56xnqdqqcqzzsxqyz5vqsp5gu6vh9hyp94c7t3tkpqrp2r059t4vrw7ps78a4n0a2u52678c7yq9qyyssq7zcferywka50wcy75skjfrdrk930cuyx24rg55cwfuzxs49rc9c53mpz6zug5y2544pt8y9jflnq0ltlha26ed846jh0y7n4gm8jd3qqaautqa
₿ Bitcoin: bc1ptzvr93pn959xq4et6sqzpfnkk2args22ewv5u2th4ps7hshfaqrshe0xtp
Ξ Ethereum/EVM: 0x42ea529282DDE0AA87B42d9E83316eb23FE62c3f