4,000+ servers built on vurb.ts
Vinkius

Mitto MCP Server for CrewAIGive CrewAI instant access to 27 tools to Add Masked Number, Add Masking Participant, Cancel 2fa, and more

MCP Inspector GDPR Free for Subscribers

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

Ask AI about this MCP Server for CrewAI

The Mitto MCP Server for CrewAI is a standout in the Communication Messaging category — giving your AI agent 27 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="Mitto Specialist",
    goal="Help users interact with Mitto effectively",
    backstory=(
        "You are an expert at leveraging Mitto 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 Mitto "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 27 available tools "
        "and what they can do."
    ),
)

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

Connect your Mitto account to any AI agent to handle global communication workflows through natural conversation.

When paired with CrewAI, Mitto becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Mitto 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

  • SMS Messaging — Send single or bulk SMS messages globally with custom sender IDs and delivery tracking.
  • Two-Factor Authentication (2FA) — Generate, send, and verify OTP codes via SMS or Voice channels to secure your user accounts.
  • Number Lookup — Validate phone numbers and retrieve carrier information to ensure deliverability.
  • Usage Analytics — Monitor your SMS and 2FA usage statistics grouped by country or date ranges.
  • Application Management — Manage your Mitto applications and masked numbers for privacy-focused communication.

The Mitto MCP Server exposes 27 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 27 Mitto tools available for CrewAI

When CrewAI connects to Mitto through Vinkius, your AI agent gets direct access to every tool listed below — spanning sms-api, two-factor-authentication, otp-verification, 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.

add

Add masked number on Mitto

Add a masked number

add

Add masking participant on Mitto

Add a masking participant

cancel

Cancel 2fa on Mitto

Cancel a 2FA OTP request

create

Create masking application on Mitto

Create a number masking application

create

Create masking context on Mitto

Create a masking context

delete

Delete masked number on Mitto

Delete a masked number

delete

Delete masking application on Mitto

Delete a number masking application

delete

Delete masking context on Mitto

Delete a masking context

delete

Delete masking participant on Mitto

Delete a masking participant

get

Get 2fa usage on Mitto

Get 2FA usage records

get

Get sms usage by country on Mitto

Get SMS usage by country

list

List masked numbers on Mitto

List masked numbers

list

List masking applications on Mitto

List number masking applications

list

List masking contexts on Mitto

List masking contexts

list

List masking participants on Mitto

List masking participants

lookup

Lookup number on Mitto

Lookup mobile number information

search

Search 2fa on Mitto

Search 2FA SDRs

search

Search masking interactions on Mitto

Search masking interactions

send

Send 2fa on Mitto

Send a 2FA OTP message

send

Send bulk sms on Mitto

Send bulk SMS messages

send

Send sms on Mitto

Send a single SMS message

set

Set 2fa limits on Mitto

Set 2FA limits

set

Set 2fa workflows on Mitto

g., SMS to Voice) for 2FA. Set 2FA workflows

track

Track sms conversion on Mitto

Track SMS conversion

update

Update masking application on Mitto

Update a number masking application

update

Update masking context on Mitto

Update a masking context

verify

Verify 2fa on Mitto

Verify a 2FA OTP code

Connect Mitto to CrewAI via MCP

Follow these steps to wire Mitto 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 27 tools from Mitto

Why Use CrewAI with the Mitto MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Mitto 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

Mitto + CrewAI Use Cases

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

01

Automated multi-step research: a reconnaissance agent queries Mitto 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 Mitto, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Mitto 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 Mitto against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Mitto in CrewAI

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

01

"Send an SMS to +1234567890 saying 'Your order is ready for pickup!' from 'MyStore'."

02

"Send a 2FA verification code to +447700900123."

03

"Lookup the phone number +4915123456789 to see the carrier info."

Troubleshooting Mitto MCP Server with CrewAI

Common issues when connecting Mitto 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.

Mitto + CrewAI FAQ

Common questions about integrating Mitto 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 →