Skip to main content
Glama
Para Wallet MCP Server
by getpara

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_wallet

Create an MPC wallet (EVM, Solana, Cosmos)

get_wallet

Get wallet status and address

sign_raw

Sign 0x-hex data via MPC

list_wallets

Batch-fetch multiple wallets by ID

wait_for_wallet_ready

Poll until wallet is ready after creation

Related MCP server: AgentWallet MCP Server

Setup

  1. Get a Para API key at developer.getpara.com

  2. Allowlist your server IP in the Para dashboard

  3. Clone and install:

git clone https://github.com/adeets-22/para-wallet-mcp.git
cd para-wallet-mcp
npm install
npm run build
  1. Copy .env.example to .env and add your API key:

cp .env.example .env

MCP 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 server

Example 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 tools
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.

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

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      B
      maintenance
      Provides 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.
      40
      399 npm
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      36
      70 npm
      4
      Apache 2.0