Do I need a Smithery account to use this MCP server?

Yes, you need a free Smithery account to generate an API key. Sign up at smithery.ai, then go to Account Settings > API Keys to create your key. The key gives access to the registry search, server details, and connection management features.

How does Smithery Connect handle OAuth for MCP servers?

Smithery Connect automatically handles OAuth flows, token refresh, and session management for MCP servers that require authentication. You don't need to configure redirect URIs, client IDs, or manage token expiration. Simply create a connection and Smithery manages the authentication lifecycle, providing your agents with seamless access.

Can I search for verified MCP servers only?

Yes! Use the verified filter in the search_servers tool by setting verified=true. This returns only servers that have been verified by Smithery, ensuring higher quality and security standards. Verified servers display a verification badge and have undergone additional review.

Smithery MCP Server for CrewAI 11 tools — connect in under 2 minutes

Name: Smithery
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 11 Tools Framework

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

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Smithery Specialist",
    goal="Help users interact with Smithery effectively",
    backstory=(
        "You are an expert at leveraging Smithery 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 Smithery "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 11 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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 Smithery MCP Server

What you can do

Connect AI agents to the Smithery Registry for comprehensive MCP server discovery and management:

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

Search MCP servers — find servers by name, description, or tags with semantic search
Get server details — review metadata, verification status, and user counts
Discover tools — list all tools (functions) exposed by any registered MCP server
Discover resources — list all data resources available from MCP servers
Discover prompts — list all prompt templates exposed by MCP servers
Create connections — connect to MCP servers via Smithery Connect with automatic OAuth handling
Manage connections — list, inspect, and remove MCP server connections
Generate service tokens — create scoped, time-limited tokens for frontend/agent access
View analytics — monitor server usage, adoption trends, and performance metrics

The Smithery MCP Server exposes 11 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Smithery to CrewAI via MCP

Follow these steps to integrate the Smithery MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

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

Customize the agent

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

Run the crew

Run python crew.py — CrewAI auto-discovers 11 tools from Smithery

Why Use CrewAI with the Smithery MCP Server

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

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

Smithery + CrewAI Use Cases

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

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

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

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

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

Smithery MCP Tools for CrewAI (11)

These 11 tools become available when you connect Smithery to CrewAI via MCP:

create_connection

Smithery handles OAuth, tokens, and sessions automatically. Requires the server namespace and connection configuration (mcpUrl, optional headers, metadata). Returns the connection ID, status, and server info. Use this to integrate MCP servers into your applications without managing authentication complexity. Create a new connection to an MCP server via Smithery Connect

create_service_token

The token has limited permissions defined by the policy (namespaces, resources, operations, metadata, TTL). Returns the token string. Use this to provide secure, time-limited access to MCP servers without exposing your main API key. Generate a scoped service token for frontend/agent access to MCP servers

delete_connection

This action cannot be undone. Requires namespace and connection ID. Use this to clean up unused connections or revoke access. Remove an MCP server connection

get_connection

Requires namespace and connection ID. Use this to review connection details or troubleshoot connectivity issues. Get detailed information about a specific MCP connection

get_server_analytics

Requires the server qualified name. Use this to monitor server adoption, identify usage trends, or troubleshoot performance issues. Get usage analytics for a specific MCP server

get_server_details

Requires the qualified name (e.g., "smithery/hello-world" or "github/github") from search_servers results. Use this to review server capabilities before connecting. Get detailed information about a specific MCP server from the Smithery registry

get_server_prompts

Returns prompt names, descriptions, and argument definitions. Requires the server qualified name. Use this to discover reusable prompt workflows available from the server. List all prompt templates exposed by a specific MCP server

get_server_resources

Returns resource URIs, names, descriptions, and MIME types. Requires the server qualified name. Use this to understand what data the server provides read access to. List all resources exposed by a specific MCP server

get_server_tools

Returns tool names, descriptions, input schemas, and annotations. Requires the server qualified name. Use this to understand what actions the server can perform before connecting it to your agents. List all tools exposed by a specific MCP server

list_connections

Returns connection IDs, names, statuses, creation dates, and metadata. Use this to audit which connections are active, review connection configurations, or identify unused connections. List all connections for a specific MCP server namespace

search_servers

Returns matching servers with qualified names, descriptions, verification status, user counts, and deployment info. Use optional filters to narrow by namespace, verified status, or deployment state. Results include pagination metadata. Use this as the first step to discover available MCP servers before connecting or installing them. Search the Smithery registry for MCP servers by name, description, or tags

Example Prompts for Smithery in CrewAI

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

"Search for verified GitHub-related MCP servers"

"Show me all tools exposed by the Stripe MCP server"

"Create a connection to the Slack MCP server for my workspace"

Troubleshooting Smithery MCP Server with CrewAI

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

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

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

Smithery + CrewAI FAQ

Common questions about integrating Smithery MCP Server with CrewAI.

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.