LabscoMCP early access ↗
EmanuelJrMCP SERVER

Web3 MCP Server

Read balances and call contracts on EVM chains — and send tokens if you hand it a key.

by EmanuelJr ↗Wallets, Signing & Transaction ExecutionCommunity

LABSCO SUMMARY

The key is what turns a reader into a spender.

Balances and contract calls need no credentials at all, so the read-only setup is the one to start from. PRIVATE_KEY is marked optional for a reason: supplying it gives whatever is driving the server the ability to transfer tokens. If you do supply one, make it a wallet whose entire balance you would accept losing to a bad prompt.

What it is

A Web3 server for EVM-compatible chains. It reads token balances, calls smart-contract functions, and — when a private key is configured — transfers native tokens and ERC-20s.

What you get

  • Token balances fetched across multiple chains
  • Smart-contract function calls
  • Native and ERC-20 token transfers
  • Support for multiple EVM-compatible chains from the same server

Requirements

The npm package web3-mcp-server, version 0.2.0, run as npx -y web3-mcp-server. PRIVATE_KEY is optional — leave it unset and the server reads; set it and it can move funds. A Docker image exists too, but its documented configuration does not pass PRIVATE_KEY into the container, so run that way it only reads.

Setup effort

Add the configuration to your client