Evm MCP Server

What mcpdotdirect/evm-mcp-server MCP server does

The mcpdotdirect/evm-mcp-server MCP server exposes blockchain operations through the Model Context Protocol for Ethereum-compatible networks. The repository lists support for more than 60 networks, including Ethereum, Optimism, Arbitrum, Base, Polygon, Avalanche, BNB Smart Chain, zkSync Era, Linea, Celo, and corresponding testnets.

Read operations cover network metadata, current and historical blocks, gas prices, native balances, ERC20 balances and allowances, NFT information, ERC1155 balances, transactions, and receipts. ENS names can be supplied where addresses are accepted, allowing agents to resolve names such as vitalik.eth during requests.

Contract tools support ABI retrieval, read-only calls, state-changing calls, and batched reads through Multicall3. The server also provides native-token and ERC20 transfers, token approvals, arbitrary message signatures, and EIP-712 typed-data signatures.

How it works

The server communicates with EVM networks through configured chain and RPC settings. get_supported_networks lists available networks, while get_chain_info reports a network's chain ID, latest block number, and RPC endpoint. Block and transaction tools can retrieve data by block number, block hash, or transaction hash; wait_for_transaction polls until a transaction is mined.

For verified contracts, the mcpdotdirect/evm-mcp-server MCP server can obtain an ABI from block explorers through the Etherscan v2 API. read_contract can use a supplied ABI or fetch one automatically when configured. Unverified contracts may still support common-function fallbacks, but the material specifically identifies verified contracts as the best fit for automatic ABI-based interaction.

Setup and configuration

The project requires Bun 1.0 or newer, or Node.js 20 or newer when Bun is not used. The documented installation process is to clone the repository, enter its directory, and install dependencies with bun install or npm install.

No wallet is needed for read-only blockchain queries. Write operations and signing use either EVM_PRIVATE_KEY or EVM_MNEMONIC. Mnemonic wallets can use EVM_ACCOUNT_INDEX to select an account derived through the stated BIP-44 path; the default index is 0.

Set ETHERSCAN_API_KEY to enable automatic ABI retrieval for get_contract_abi and ABI-dependent contract reads, as well as the ABI analysis prompt. The documented defaults are Ethereum mainnet as chain ID 1, port 3001, and host 0.0.0.0.

Tools and capabilities

Available capabilities include:

• Inspecting supported networks, chain details, gas prices, blocks, balances, transactions, and receipts.
• Resolving ENS names and performing reverse address lookup.
• Reading and writing smart contracts, fetching ABIs, and batching read calls.
• Sending native tokens and ERC20 tokens, checking allowances, and approving spenders.
• Reading NFT and ERC1155 information.
• Signing personal messages and EIP-712 structured data.
• Using prompts for transaction preparation, wallet analysis, contract exploration, approval review, and error diagnosis.

The mcpdotdirect/evm-mcp-server MCP server uses the configured wallet for actions that spend funds or produce signatures. Private keys and mnemonic phrases should be kept out of source control and stored securely.

Limitations and notes

Automatic ABI discovery depends on block-explorer verification and ETHERSCAN_API_KEY; without it, callers may need to provide ABI data or use supported common functions. Wallet credentials are required for transfers, approvals, contract writes, and signing, so these operations should be limited to accounts intended for agent control. Server host, port, and chain configuration are documented as hardcoded values that require source changes to modify.