Bring Sms Marketing
to CrewAI
Learn how to connect Tatango to CrewAI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Tatango MCP Server?
Connect your Tatango account to any AI agent and simplify how you manage your high-volume SMS marketing, subscriber lists, and campaign outreach through natural conversation.
What you can do
- Subscriber Management — List and search subscribers, add new phone numbers to lists, and handle unsubscribes programmatically.
- Broadcast Campaigns — Create and send mass SMS campaigns to specific marketing lists and monitor their performance.
- Transactional SMS — Send one-to-one non-marketing messages like alerts, receipts, and notifications.
- List Oversight — Manage your marketing directories by listing and inspecting metadata for each subscriber list.
- Webhook Monitoring — List active webhooks to ensure your outbound events and integrations are running smoothly.
- Account Visibility — Fetch your profile details and check API health directly from the agent.
How it works
1. Subscribe to this server
2. Enter your Tatango API Key (found in your account settings)
3. Start managing your SMS outreach from Claude, Cursor, or any MCP client
Who is this for?
- Political & Non-Profit Teams — quickly execute mass alerts and manage large subscriber lists via simple AI commands.
- Marketing Managers — monitor campaign statuses and verify list growth directly from the workspace.
- Operations Leads — automate transactional notifications and verify API connectivity via the AI assistant.
Built-in capabilities (12)
Can trigger an opt-in confirmation. Add a subscriber to a list
Verify Tatango API connectivity
Create and send a broadcast message
Get authenticated account info
Get details for a specific list
Get info for a specific phone number
List active webhooks
List all broadcast campaigns
List all marketing lists
List subscribers for a specific list
g., receipt, alert) to a phone number. Max 160 chars. Send a one-to-one transactional message
Remove a subscriber from a list
Why CrewAI?
When paired with CrewAI, Tatango becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Tatango 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
Tatango in CrewAI
Tatango and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Tatango 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 Tatango in CrewAI
The Tatango 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 12 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
Tatango for CrewAI
Every tool call from CrewAI to the Tatango 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 an SMS to a whole list using the AI?
Yes! Use the create_broadcast_campaign tool. Provide the List ID and your message text. Your agent will trigger the broadcast to all subscribers in that list instantly.
How do I add a new phone number to a marketing list?
Use the add_new_sms_subscriber action. Provide the phone number and the target List ID. The agent will instantly register the new subscriber in Tatango.
Is it possible to see my recent broadcast history via AI?
Absolutely. Run the list_sms_campaigns query. The agent will retrieve a history of all broadcast messages sent from your account, allowing you to monitor past outreach.
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.