MCPilot

Provides MCP servers to enable LLMs to interact with blockchains via MetaMask for secure, on‑chain actions.
  • typescript

3

GitHub Stars

typescript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "xiawpohr-mcpilot": {
      "command": "npx",
      "args": [
        "tsx",
        "/PATH/TO/YOUR_PROJECT/packages/metamask-mcp/src/index.ts"
      ],
      "env": {
        "CELOSCAN_API_KEY": "<CELOSCAN_API_KEY>"
      }
    }
  }
}

MCPilot provides a suite of MCP servers that let large language models interact with blockchains through the MetaMask wallet, keeping private keys secure while enabling AI-driven Web3 tasks. This toolkit makes it practical to onboard users to on‑chain experiences with natural language, and it supports a range of blockchain interactions through MCP-enabled services.

How to use

You can run the MCP servers locally and connect them to an MCP client to perform blockchain actions from natural language. Each server exposes a defined tool set (for example, wallet interactions, token information, and contract utilities). Start the relevant servers, then configure your MCP client to talk to them as part of your MCPlanned workflow. The set of servers here includes wallets via MetaMask, chain information, Solidity compilation, and blockchain verification helpers. When you issue requests through the MCP client, the LLM will coordinate these tools to complete tasks such as token lookups, contract verification, and token operations without exposing private keys.

How to install

Prerequisites: you need Node.js and npm installed on your machine. You will also use npx to run the MCP servers. Ensure you have a development setup where paths to your project are accessible.

  1. Create a working directory for your MCPilot project.

  2. Ensure Node.js and npm are installed. Check versions with node -v and npm -v.

  3. Install dependencies in your project if required by your setup (follow your project’s usual workflow for building or linking MCP packages).

  4. Start each MCP server using the commands shown in the configuration snippet below. You will typically run these in separate terminals or as background processes.

  5. In your MCP client (for example, Claude Desktop or another MCPlient), add the MCP server configurations so the client can communicate with each server. The configuration block below shows the required stdio server entries and how to reference the local index script for each package.

Other important notes

The following configuration snippet demonstrates how to wire up the MCP servers. Each server runs locally using Node.js tooling via npx and tsx to execute the TypeScript entry points. If you modify paths, replace /PATH/TO/YOUR_PROJECT with your actual project root.

Configuration example

{
  "mcpServers": {
    "metamask-server": {
      "command": "npx",
      "args": [
        "tsx",
        "/PATH/TO/YOUR_PROJECT/packages/metamask-mcp/src/index.ts"
      ]
    },
    "chainlist-server": {
      "command": "npx",
      "args": [
        "tsx",
        "/PATH/TO/YOUR_PROJECT/packages/chainlist-mcp/src/index.ts"
      ]
    },
    "solc-server": {
      "command": "npx",
      "args": [
        "tsx",
        "/PATH/TO/YOUR_PROJECT/packages/solc-mcp/src/index.ts"
      ]
    },
    "erc20-server": {
      "command": "npx",
      "args": [
        "tsx",
        "/PATH/TO/YOUR_PROJECT/packages/erc20-mcp/src/index.ts"
      ]
    },
    "polygon-server": {
      "command": "npx",
      "args": [
        "tsx",
        "/PATH/TO/YOUR_PROJECT/packages/polygon-mcp/src/index.ts"
      ],
      "env": {
        "POLYGONSCAN_API_KEY": ""
      }
    },
    "celo-server": {
      "command": "npx",
      "args": [
        "tsx",
        "/PATH/TO/YOUR_PROJECT/packages/celo-mcp/src/index.ts"
      ],
      "env": {
        "CELOSCAN_API_KEY": ""
      }
    },
    "zircuit-server": {
      "command": "npx",
      "args": [
        "tsx",
        "/PATH/TO/YOUR_PROJECT/packages/zircuit-mcp/src/index.ts"
      ]
    },
  }
}

Security and usage cautions

MCPilot relies on the MetaMask wallet to sign transactions so private keys never leave the wallet. Treat any tool that handles signing with care and ensure you operate within trusted environments. Use test networks and test tokens during development to avoid real asset exposure.

Available tools

metamask-mcp

Enables LLMs to interact with MetaMask for secure wallet operations without exposing private keys.

chainlist-mcp

Provides information on supported blockchain networks.

solc-mcp

Compiles Solidity smart contracts.

erc20-mcp

Manages ERC20 tokens.

celo-mcp

Verifies contracts on the Celo blockchain.

polygon-mcp

Verifies contracts on the Polygon blockchain.

zircuit-mcp

Provides token data on the Zircuit blockchain.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational