MCP Ethers Wallet

What is MCP Ethers Wallet?

MCP Ethers Wallet is a complete ethers.js v6 wrapper for Claude, providing 40+ tools for Ethereum blockchain interactions. It works with 20+ EVM networks including Ethereum, Polygon, Arbitrum, Base, and more, and is intended for developers integrating Ethereum operations into Claude workflows.

How to use MCP Ethers Wallet?

Install the server by cloning the repository, running npm install and npm run build. Add it to Claude using claude mcp add ethers-wallet -- node /path/to/ethers-server/build/src/index.js. Optionally configure environment variables such as ALCHEMY_API_KEY, INFURA_API_KEY, and DEFAULT_NETWORK in a .env file. Invoke specific Ethereum operations (e.g., getting a wallet balance) via JSON‑formatted tool calls as shown in the README.

Key features of MCP Ethers Wallet

• 40+ tools for Ethereum blockchain interactions
• Wraps ethers.js v6 for maximum compatibility
• Supports 20+ EVM networks (Ethereum, Polygon, Arbitrum, Base, etc.)
• Secure prepare‑sign‑broadcast workflow; private keys never stored
• Token support for ERC20, ERC721, and ERC1155
• Smart contract calls with custom ABI support

Use cases of MCP Ethers Wallet

• Get wallet balances and token info across multiple EVM networks
• Prepare and broadcast Ethereum transactions with gas optimization
• Interact with smart contracts, including custom ABI calls
• Resolve ENS names and perform unit conversions
• Manage ERC20/721/1155 token transfers and approvals

FAQ from MCP Ethers Wallet

What does the server do that ethers.js alone cannot?

It wraps ethers.js v6 into a set of 40+ MCP tools, allowing Claude to directly perform Ethereum operations (e.g., balance checks, transaction broadcasting) without manual scripting.

What dependencies or runtime are required?

Node.js and npm are required. The server is built with TypeScript and ethers.js v6. Testing requires a Hardhat local node.

Where do API keys and private keys live?

API keys for Alchemy or Infura are stored in a .env file on the user’s machine. Private keys are never stored on the server; external signing (hardware wallets, offline signing) is supported.

What transport or authentication does it use?

It communicates via the Model Context Protocol (MCP) with Claude. Authentication relies on the user’s API keys (Alchemy/Infura) in the environment.

Are there known limitations?

The README does not list specific limitations. It notes that private keys are never stored on the server, implying that signing must be handled externally.