Privy MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRIVY_APP_ID | Yes | Your Privy App ID | |
| PRIVY_APP_SECRET | Yes | Your Privy App Secret | |
| PRIVY_API_BASE_URL | No | Custom API URL | https://api.privy.io/v1 |
| PRIVY_AUTHORIZATION_PRIVATE_KEY | No | For signing ops on owner-controlled wallets |
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 |
|---|---|
| get_walletsB | Retrieves a list of wallets associated with the Privy application. |
| get_wallet_detailsB | Retrieves details for a specific wallet by its ID. |
| create_walletB | Creates a new app-owned wallet. App-owned wallets are fully managed by your Privy app. |
| update_walletC | Updates a wallet's policies. |
| get_wallet_balanceA | Retrieves the balance of a wallet for a specific asset and chain. |
| get_wallet_transactionsC | Retrieves transaction history for a specific wallet. |
| personal_signB | Sign a message using the personal_sign method with a specified wallet. |
| eth_signTransactionC | Sign a transaction using the eth_signTransaction method with a specified wallet. |
| eth_signTypedData_v4C | Sign EIP-712 typed data using eth_signTypedData_v4 method. |
| secp256k1_signC | Sign a hash using the secp256k1 method. |
| raw_signA | Sign a raw hash using the wallet's private key along the blockchain's cryptographic curve. |
| eth_sendTransactionB | Sign and broadcast a transaction to the blockchain network. |
| solana_signMessageC | Sign a message with a Solana wallet. |
| solana_signTransactionA | Sign a transaction with a Solana wallet without broadcasting it. |
| solana_signAndSendTransactionC | Sign and broadcast a transaction with a Solana wallet. |
| create_policyB | Create a new wallet policy with rules governing transaction behavior. |
| get_policyA | Retrieves a policy by its ID. |
| update_policyB | Updates an existing policy by its ID. |
| delete_policyB | Deletes a policy by its ID. |
| add_rule_to_policyC | Adds a new rule to an existing policy. |
| get_policy_ruleB | Retrieves a specific rule from a policy. |
| update_policy_ruleB | Updates an existing rule within a policy. |
| delete_policy_ruleB | Deletes a specific rule from a policy. |
| get_transactionB | Retrieves transaction details by transaction ID. |
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 24 tools
Each tool has a clearly distinct purpose: wallet CRUD, different signing methods (Ethereum vs Solana, various formats), policy management, and transaction retrieval. No two tools overlap in functionality.
All tool names follow a consistent verb_noun snake_case pattern (e.g., create_wallet, delete_policy_rule). Even longer names like solana_signAndSendTransaction adhere to this convention without mixing styles.
With 24 tools, the server is on the upper end of the 'heavy' range, but each tool serves a specific need in wallet management, multi-chain signing, and policy administration. No obvious redundancy or bloat.
The tool set covers wallet CRUD (except deletion), extensive signing operations, and full policy lifecycle management. The absence of a delete_wallet tool is a notable gap, though other core workflows are well-supported.