Bring Bulk Sms
to CrewAI
Learn how to connect SMS Masivo to CrewAI and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the SMS Masivo MCP Server?
Connect your SMS Masivo account to any AI agent and automate your SMS communications through natural conversation.
What you can do
- Send SMS — Send individual messages to any international phone number.
- Bulk Messaging — Send the same message to multiple recipients at once.
- Scheduled Delivery — Schedule SMS for future delivery at a specific date and time.
- Delivery Reports — Track real-time delivery status for individual or batch messages.
- Contacts — Manage your contact directory and create new entries.
- Groups — View contact groups for campaign targeting.
- Balance — Check your available SMS credits.
How it works
1. Subscribe to this server
2. Enter your SMS Masivo API key
3. Start sending messages from Claude, Cursor, or any MCP client
Who is this for?
- Marketing Teams — send bulk SMS campaigns and track delivery rates.
- Customer Support — send transactional notifications and appointment reminders.
- Sales Teams — automate follow-up messaging with scheduled delivery.
Built-in capabilities (10)
Verify SMS Masivo API connectivity
Create a new contact
Check your SMS credit balance
Get the delivery report for a specific message
List all contacts in your account
List delivery reports by date range
List all contact groups
Provide the date in ISO 8601 format. Schedule an SMS for future delivery
Provide comma-separated numbers in international format. Send the same SMS to multiple recipients
Optionally provide a campaign name for tracking. Send an SMS message to a single recipient
Why CrewAI?
When paired with CrewAI, SMS Masivo becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call SMS Masivo 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
SMS Masivo in CrewAI
SMS Masivo and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect SMS Masivo 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 | 3,400+ 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 SMS Masivo in CrewAI
The SMS Masivo 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 10 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
SMS Masivo for CrewAI
Every tool call from CrewAI to the SMS Masivo MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I send SMS to multiple recipients at once?
Yes! Use send_bulk_sms with a comma-separated list of phone numbers in international format. All recipients receive the same message.
How do I check if my message was delivered?
Use get_delivery_report with the transmission ID returned when the SMS was sent. It shows real-time delivery status (delivered, pending, failed).
Can I schedule messages for later?
Yes! Use schedule_sms with the delivery date in ISO 8601 format (e.g., 2025-01-15T14:00:00Z). The message will be sent at the specified time.
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.