web3-mcp-server
# Web3 MCP Server
[](https://smithery.ai/server/web3-mcp-server)
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.
## 🚀 Features
- 📊 Fetch token balances across multiple chains
- 📝 Call smart contract functions
- 💰 Native and ERC-20 token transfer
- 🔗 Support for multiple EVM-compatible chains
## 🔧 Configuration
### Claude Desktop Integration
### Installing via Smithery
To install Web3 MCP Server for Claude Desktop automatically via [Smithery](https://smithery.ai/server/web3-mcp-server):
```bash
npx -y @smithery/cli install web3-mcp-server --client claude
```
#### Using NPX
Add the following configuration to your Claude Desktop settings:
```json
{
"mcpServers": {
"web3": {
"command": "npx",
"args": ["-y", "web3-mcp-server"],
"env": {
"PRIVATE_KEY": "0xYour-wallet-private-key (optional)"
}
}
}
}
```
#### Using Docker
For Docker-based deployment, use this configuration:
```json
{
"mcpServers": {
"web3": {
"command": "docker",
"args": ["run", "-i", "--rm", "emanueljr/web3-mcp-server"],
"env": {
"PRIVATE_KEY": "0xYour-wallet-private-key (optional)"
}
}
}
}
```
## 📝 License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
## 👥 Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
TDQS
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.