base-multi-wallet-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_walletA | Generate a new random wallet. Returns address (private key stored in-memory for session only). |
| import_walletA | Import an existing wallet by private key. Key is stored in-memory for session only. |
| list_walletsB | List all managed wallets with ETH balances and optional token balances. |
| fund_walletsA | Send ETH from main wallet (DEPLOYER_PRIVATE_KEY) to all managed wallets equally. |
| coordinated_buyA | Buy a token from all managed wallets simultaneously via Uniswap V2 on Base. |
| coordinated_sellA | Sell a token from all managed wallets via Uniswap V2 on Base. |
| collect_fundsA | Sweep all ETH (and optionally tokens) from managed wallets back to main wallet. |
| get_gas_estimateB | Get current Base gas price and estimate cost for N wallet operations. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no ambiguity: wallet management (create_wallet, import_wallet, list_wallets), funding operations (collect_funds, fund_wallets), coordinated trading (coordinated_buy, coordinated_sell), and gas estimation (get_gas_estimate). The descriptions make it easy to differentiate between similar-sounding tools like coordinated_buy vs coordinated_sell.
The naming follows a consistent verb_noun pattern throughout (e.g., collect_funds, create_wallet, get_gas_estimate), with all tools using snake_case. The only minor deviation is 'list_wallets' (plural) while others use singular nouns, but this doesn't break the overall consistency.
With 8 tools, this is well-scoped for a multi-wallet management server. Each tool earns its place by covering distinct aspects: wallet setup, funding, trading, and gas estimation. The count is neither too sparse nor bloated for the domain.
The toolset provides comprehensive coverage for multi-wallet operations on Base, including wallet lifecycle (create/import/list), funding flows, and coordinated trading. A minor gap is the lack of individual wallet operations (e.g., buy/sell from a single wallet), but agents can work around this using the coordinated tools or by managing wallets separately.