MCP EVM Signer logo

MCP EVM Signer

by zhangzhongnan928

The MCP EVM Signer is a Model Context Protocol (MCP) server designed to manage Ethereum private keys and deploy smart contracts using Infura. It enables Claude for Desktop and other MCP clients to interact with EVM-compatible blockchains.

View on GitHub

Last updated: N/A

What is MCP EVM Signer?

The MCP EVM Signer is a server that allows Claude for Desktop and other MCP clients to interact with EVM-compatible blockchains. It securely manages Ethereum private keys locally and connects to Infura for blockchain interactions.

How to use MCP EVM Signer?

To use the MCP EVM Signer, you need to clone the repository, install dependencies, build the project, configure environment variables (including your Infura API key), and then add the server to your Claude for Desktop configuration. Detailed instructions are provided in the README.

Key features of MCP EVM Signer

  • Securely store and manage Ethereum private keys locally

  • Connect to Infura for blockchain interactions

  • Deploy smart contracts from compiled ABIs and bytecode

  • Sign and send transactions

  • View account balances and transaction history

  • Query blockchain data and interact with deployed contracts

Use cases of MCP EVM Signer

  • Deploying smart contracts using Claude

  • Checking Ethereum wallet balances

  • Sending ETH transactions

  • Interacting with deployed smart contracts

  • Automating blockchain interactions through Claude

  • Creating and managing Ethereum wallets

FAQ from MCP EVM Signer

Where are private keys stored?

Private keys are stored locally on your machine in the keys/ directory (gitignored).

Are the private keys encrypted?

Yes, keys can be encrypted with a password, which you configure in the .env file.

What networks are supported?

The server can be configured to use various Ethereum networks via the DEFAULT_NETWORK environment variable, such as Sepolia or Goerli.

How do I deploy a smart contract?

You can use the deploy-contract tool with Claude, providing the ABI and bytecode of your smart contract. See the ERC-20 token example for a complete walkthrough.

What security measures are in place?

Private keys are stored locally and can be encrypted. The server only exposes functionality through the MCP protocol. Always review transactions before approving them.