Compatible with every major AI agent and IDE
What is the ThirdWeb MCP Server?
Connect your ThirdWeb account to any AI agent to build and manage Web3 applications through natural language. This server provides a comprehensive suite of tools for blockchain interaction and identity management.
What you can do
- Authentication & Identity — Handle email, SMS, social, and passkey logins. Link multiple social profiles to a single wallet address using
initiate_authandlink_profile. - Wallet Management — Retrieve authenticated user details, search for users by address or email, and pre-generate wallets for new users via
get_user_detailsandpregenerate_wallet. - Smart Contract Interaction — Execute read-only multicalls or state-changing transactions across any supported chain using
read_contractandwrite_contract. - Event Monitoring — Query historical contract events with advanced filtering for data analysis using
query_events.
How it works
- Subscribe to this server
- Provide your ThirdWeb Secret Key and API URL
- Start building Web3 workflows from your favorite MCP client
Who is this for?
- Web3 Developers — Rapidly prototype contract interactions and test auth flows directly from the IDE.
- DApp Operators — Manage user profiles and monitor contract events without custom scripts.
- Product Managers — Query on-chain data and user details to understand platform activity.
Built-in capabilities (29)
Broadcast a transaction on Solana
Verify challenge and complete login
Create a Solana wallet
Deploy a contract using bytecode and ABI
Execute a token swap on Solana Mainnet
Proxy a request to a paid API using x402
Generate payment requirements for a resource (x402)
Get Solana wallet balance
Get a token swap quote on Solana Mainnet
Get status of a transaction
Search for users in your project
Retrieve details of the authenticated user
Start authentication process for email, phone, passkey, or SIWE
Tie multiple social identities to a single wallet address
List Solana wallets
List transactions
Create a wallet for a user before they first log in
Fetch historical events for a contract
Fetch transaction history for a contract
Execute one or more read-only calls (multicall)
Broadcast encoded transactions
Send Solana tokens
Submit the payment on-chain (x402)
Sign a message on Solana
Sign a transaction on Solana
OAuth flow for social providers
Unlink a social identity from a wallet address
Validate a signed payment payload (x402)
Execute one or more state-changing calls atomically
Why CrewAI?
When paired with CrewAI, ThirdWeb becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call ThirdWeb 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
mcpsparameter 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
ThirdWeb in CrewAI
ThirdWeb and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect ThirdWeb 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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for ThirdWeb in CrewAI
The ThirdWeb 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 29 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.

* 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
How Vinkius secures
ThirdWeb for CrewAI
Every tool call from CrewAI to the ThirdWeb MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I read data from a smart contract without paying gas?
Yes! Use the read_contract tool. It performs read-only calls (multicall) to the blockchain, which do not require gas or state changes.
How do I start an authentication flow for a new user?
You can use the initiate_auth tool by specifying the method (email, sms, etc.) and the user's identifier. Then, use complete_auth with the verification code to finish the login.
Can I find a user's profile if I only have their wallet address?
Absolutely. Use the get_user_details tool and provide the address parameter. The agent will return any associated user IDs, emails, or phone numbers linked to that wallet in your project.
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.
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.
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.
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.
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.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
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 →
Tailscale
13 toolsManage your Tailscale mesh network — list devices, update ACL policies, manage auth keys, and inspect users directly from any AI agent.

Reverb
30 toolsManage your Reverb shop — create listings, track orders, handle payouts, and communicate with buyers directly via AI.

HotDocs
14 toolsAutomate document assembly via HotDocs Advance — list templates, create work items, conduct interviews, and generate documents directly from any AI agent.

Vapi
10 toolsCommand Voice AI assistants directly from your chat. Make outbound phone calls, update personas, and retrieve full transcripts via Vapi.
