About multi-wallet
Multi-wallet management for AI agents: generate, distribute, consolidate on EVM
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @thryx/multi-wallet-mcp-serverRPC_URLRPC endpoint URL (defaults to Base mainnet)THRYX_API_KEYSecretPremium API key for unlimited accessDEPLOYER_PRIVATE_KEYSecretPrivate key for write operations like distributing ETHWALLET_PASSWORDSecretPassword for encrypted wallet storageLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
10Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| count | number | No | Number of wallets to generate (1-100, default 5) |
| api_key | string | No | Premium API key for unlimited access. Free tier: 5/hour. |
| label_prefix | string | No | Label prefix for generated wallets (e.g. 'sniper', 'holder') |
Details
The maintainer has not added details yet. Check the README in the repository.
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.