MCP Ethers Wallet
by crazyrabbitLTC
The MCP Ethers Wallet is a Model Context Protocol (MCP) server that provides Ethereum wallet functionality using ethers.js v6. It exposes Ethereum functionality to LLM applications through the Model Context Protocol.
Last updated: N/A
What is MCP Ethers Wallet?
The MCP Ethers Wallet is an MCP server providing Ethereum wallet functionalities, enabling LLM applications to interact with the Ethereum blockchain. It supports network management, wallet operations, transaction handling, contract interactions, ENS resolution, and unit conversions.
How to use MCP Ethers Wallet?
To use the server, clone the repository, install dependencies, build the code, and configure environment variables for API keys. Start the server using Node.js or Bun. Configure an MCP client like Claude Desktop to connect to the server using the provided command and arguments.
Key features of MCP Ethers Wallet
Network information and management
Wallet creation and management
Transaction creation and sending
Contract interaction (ERC20, ERC721, ERC1155)
ENS resolution
Unit conversion
Gas estimation
Transaction history
Use cases of MCP Ethers Wallet
Integrating Ethereum wallet functionality into LLM applications
Automating Ethereum transactions through AI agents
Interacting with smart contracts using natural language commands
Building AI-powered decentralized applications
FAQ from MCP Ethers Wallet
What is MCP?
What is MCP?
MCP stands for Model Context Protocol, a standard for communication between LLMs and external tools.
What networks are supported?
What networks are supported?
The server supports multiple Ethereum and EVM-compatible networks, including Ethereum, Polygon, Arbitrum, Optimism, Avalanche, Base, and more. See the src/config/networkList.ts file for the full list.
How do I configure API keys?
How do I configure API keys?
Create a .env file in the root directory and set the ALCHEMY_API_KEY and INFURA_API_KEY environment variables.
How do I use a custom RPC URL?
How do I use a custom RPC URL?
You can specify a custom RPC URL in the provider parameter, e.g., "provider": "https://my-custom-rpc.example.com".
What security considerations should I be aware of?
What security considerations should I be aware of?
Be cautious with private keys, protect your API keys, and use signMessage instead of ethSign where possible.