Wallet MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BSC_RPC_URL | No | BSC RPC endpoint | https://bsc-dataseed.binance.org/ |
| SOLANA_RPC_URL | No | Solana RPC endpoint | https://api.mainnet-beta.solana.com |
| AMBIENT_RPC_URL | No | Ambient RPC endpoint | https://rpc.ambient.xyz |
| ARBITRUM_RPC_URL | No | Arbitrum One RPC endpoint | https://arb1.arbitrum.io/rpc |
| WALLET_KEYSTORE_PATH | No | Keystore file location | ~/.config/wallet-mcp-server/keystore.json |
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 |
|---|---|
| wallet_generateB | Generate a new keypair, encrypt it with the provided password, and store it in the keystore. |
| wallet_importB | Import an existing private key, encrypt it, and store it in the keystore. |
| wallet_exportB | Export a stored private key (requires password to decrypt). |
| wallet_get_public_keyB | Get the public key / address of a stored wallet. |
| wallet_sign_messageC | Sign an arbitrary message with a stored wallet. |
| wallet_sign_transactionA | Sign a transaction with a stored wallet (does not broadcast). For EVM, provide standard tx fields; for SVM, provide a base64-serialized transaction. |
| wallet_send_transactionA | Sign and broadcast a transaction. Fills in missing gas/nonce params from the RPC provider. |
| wallet_listA | List all stored wallets (addresses and metadata only, no private keys). |
| wallet_deleteA | Delete a stored wallet (requires password to confirm ownership). |
| wallet_get_balanceB | Query the native token balance of a stored wallet. Native token: AMB on Ambient (wAMB when held in a market), SOL on Solana, BNB on BSC, ETH on Arbitrum. |
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 10 tools
Most tools target distinct actions, but wallet_sign_transaction and wallet_send_transaction both involve signing and could be momentarily confused; descriptions clarify that one broadcasts and the other does not. Remaining tools (list, delete, generate, import, export, get_balance, get_public_key, sign_message) are clearly distinct.
All tools use the wallet_ prefix with consistent snake_case verb_noun or verb naming (wallet_sign_message, wallet_get_balance, wallet_generate, etc.). The pattern is predictable and readable throughout.
10 tools is well-scoped for a wallet server, covering key management, signing, broadcasting, and balance queries without redundancy. Each tool earns its place.
Core wallet lifecycle is covered: create (generate/import), read (list/get_public_key/get_balance), delete, and signing/broadcast operations. Minor gaps include no wallet metadata update/rename and no transaction status/receipt lookup, but these are not central to the stated purpose.