Para Wallet MCP Server
Enables creation and management of Multi-Party Computation (MPC) wallets on the Solana blockchain, including capabilities to sign raw hex data and check wallet status.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Para Wallet MCP Server Create a new EVM wallet for user@example.com and give me the address"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Para Wallet MCP Server
An MCP (Model Context Protocol) server that wraps Para's REST API, giving AI agents wallet creation and signing capabilities via MPC (Multi-Party Computation).
Tools
Tool | Purpose |
| Create an MPC wallet (EVM, Solana, Cosmos) |
| Get wallet status and address |
| Sign 0x-hex data via MPC |
| Batch-fetch multiple wallets by ID |
| Poll until wallet is ready after creation |
Related MCP server: AgentWallet MCP Server
Setup
Get a Para API key at developer.getpara.com
Allowlist your server IP in the Para dashboard
Clone and install:
git clone https://github.com/adeets-22/para-wallet-mcp.git
cd para-wallet-mcp
npm install
npm run buildCopy
.env.exampleto.envand add your API key:
cp .env.example .envMCP Client Configuration
Add to your MCP client config (e.g. Claude Desktop claude_desktop_config.json):
{
"mcpServers": {
"para-wallet": {
"command": "node",
"args": ["/path/to/para-wallet-mcp/dist/index.js"],
"env": {
"PARA_API_KEY": "your_api_key_here"
}
}
}
}Or for development with tsx:
{
"mcpServers": {
"para-wallet": {
"command": "npx",
"args": ["tsx", "/path/to/para-wallet-mcp/src/index.ts"],
"env": {
"PARA_API_KEY": "your_api_key_here"
}
}
}
}Development
npm run dev # Watch mode with tsx
npm run build # Compile TypeScript
npm start # Run compiled serverExample Workflow
create_wallet(type: "EVM", userIdentifier: "alice@example.com", userIdentifierType: "EMAIL")
→ wallet.id = "abc-123", status = "creating"
wait_for_wallet_ready(walletId: "abc-123")
→ status = "ready", address = "0x742d..."
sign_raw(walletId: "abc-123", data: "0x48656c6c6f")
→ signature = "a1b2c3..."License
MIT
Available Tools
5 toolscreate_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.
Inputs: type (required), userIdentifier (required), userIdentifierType (required), scheme, +1 more.
get_walletB
Get wallet details by ID, including status, address, and public key.
Inputs: walletId (required).
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.
Inputs: walletIds (required).
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.
Inputs: walletId (required), data (required).
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).
Inputs: walletId (required), maxWaitMs.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Crypto wallet for AI agents: balances, payments, swaps and trading with owner controls.
Native Solana staking for AI agents. 26 MCP tools, one-shot signing, webhooks.
Non-custodial DeFi tools for AI agents on Solana: swaps, perps, lending, staking, equities.
ERC-8004 agent identity, on-chain subscriptions, reputation, A2A tasks and chat over 53 tools.
Related MCP Servers
- AlicenseCqualityDmaintenanceEnables AI agents to interact with cryptocurrency ecosystems through wallet management, trading operations (swaps, DCA, limit orders), staking, and multi-chain support starting with Solana.37GPL 3.0
- AlicenseBqualityBmaintenanceProvides permissionless wallet infrastructure for AI agents to manage wallets, sign transactions, and handle tokens across Solana and all EVM-compatible chains. It includes 29 specialized tools for on-chain operations, featuring built-in security guards and automated x402 payment processing without KYC requirements.40399 npm3MIT
- AlicenseAqualityBmaintenanceEnables AI agents to manage USDC wallets on Solana, allowing them to send payments, create invoices, and access paid APIs within human-defined spending limits. It uses threshold signatures to provide agents with financial autonomy while ensuring secure oversight and transaction approval.3670 npm4Apache 2.0

Privy MCP Serverofficial
AlicenseBqualityDmaintenanceEnables AI agents to create wallets, sign transactions, and manage blockchain operations across multiple chains like Ethereum, Solana, and more via Privy.242MIT