This MCP server provides a unified interface to interact with 60+ EVM-compatible networks through 22 tooling options and AI-guided prompts. It supports reading blockchain state (balances, blocks, transactions), interacting with smart contracts with automatic ABI fetching, token transfer (native and ERC standards), token metadata queries, and comprehensive transaction signing capabilities including personal messages, EIP-712 data, and SIWE flows. All tools and prompts are designed to be ENS-friendly, resolving human-readable names like vitalik.eth to addresses automatically, and ABI fetching is automated across networks so you don’t need to pre-load ABIs.

To use the server, configure the required wallet environment (private key or mnemonic) and start the Node server as described in the installation section. Once running, you can access the MCP tools to perform contract reads/writes, token transfers, event queries, and contract verifications. Use the provided AI-guided workflows to plan transactions, analyze wallets, explore contracts, manage approvals, or diagnose errors. ENS resolution will help you work with human-readable names across the prompts and tools, streamlining complex multi-network interactions.

Prerequisites:

• Node.js 20+ or Bun (Node-based setup is assumed here)
• Optional: Etherscan API key for ABI fetching

Install steps:

1. Clone the repository: git clone https://github.com/mcpdotdirect/mcp-evm-server.git cd mcp-evm-server

2. Install dependencies:

   If using Bun (recommended in prerequisites)

   bun install

   Or with npm (alternative):

   npm install

3. Build/prepare if required (check repo for build script, otherwise run the server directly): npm run build

4. Run the MCP server (example): node dist/server.js

5. Verify the server starts and is listening on the configured port (default often 3000 or 8080 as per project).

Prerequisites note: Ensure you have either a private key or mnemonic configured via environment variables (EVM_PRIVATE_KEY or EVM_MNEMONIC) before performing write or ABI-fetching operations.

Environment variables and configuration tips:

• You must configure wallet access for write operations (transfer, write_contract, approve_token_spending, sign_message, sign_typed_data).
• If you rely on ABI fetching across networks, consider providing an Etherscan API key via environment to speed up automatic ABI resolution.
• For HD wallets, EVM_ACCOUNT_INDEX allows you to derive multiple accounts from a single mnemonic.
• Never commit your private keys or mnemonics to version control. Use secure env management.
• If you encounter network-specific issues, verify the RPC endpoints and chain IDs for the target network in the MCP server configuration.
• For debugging, enable verbose logs if supported by the server to obtain more context about errors in contract interactions or ABI fetching.