Privy.io MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRIVY_APP_ID | Yes | Your Privy App ID from dashboard.privy.io | |
| PRIVY_APP_SECRET | Yes | Your Privy App Secret from dashboard.privy.io |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_userA | Get user details by Privy DID (decentralized identifier). Returns user data including linked accounts (email, phone, wallet, OAuth providers), MFA methods, creation timestamps, terms acceptance, and custom metadata. |
| list_usersA | List all users with pagination support. Returns paginated list of users with their linked accounts, wallets, and metadata. |
| get_user_by_walletA | Query and retrieve user information by blockchain wallet address. Supports Ethereum, Solana, Bitcoin, and all EVM-compatible chains. |
| create_userA | Create a new user with linked accounts. Supports email, phone, wallet, and 15+ OAuth providers (Apple, Discord, GitHub, Google, Farcaster, Telegram, Twitter, etc.). Optionally creates an embedded wallet. |
| delete_userA | Delete a user by Privy DID. This action is permanent and removes all associated data. |
| search_usersA | Search for users by search term OR specific identifiers (emails, phone numbers, wallet addresses). Note: Use either search_term OR specific identifiers, not both. Returns user data matching the search criteria including linked accounts, MFA methods, and metadata. |
| get_walletA | Get wallet details by wallet ID. Returns wallet address, chain type, creation/export/import timestamps, policy IDs, and owner information. |
| list_walletsB | List all wallets with pagination. Returns wallet addresses, chain types, and associated metadata. |
| create_walletC | Create or pregenerate a wallet for a user. Supports Ethereum, Solana, Bitcoin, and all EVM-compatible chains. |
| get_wallet_balanceB | Get the current balance of a wallet. |
| get_wallet_transactionsB | Get transaction history for a wallet with pagination support. |
| update_walletC | Update wallet metadata and configuration. |
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 12 tools
Each tool has a clearly distinct purpose: user creation vs wallet creation, different retrieval methods (by DID, by wallet address, search), and separate actions for wallets (balance, transactions, update). No overlapping functionality.
All tools follow a consistent verb_noun pattern (create_user, get_wallet_balance, list_users) with occasional prepositions for specificity (get_user_by_wallet). No mixing of conventions or vague verbs.
12 tools cover the main operations for user and wallet management without being excessive. Each tool serves a clear need, and the count is appropriate for the server's scope.
Covers most CRUD operations: create, read, delete for users; create, read, update for wallets. Missing update_user and delete_wallet, but the core workflows are well-supported, and agents can likely work around minor gaps.