Base MCP Server

MCP server for AI agents to manage multiple wallets with coordinated trading and batch operations on. The base mcp server wraps that behind the Model Context Protocol, so an assistant can use it rather than through you.

What it actually does

• create_wallet — - Generate new random wallets
• import_wallet — - Import existing wallets by private key
• list_wallets — - List all managed wallets with ETH + token balances
• fund_wallets — - Distribute ETH from main wallet to all managed wallets equally
• coordinated_buy — - Buy a token from all wallets simultaneously via Uniswap V2
• coordinated_sell — - Sell a token from all wallets via Uniswap V2

Adding it to your client

base-multi-wallet-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration

You will need 2 environment variables: RPC_URL, DEPLOYER_PRIVATE_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by lordbasilaiassistant-sudo; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the base mcp server does with a few real requests.