EVM MCP Server

npx @mcpdotdirect/evm-mcp-server

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

Most chain servers pin themselves to a single network, so an agent moving between Base and Arbitrum ends up running two of them. This one keeps a single interface over 34 mainnets and 26 testnets: block and transaction lookups, native and ERC-20/721/1155 balances and transfers, contract reads and writes, event log filtering, gas estimation, and EIP-712 typed data signing for permits and Sign-In With Ethereum flows. Two design choices remove most of the guesswork: contract ABIs are pulled from block explorers on demand, so a function can be called without pasting an interface first, and every parameter that takes an address also takes an ENS name. A private key or mnemonic is only needed for the write and signing tools; read-only work needs no credentials.