4,000+ servers built on vurb.ts
Vinkius

ThirdWeb MCP Server for CrewAIGive CrewAI instant access to 29 tools to Broadcast Solana Transaction, Complete Auth, Create Solana Wallet, and more

MCP Inspector GDPR Free for Subscribers

Connect your CrewAI agents to ThirdWeb through Vinkius, pass the Edge URL in the `mcps` parameter and every ThirdWeb tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

The ThirdWeb MCP Server for CrewAI is a standout in the Developer Tools category — giving your AI agent 29 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="ThirdWeb Specialist",
    goal="Help users interact with ThirdWeb effectively",
    backstory=(
        "You are an expert at leveraging ThirdWeb tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in ThirdWeb "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 29 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
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

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

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.

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.

The ThirdWeb MCP Server exposes 29 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 29 ThirdWeb tools available for CrewAI

When CrewAI connects to ThirdWeb through Vinkius, your AI agent gets direct access to every tool listed below — spanning web3, smart-contracts, wallet-management, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

broadcast

Broadcast solana transaction on ThirdWeb

Broadcast a transaction on Solana

complete

Complete auth on ThirdWeb

Verify challenge and complete login

create

Create solana wallet on ThirdWeb

Create a Solana wallet

deploy

Deploy contract on ThirdWeb

Deploy a contract using bytecode and ABI

execute

Execute solana swap on ThirdWeb

Execute a token swap on Solana Mainnet

fetch

Fetch with payment on ThirdWeb

Proxy a request to a paid API using x402

get

Get payment requirements on ThirdWeb

Generate payment requirements for a resource (x402)

get

Get solana balance on ThirdWeb

Get Solana wallet balance

get

Get solana swap quote on ThirdWeb

Get a token swap quote on Solana Mainnet

get

Get transaction status on ThirdWeb

Get status of a transaction

get

Get user details on ThirdWeb

Search for users in your project

get

Get wallet me on ThirdWeb

Retrieve details of the authenticated user

initiate

Initiate auth on ThirdWeb

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

link

Link profile on ThirdWeb

Tie multiple social identities to a single wallet address

list

List solana wallets on ThirdWeb

List Solana wallets

list

List transactions on ThirdWeb

List transactions

pregenerate

Pregenerate wallet on ThirdWeb

Create a wallet for a user before they first log in

query

Query events on ThirdWeb

Fetch historical events for a contract

query

Query transactions on ThirdWeb

Fetch transaction history for a contract

read

Read contract on ThirdWeb

Execute one or more read-only calls (multicall)

send

Send raw transactions on ThirdWeb

Broadcast encoded transactions

send

Send solana tokens on ThirdWeb

Send Solana tokens

settle

Settle payment on ThirdWeb

Submit the payment on-chain (x402)

sign

Sign solana message on ThirdWeb

Sign a message on Solana

sign

Sign solana transaction on ThirdWeb

Sign a transaction on Solana

social

Social auth on ThirdWeb

OAuth flow for social providers

unlink

Unlink profile on ThirdWeb

Unlink a social identity from a wallet address

verify

Verify payment on ThirdWeb

Validate a signed payment payload (x402)

write

Write contract on ThirdWeb

Execute one or more state-changing calls atomically

Connect ThirdWeb to CrewAI via MCP

Follow these steps to wire ThirdWeb into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install CrewAI

Run pip install crewai
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
03

Customize the agent

Adjust the role, goal, and backstory to fit your use case
04

Run the crew

Run python crew.py. CrewAI auto-discovers 29 tools from ThirdWeb

Why Use CrewAI with the ThirdWeb MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with ThirdWeb through the Model Context Protocol.

01

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

02

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

03

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

04

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 + CrewAI Use Cases

Practical scenarios where CrewAI combined with the ThirdWeb MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries ThirdWeb for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries ThirdWeb, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain ThirdWeb tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries ThirdWeb against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for ThirdWeb in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with ThirdWeb immediately.

01

"Read the total supply of the contract 0x123... on chain 1."

02

"Start an email authentication for dev@example.com."

03

"Search for user details associated with address 0xAbc123..."

Troubleshooting ThirdWeb MCP Server with CrewAI

Common issues when connecting ThirdWeb to CrewAI through Vinkius, and how to resolve them.

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

ThirdWeb + CrewAI FAQ

Common questions about integrating ThirdWeb MCP Server with CrewAI.

01

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

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

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

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

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.

Explore More MCP Servers

View all →