EVM MCP Server

@chulanpro5

About EVM MCP Server

No overview available yet

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "evm-mcp-server-chulanpro5": {
      "command": "npx",
      "args": [
        "@mcpdotdirect/evm-mcp-server"
      ]
    }
  }
}

Tools

Get the address of the configured wallet. Use this to verify which wallet is active.

Get information about an EVM network: chain ID, current block number, and RPC endpoint

Get a list of all supported EVM networks

Get current gas prices (base fee, standard, and fast) for a network

Resolve an ENS name to an Ethereum address

Lookup the ENS name for an Ethereum address (reverse resolution)

Get block details by block number or hash

Get the latest block from the network

Get the native token balance (ETH, MATIC, etc.) for an address

Get the ERC20 token balance for an address

Check the allowance granted to a spender for a token. This tells you how much of a token an address can spend on your behalf.

Get transaction details by transaction hash

Get transaction receipt (confirmation status, gas used, logs). Use this to check if a transaction has been confirmed.

Wait for a transaction to be confirmed (mined). Polls the network until confirmation.

Fetch a contract's full ABI from Etherscan/block explorers. Use this to understand verified contracts before interacting. Requires ETHERSCAN_API_KEY. Supports 30+ EVM networks. Works best with verified contracts on block explorers.

Call read-only functions on a smart contract. Automatically fetches ABI from block explorer if not provided (requires ETHERSCAN_API_KEY). Falls back to common functions if contract is not verified. Use this to query contract state and data.

Execute state-changing functions on a smart contract. Automatically fetches ABI from block explorer if not provided (requires ETHERSCAN_API_KEY). Use this to call any write function on verified contracts. Requires wallet to be configured (via private key or mnemonic).

Batch multiple contract read calls into a single RPC request. Significantly reduces latency and RPC usage when querying multiple functions. Uses the Multicall3 contract deployed on all major networks. Perfect for portfolio analysis, price aggregation, and querying multiple contract states efficiently.

Transfer native tokens (ETH, MATIC, etc.) to an address. Uses the configured wallet.

Transfer ERC20 tokens to an address. Uses the configured wallet.

Approve a spender (contract) to spend tokens on your behalf. Required before interacting with DEXes, lending protocols, etc.

Get information about an ERC721 NFT including metadata URI

Get ERC1155 token balance for an address

Sign an arbitrary message using the configured wallet. Useful for authentication (SIWE), meta-transactions, and off-chain signatures. The signature can be verified on-chain or off-chain.

Sign structured data (EIP-712) using the configured wallet. Used for gasless transactions, meta-transactions, permit signatures, and protocol-specific signatures. The signature follows the EIP-712 standard.

Overview

What is EVM MCP Server?

A comprehensive Model Context Protocol (MCP) server that provides blockchain services across 30+ EVM-compatible networks. It enables AI agents to interact with Ethereum, Optimism, Arbitrum, Base, Polygon, and other EVM chains through a unified interface.

How to use EVM MCP Server?

Install via git clone and bun install (or npm install), or run directly with npx @mcpdotdirect/evm-mcp-server. Start in stdio mode for CLI tools or HTTP mode for web applications. Connect any MCP-compatible client, such as Cursor, Claude CLI, or the MCP Inspector.

Key features of EVM MCP Server

Multi-chain support for 30+ EVM networks including mainnets and testnets.
Read blockchain state: balances, transactions, blocks, chain info.
Interact with smart contracts via read/write functions.
Transfer native tokens, ERC20, ERC721, and ERC1155 tokens.
ENS name resolution for all address parameters.
Gas estimation, transaction status, and event log retrieval.

Use cases of EVM MCP Server

AI agents querying live blockchain data across multiple chains.
Automating token transfers and approvals from natural language.
Checking NFT ownership and metadata for collections.
Researching smart contract interactions and event logs.
Building blockchain-aware web applications with SSE support.

FAQ from EVM MCP Server

What EVM networks are supported?

Over 30 mainnets (Ethereum, Optimism, Arbitrum, Base, Polygon, etc.) and 20+ testnets (Sepolia, Goerli, Holesky, etc.). The full list is in the Supported Networks section.

Does EVM MCP Server require a private key for all operations?

No. Read-only tools (e.g., get-token-balance, get-nft-info) do not require a private key. Write tools (e.g., transfer-token, approve-token-spending) require a private key for signing.

Can I use ENS names instead of addresses?

Yes. Every tool that accepts an Ethereum address also supports ENS names (e.g., vitalik.eth). They are automatically resolved to addresses.

How do I run EVM MCP Server without installation?

Use npx @mcpdotdirect/evm-mcp-server for stdio mode, or add --http for HTTP mode. No cloning or local build required.

What transport modes are available?

The server supports stdio (for CLI/embedding) and HTTP with Server-Sent Events (SSE) for web applications.

Frequently asked questions

What EVM networks are supported?

Over 30 mainnets (Ethereum, Optimism, Arbitrum, Base, Polygon, etc.) and 20+ testnets (Sepolia, Goerli, Holesky, etc.). The full list is in the Supported Networks section.

Does EVM MCP Server require a private key for all operations?

No. Read-only tools (e.g., `get-token-balance`, `get-nft-info`) do not require a private key. Write tools (e.g., `transfer-token`, `approve-token-spending`) require a private key for signing.