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

Bring Web3
to CrewAI

Learn how to connect ThirdWeb to CrewAI and start using 29 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
Broadcast Solana TransactionComplete AuthCreate Solana WalletDeploy ContractExecute Solana SwapFetch With PaymentGet Payment RequirementsGet Solana BalanceGet Solana Swap QuoteGet Transaction StatusGet User DetailsGet Wallet MeInitiate AuthLink ProfileList Solana WalletsList TransactionsPregenerate WalletQuery EventsQuery TransactionsRead ContractSend Raw TransactionsSend Solana TokensSettle PaymentSign Solana MessageSign Solana TransactionSocial AuthUnlink ProfileVerify PaymentWrite Contract

Compatible with every major AI agent and IDE

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

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_auth and link_profile.
  • Wallet Management — Retrieve authenticated user details, search for users by address or email, and pre-generate wallets for new users via get_user_details and pregenerate_wallet.
  • Smart Contract Interaction — Execute read-only multicalls or state-changing transactions across any supported chain using read_contract and write_contract.
  • Event Monitoring — Query historical contract events with advanced filtering for data analysis using query_events.

How it works

  1. Subscribe to this server
  2. Provide your ThirdWeb Secret Key and API URL
  3. 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_solana_transaction

Broadcast a transaction on Solana

complete_auth

Verify challenge and complete login

create_solana_wallet

Create a Solana wallet

deploy_contract

Deploy a contract using bytecode and ABI

execute_solana_swap

Execute a token swap on Solana Mainnet

fetch_with_payment

Proxy a request to a paid API using x402

get_payment_requirements

Generate payment requirements for a resource (x402)

get_solana_balance

Get Solana wallet balance

get_solana_swap_quote

Get a token swap quote on Solana Mainnet

get_transaction_status

Get status of a transaction

get_user_details

Search for users in your project

get_wallet_me

Retrieve details of the authenticated user

initiate_auth

Start authentication process for email, phone, passkey, or SIWE

link_profile

Tie multiple social identities to a single wallet address

list_solana_wallets

List Solana wallets

list_transactions

List transactions

pregenerate_wallet

Create a wallet for a user before they first log in

query_events

Fetch historical events for a contract

query_transactions

Fetch transaction history for a contract

read_contract

Execute one or more read-only calls (multicall)

send_raw_transactions

Broadcast encoded transactions

send_solana_tokens

Send Solana tokens

settle_payment

Submit the payment on-chain (x402)

sign_solana_message

Sign a message on Solana

sign_solana_transaction

Sign a transaction on Solana

social_auth

OAuth flow for social providers

unlink_profile

Unlink a social identity from a wallet address

verify_payment

Validate a signed payment payload (x402)

write_contract

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

ThirdWeb in CrewAI

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

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.

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

ThirdWeb
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 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.

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

Frequently asked questions

01

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.

02

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.

03

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.

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 →