Para Wallet MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PARA_API_KEY | Yes | Your Para API key, which can be obtained at developer.getpara.com |
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 | Create an MPC wallet via Para. The wallet is created asynchronously — status starts as "creating" and transitions to "ready" once key generation completes. Use wait_for_wallet_ready to poll until ready. |
| get_walletB | Get wallet details by ID, including status, address, and public key. |
| sign_rawA | Sign arbitrary data with a wallet via MPC. The data must be a 0x-prefixed hex string. The wallet must be in "ready" status. Returns the signature. |
| list_walletsA | Batch-fetch multiple wallets by their IDs. Para has no native list endpoint, so this fetches each wallet individually via Promise.allSettled. Maximum 10 IDs per call. |
| wait_for_wallet_readyA | Poll a wallet until its status becomes "ready" (MPC key generation complete). Polls every 2 seconds up to a configurable max wait time (default 30s). |
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 5 tools
Each tool has a clearly distinct purpose with no overlap: create_wallet for creation, get_wallet for single retrieval, list_wallets for batch retrieval, sign_raw for signing, and wait_for_wallet_ready for polling. The descriptions explicitly differentiate their functions, eliminating any ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case: create_wallet, get_wallet, list_wallets, sign_raw, and wait_for_wallet_ready. This uniformity makes the set predictable and easy to understand at a glance.
With 5 tools, this server is well-scoped for wallet management and signing operations. Each tool serves a clear, essential function without redundancy, fitting the typical range of 3-15 tools for a focused domain like MPC wallets.
The tool set covers core MPC wallet workflows: creation, retrieval (single and batch), signing, and status polling. A minor gap is the lack of update or delete operations for wallets, which might be intentional given the domain but could limit agent flexibility in some scenarios.