4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Privy MCP Server

Bring Web3
to CrewAI

Learn how to connect Privy to CrewAI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Batch Create WalletsCreate UserCreate WalletDelete UserGet TransactionGet Transaction By External IdGet UserGet User By EmailGet WalletSearch UsersUpdate WalletWallet Rpc

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Privy

What is the Privy MCP Server?

Connect your Privy application to any AI agent to streamline user onboarding and wallet management in your Web3 application through natural language.

What you can do

  • User Management — Create new users, search for existing ones by term or email, and retrieve full profile metadata.
  • Embedded Wallets — Provision new wallets (Ethereum, Solana, Bitcoin, Sui) for your users individually or in batches of up to 100.
  • Wallet Operations — Update wallet metadata, policies, and ownership, or retrieve specific wallet details via ID.
  • Blockchain Actions — Execute RPC methods like signing messages or sending transactions directly through managed wallets.
  • Data Maintenance — Securely delete user records when they are no longer needed.

How it works

  1. Subscribe to this server
  2. Enter your Privy App ID and App Secret
  3. Start managing your Web3 identity and wallet infrastructure from Claude, Cursor, or any MCP client

Who is this for?

  • Web3 Developers — quickly inspect user accounts or provision test wallets without leaving the code editor.
  • Product Managers — search for user profiles and verify linked accounts or wallet statuses during support or planning.
  • DevOps & Security — automate user lifecycle management and wallet policy updates via a conversational interface.

Built-in capabilities (12)

batch_create_wallets

Batch create wallets

create_user

Create a new user object with linked accounts

create_wallet

Create a new wallet

delete_user

Delete a user

get_transaction

Get a transaction

get_transaction_by_external_id

Get a transaction by external ID

get_user

Get a user by ID

get_user_by_email

Get a user by email address

get_wallet

Get wallet details

search_users

Search for users

update_wallet

Update a wallet

wallet_rpc

Perform a wallet RPC action

Why CrewAI?

When paired with CrewAI, Privy becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Privy tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

Privy in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Privy and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Privy to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Privy in CrewAI

The Privy MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Privy
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Privy for CrewAI

Every tool call from CrewAI to the Privy MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I find a user if I only have their email address?

Yes. You can use the get_user_by_email tool to retrieve the full user object and linked accounts associated with that specific email address.

02

Is it possible to create multiple wallets for a large group of users at once?

Absolutely. The batch_create_wallets tool allows you to create up to 100 wallets in a single request, which is ideal for bulk onboarding or migration tasks.

03

Can the AI agent perform transactions on behalf of a wallet?

Yes, using the wallet_rpc tool. You can specify the wallet_id and the RPC method (like eth_sendTransaction) to execute blockchain actions through Privy's infrastructure.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →