Supports containerized deployment for seamless blockchain interactions, allowing access to token balances and smart contract functions across multiple EVM chains.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@web3-mcp-server check my ETH balance on Ethereum mainnet"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol (MCP) server implementation for Web3 interactions on EVM chains. This server enables seamless interaction with blockchain networks through the Model Context Protocol.
📊 Fetch token balances across multiple chains
📝 Call smart contract functions
💰 Native and ERC-20 token transfer
🔗 Support for multiple EVM-compatible chains
Related MCP server: mcp-chainlist
To install Web3 MCP Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install web3-mcp-server --client claudeAdd the following configuration to your Claude Desktop settings:
{
"mcpServers": {
"web3": {
"command": "npx",
"args": ["-y", "web3-mcp-server"],
"env": {
"PRIVATE_KEY": "0xYour-wallet-private-key (optional)"
}
}
}
}For Docker-based deployment, use this configuration:
{
"mcpServers": {
"web3": {
"command": "docker",
"args": ["run", "-i", "--rm", "emanueljr/web3-mcp-server"],
"env": {
"PRIVATE_KEY": "0xYour-wallet-private-key (optional)"
}
}
}
}This project is licensed under the MIT License - see the LICENSE file for details.
Contributions are welcome! Please feel free to submit a Pull Request.
Get the balance of a wallet
Inputs: walletAddress (required), chainId (required).
Get the price of a token
Inputs: slug (required).
Get the balance of a token
Inputs: tokenAddress (required), chainId (required), walletAddress (required).
Read a value from a contract
Inputs: contractAddress (required), chainId (required), abi (required), functionName (required), +1 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 4 tools
The tools have some overlap that could cause confusion, particularly between fetch_balance and fetch_token_balance, as both involve retrieving balances but target different resources (wallet vs. token). However, the descriptions clarify the distinctions, and the other tools (fetch_quote, read_contract) are clearly distinct in purpose.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., fetch_balance, fetch_quote, fetch_token_balance, read_contract). This uniformity makes the set predictable and easy to understand, with no deviations in naming conventions.
With only 4 tools, the server feels slightly thin for a web3 domain, which typically involves more operations like transactions, token transfers, or contract interactions. While the tools cover basic read-only functions, the count is borderline for comprehensive coverage in this scope.
The tool set is significantly incomplete for a web3 server, as it lacks essential operations such as sending transactions, interacting with smart contracts beyond reading, or managing tokens. This creates gaps that will likely cause agent failures when trying to perform common blockchain tasks.
Read EVM and Solana chains for balances, tokens, eth_call, logs, receipts, gas, blocks and ENS.
Wallet balances, ERC-20, blocks, transactions, receipts, ENS and payment checks, pay per call
Read-only BlockReq docs, EVM JSON-RPC, and on-chain DEX and wallet data
Provide AI agents and automation tools with contextual access to blockchain data including balance…