EVM Wallet Signer MCP Server

Route EVM transactions to browser wallets (MetaMask, etc.) for signing via EIP-6963

Local serverstdio

What is the EVM Wallet Signer MCP Server?

EVM Wallet Signer is an MCP integration. Route EVM transactions to browser wallets (MetaMask, etc.) for signing via EIP-6963.

Packages and local setup

The published npm package is mcp-wallet-signer, version 0.1.3. Its declared MCP transport is stdio.

The package declares EVM_MCP_PORT: HTTP server port for the browser approval UI (default: 3847); EVM_MCP_DEFAULT_CHAIN: Default EVM chain ID (default: 1 for Ethereum mainnet).

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.1.3 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related browser automation MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
EVM_MCP_PORTHTTP server port for the browser approval UI (default: 3847)Optional
EVM_MCP_DEFAULT_CHAINDefault EVM chain ID (default: 1 for Ethereum mainnet)Optional