MCP Wallet Signer

Routes blockchain transactions to browser wallets for signing and returns results to MCP clients.

typescript

0

GitHub Stars

typescript

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "nikicat-mcp-wallet-signer": {
      "command": "npx",
      "args": [
        "mcp-wallet-signer"
      ],
      "env": {
        "EVM_MCP_PORT": "3847",
        "EVM_MCP_DEFAULT_CHAIN": "1"
      }
    }
  }
}

You have an MCP Wallet Signer that routes blockchain signing requests to your browser wallet, enabling signing of transactions and messages directly from your browser. This makes it easy to approve actions securely without running separate wallet software.

How to use

You interact with the MCP Wallet Signer from your MCP client. When you request actions like connecting a wallet, sending a transaction, or signing a message, the server opens a local signing page in your browser. You approve the action in your wallet, and the server returns the result to your client, such as the address, transaction hash, or signature.

How to install

Prerequisites: you need a computer with Node.js and npm or compatible runtime available. You will run commands that use npx to execute the MCP Wallet Signer.

claude mcp add evm-wallet -- npx mcp-wallet-signer

Configuration and runtime setup

If you are using Claude Desktop, add a new MCP server entry to your claude_desktop_config.json like this:

{
  "mcpServers": {
    "evm-wallet": {
      "command": "npx",
      "args": ["mcp-wallet-signer"]
    }
  }
}

Run directly

You can run the signer directly from the command line using one of these commands:

npx mcp-wallet-signer
pnpx mcp-wallet-signer
bunx mcp-wallet-signer

Configuration options

Optional environment variables configure how the server operates. They control the listen port and the default network chain you target.

Environment variables

EVM_MCP_PORT: HTTP server port. Default is 3847.
EVM_MCP_DEFAULT_CHAIN: Default chain ID. Default is 1.

Tools and capabilities

The MCP Wallet Signer provides a set of tools to interact with wallets and sign data from your browser.

Supported chains

Built-in RPC URLs include Ethereum, Sepolia, Polygon, Arbitrum One, Optimism, Base, Avalanche, and BNB Smart Chain.

Development notes

Development uses Deno v2.0+ for local development tasks, with commands to install dependencies, run the dev server, run tests, and build artifacts.

Project structure

A typical project layout includes a source directory with the MCP server logic, a web UI built with Svelte for the signing pages, and tests for the request/promise tracking and end-to-end flows.

License

MIT licensed.

Available tools

connect_wallet

Connect wallet, return address

send_transaction

Send ETH/tokens, call contracts

sign_message

Sign arbitrary message (personal_sign)

sign_typed_data

Sign EIP-712 typed data

get_balance

Read ETH balance (via RPC)