MCP Wallet Signer

[!WARNING] Superseded by browser-web3-signer — the same browser-wallet signing flow, reimplemented in Rust with a CLI plus Rust/TypeScript/Go libraries. mcp-wallet-signer still works, but new development happens there.

Your private keys never leave your browser. Every transaction requires explicit user approval in your wallet.

Most blockchain MCPs require you to paste a private key into a config file — giving the AI agent full, unsupervised access to your funds. MCP Wallet Signer takes a different approach: it routes every transaction to your actual browser wallet — EVM wallets (MetaMask, Rabby, …) via EIP-6963, and TRON via TronLink — so you review and approve each action just like any other dapp interaction. No keys in config files, no risk of silent transactions.

Compatible With

Works with any MCP-compatible client via stdio transport.

Installation

Claude Code CLI

claude mcp add wallet-signer -- npx -y mcp-wallet-signer

(The name wallet-signer is just the MCP server identifier — pick anything you like. Legacy evm-wallet still works for users who installed before TRON support landed.)

Claude Desktop

Add to your claude_desktop_config.json:

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

Run directly

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

MCP Tools

EVM (MetaMask / Rabby / any EIP-6963 wallet)

TRON (TronLink)

... View full README on GitHub