Web3 Assistant MCP
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 Assistant MCP call the balanceOf method on this USDC contract: 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48"
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.
Web3 Assistant MCP
A secure blockchain smart contract interaction toolkit with multi-chain support.
Key Features
π Smart Contract ABI Analysis
π‘ Contract Method Invocation (view/nonpayable/payable)
π Local Wallet Address Management
π Multi-chain Support
Related MCP server: Blockchain Payment MCP Server
Project Structure
web3-assistant-mcp/
βββ src/
β βββ common/
β β βββ clients/ # Blockchain client implementations
β β βββ constants/ # Network configurations
β β βββ services/ # Core services (contract, wallet)
β β βββ utils/ # Helper functions
β βββ tools/ # MCP tool implementations
β βββ types/ # TypeScript type definitions
βββ test/ # Test suites
βββ .env.example # Environment template
βββ smithery.yaml # MCP server configurationQuick Start
Prerequisites
Node.js 18+
pnpm
Configure environment variables (copy .env.example):
cp .env.example .envInstallation
pnpm installBuild
pnpm buildMCP Configuration Example
{
"mcpServers": {
"web3-assistant": {
"command": "node",
"args": [
"***/dist/index.js"
],
"env": {
"ALCHEMY_KEY": "your_alchemy_key",
"INFURA_KEY": "your_infura_key",
"ANKR_KEY": "your_ankr_key",
"PRIVATE_KEY": "your_wallet_private_key"
}
}
}
}Path Note: When using MCP locally, replace *** with the absolute path to your MCP server directory.
MCP Tools Documentation
π analyze_contract_abi - ABI Analysis
{
"abi": "[Contract ABI JSON string]"
}Features:
Parse contract ABI and list callable methods
Auto-detect method types (view/pure/payable)
Input/output parameter types
State mutability
π call_contract - Contract Interaction
{
"abi": "[Method ABI]",
"networkName": "base|baseSepolia",
"contractAddress": "0x...",
"functionName": "methodName",
"args": ["param1", param2],
"value": 0.001 // ETH amount for payable methods (in ETH)
}Supported Operations:
Read contract state (view/pure)
Send transactions (nonpayable)
Token transfers (payable)
π local_wallet_address - Wallet Address
No parameters required:
{
"address": "0x..."
}Network Configuration
Pre-configured networks in src/common/constants/networks:
mainnet: Ethereum Mainnetsepolia: Ethereum Sepoliabase: Base MainnetbaseSepolia: Base Testnet
Security Guidelines
Private Key Management: Configure via environment variables
Transaction Verification: Confirm details for payable methods
Gas Limits: Automatic safe gas calculation
Available Tools
3 toolsanalyze_contract_abiC
Analyze the functions provided in the solidity contract.
Inputs: abi (required).
call_contractC
Call a function in the solidity contract.
Inputs: abi (required), networkName (required), contractAddress (required), functionName (required), +2 more.
local_wallet_addressB
Get the local wallet evm address.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: analyze_contract_abi is for inspecting contract functions, call_contract is for executing functions, and local_wallet_address is for retrieving wallet information. There is no overlap or ambiguity between these tools.
The tools follow a consistent snake_case naming convention, but the naming pattern is not perfectly uniform: analyze_contract_abi and call_contract use verb_noun format, while local_wallet_address is a noun phrase. This minor deviation keeps it mostly consistent.
With only 3 tools, the set feels thin for a 'Web3 Assistant' domain, which typically involves more operations like deploying contracts, checking balances, or interacting with blockchains. While the tools cover some basics, the count is borderline for the apparent scope.
There are significant gaps in the tool surface for Web3/blockchain interactions. Missing are essential operations such as deploying contracts, reading blockchain data (e.g., balances, transactions), or sending transactions. This incompleteness will likely cause agent failures in common workflows.
Related MCP Connectors
Read-only on-chain intelligence for AI agents on Base: balances, tokens, gas, tx status.
Read-only on-chain intelligence for AI agents on Base: balances, tokens, gas, tx status.
Resolve any EVM contract ABI (even unverified, via decompilation), read, simulate, prepare txs.
EVM wallet reads, simulation, and transaction execution under user-defined authorization policies.
Related MCP Servers
- AlicenseBqualityDmaintenanceProvides Claude with access to Ethereum and EVM-compatible blockchain operations, enabling wallet management, transaction handling, contract interactions, and blockchain queries through natural language.35236 npm10MIT
- AlicenseNot gradedqualityDmaintenanceEnables blockchain payment operations across multiple networks including Base, Ethereum, BSC, Polygon, and Avalanche. Supports balance queries, token transfers, transaction tracking, wallet management, and gas fee estimation with built-in security limits.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI applications to interact with the Base blockchain network, allowing wallet management, smart contract deployment, token transfers, NFT operations, DeFi interactions with Morpho vaults, and onramping funds via Coinbase.26 npm-
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI applications to interact with the Base blockchain network and Coinbase API, supporting wallet operations, smart contract deployment, token transfers, NFT management, DeFi lending through Morpho vaults, and onramp functionality.26 npm-