Skip to main content
Glama
Web3 Assistant MCP

Web3 Assistant MCP

by LaplaceMan

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 configuration

Quick Start

Prerequisites

  • Node.js 18+

  • pnpm

  • Configure environment variables (copy .env.example):

cp .env.example .env

Installation

pnpm install

Build

pnpm build

MCP 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 Mainnet

  • sepolia: Ethereum Sepolia

  • base: Base Mainnet

  • baseSepolia: Base Testnet

Security Guidelines

  1. Private Key Management: Configure via environment variables

  2. Transaction Verification: Confirm details for payable methods

  3. Gas Limits: Automatic safe gas calculation

Available Tools

3 tools
analyze_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

    B3.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness2/5

    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

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables 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
      -
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables 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
      -