About Base Web3 Action Mcp Server
Base Web3 Action Mcp Server provides EVM tools for agents working with the Base L2 network. It reads balances and resolves Basenames, and builds unsigned transaction payloads without handling private keys.
Key features
- 01Read ETH and ERC-20 balances
- 02Resolve .base domains to addresses
- 03Build ETH and ERC-20 transfer payloads
- 04Build Uniswap V3 swap payloads
- 05Generate ERC-20 and ERC-721 deployment payloads
- 06Append ERC-8021 Builder Code suffixes
Use cases
- 01Check an address's Base balance
- 02Resolve a .base domain to an EVM address
- 03Prepare a transfer or Uniswap V3 swap
- 04Create token or NFT deployment payloads
MCP support
Exposes Base network balance, name-resolution, and transaction-building tools to MCP clients. Transactions are unsigned; the client reviews, signs, and broadcasts them.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEBase Web3 Action MCP Server 🛠️🚀
A lightweight, zero-config Model Context Protocol (MCP) server for the Base L2 Network. This server equips AI agents (such as Cursor, Windsurf, Zed, or Claude Desktop) with standard EVM tools to query balances, resolve Basenames, and build transaction payloads that automatically capture sequencer fee rewards.
Features
- Zero API Keys Required: Runs out-of-the-box using rotated public RPC endpoints with built-in failover to prevent rate-limiting (
429) errors. - On-chain Basenames Resolver: Resolves
.basedomains (e.g.,jesse.base->jesse.base.eth) directly on-chain using Base L2 contracts, bypassing slow L1 gateways. - ERC-8021 Suffix Appender: Automatically encodes and appends your Builder Code suffix to all generated transaction payloads, enabling passive sequencer reward attribution.
- Token & NFT Deployers: Scaffolds and generates deployment payloads for optimized standard ERC-20 tokens and ERC-721 NFT collections in a single click.
- Self-Custodial: Never handles, requests, or stores private keys. It only builds unsigned transaction payloads for the client to review, sign, and broadcast.
Active Tools
get_balance: Retrieve native ETH or ERC-20 token balances on Base (Mainnet or Sepolia).resolve_basename: Resolve any.basedomain to its EVM hex address.build_transfer: Build an unsigned transfer transaction payload for ETH or ERC-20.build_swap: Build Uniswap V3 swap payloads (e.g., swapping ETH to USDC) on Base.build_deploy_contract: Build contract deployment payloads for custom bytecodes.build_deploy_token: Deploy a standard ERC-20 token contract.build_deploy_nft: Deploy a standard ERC-721 NFT collection contract.
Installation & Setup
Local Client Setup (stdio)
1. Claude Desktop
Add the following to your claude_desktop_config.json (located at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"base-web3": {
"command": "node",
"args": ["/absolute/path/to/mcp-server/index.js"],
"env": {
"BASE_BUILDER_CODE": "bc_3nsmabm6"
}
}
}
}
2. Cursor Settings
- Go to Settings > Models > MCP.
- Click + Add New MCP Server.
- Configure:
- Name:
Base Web3 Action - Type:
stdio - Command:
node /absolute/path/to/mcp-server/index.js
- Name:
3. Smithery (Recommended)
Install the server directly into Claude Desktop using the Smithery CLI:
npx -y @smithery/cli@latest install base-web3-mcp --client claude
For Cursor, configure it as a standard stdio server as shown above.
Remote API Setup (Stateless HTTP)
Exposed as a stateless, authenticated endpoint for websites, bots, and Farcaster frames:
- Endpoint:
https://your-worker-subdomain.workers.dev/mcp - Headers:
Authorization: Bearer <EXECUTION_SECRET> - Request Body (JSON-RPC 2.0):
{ "method": "tools/call", "params": { "name": "get_balance", "arguments": { "address": "0x179A862703a4adfb29896552DF9e307980D19285" } } }
License
MIT - Open Source. Created for the Base builder ecosystem.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.