
zhangzhongnan928/mcp-blockchain-server
Developer toolsこのページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る
MCP Server for blockchain interactions with Web DApp for secure transaction signing
概要
An MCP server that lets AI assistants and — while the user keeps full custody of their keys and signs every transaction in their own wallet. It runs as a . No database, no Redis, no API keys, no separate frontend to build. Point your MCP client at it and go. The hard problem in AI + blockchain is letting an assistant act without ever touching private keys. This server solves it by splitting the work: - (balances, contract state) happen server-side and return directly to the assistant. - are only ever prepared server-side. The server hands back a URL; the user opens it, reviews the details, and . The wallet broadcasts the transaction. The server only ever learns the resulting transaction hash. Requirements: . No clone, no build, no API keys. Add the server to any MCP client that launches stdio servers. For , open Settings → Developer → Edit Config and add: Restart the client. You can now ask things like "What's the ETH balance of vitalik.eth?" or "Send 0.01 test ETH to 0x…
README
以下は原文 README の抜粋です。原文を見る。
MCP Blockchain Server
An MCP server that lets AI assistants read blockchain data and prepare transactions — while the user keeps full custody of their keys and signs every transaction in their own wallet.
It runs as a single, self-contained process. No database, no Redis, no API keys, no separate frontend to build. Point your MCP client at it and go.
┌──────────────┐ MCP (stdio) ┌─────────────────────┐ RPC ┌────────────┐
│ AI assistant │ ──────────────► │ mcp-blockchain │ ───────► │ Blockchain │
│ (Claude …) │ ◄────────────── │ server │ ◄─────── │ (EVM) │
└──────────────┘ │ + signing web page │ └────────────┘
└─────────┬───────────┘
│ opens link, signs in wallet
▼
┌───────────┐
│ User │ (MetaMask / Rabby / …)
└───────────┘
Why this design
The hard problem in AI + blockchain is letting an assistant act without ever touching private keys. This server solves it by splitting the work:
- Reads (balances, contract state) happen server-side and return directly to the assistant.
- Writes are only ever prepared server-side. The server hands back a URL; the user opens it, reviews the details, and signs in their own wallet. The wallet broadcasts the transaction. The server only ever learns the resulting transaction hash. Private keys never reach the server.
Quick start
Requirements: Node.js 18+. No clone, no build, no API keys.
Add the server to any MCP client that launches stdio servers. For Claude Desktop, open Settings → Developer → Edit Config and add:
{
"mcpServers": {
"blockchain": {
"command": "npx",
"args": ["-y", "mcp-blockchain-server"]
}
}
}
Restart the client. You can now ask things like “What’s the ETH balance of vitalik.eth?” or “Send 0.01 test ETH to 0x… on Sepolia.” For a send, the assistant returns a link — open it, review, and sign in your wallet.
No configuration is required: the server ships with free public RPC endpoints and defaults to the Sepolia testnet.
Use it in other clients
The same npx command works anywhere that runs an MCP stdio server — the config
shape is identical across clients:
{ "command": "npx", "args": ["-y", "mcp-blockchain-server"] }
This is the block to drop into Cursor (.cursor/mcp.json), Cline,
Windsurf, VS Code (.vscode/mcp.json), and others. To pass options, add
an "env" block (see Configuration).
Run from source (development)
git clone https://github.com/zhangzhongnan928/mcp-blockchain-server.git
cd mcp-blockchain-server
npm install # installs and builds (via the prepare script)
インストール
npx -y mcp-blockchain-server設定
{
"mcpServers": {
"blockchain": {
"command": "npx",
"args": ["-y", "mcp-blockchain-server"]
}
}
}