3,400+ MCP servers ready to use
Vinkius

Tatango MCP Server for CrewAIGive CrewAI instant access to 12 tools to Add New Sms Subscriber, Check Api Health, Create Broadcast Campaign, and more

Built by Vinkius GDPR 12 Tools Framework

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

Use with Your AI Agent

Ask AI about this App Connector for CrewAI

Open in ChatGPT Open in Claude Open in Perplexity

The Tatango app connector for CrewAI is a standout in the Communication Messaging category — giving your AI agent 12 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

python
from crewai import Agent, Task, Crew

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

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

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.

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.

The Tatango MCP Server exposes 12 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.

All 12 Tatango tools available for CrewAI

When CrewAI connects to Tatango through Vinkius, your AI agent gets direct access to every tool listed below — spanning sms-marketing, mms-campaigns, tcpa-compliance, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.

add_new_sms_subscriber

Can trigger an opt-in confirmation. Add a subscriber to a list

check_api_health

Verify Tatango API connectivity

create_broadcast_campaign

Create and send a broadcast message

get_account_profile

Get authenticated account info

get_list_details

Get details for a specific list

get_subscriber_details

Get info for a specific phone number

list_configured_webhooks

List active webhooks

list_sms_campaigns

List all broadcast campaigns

list_sms_marketing_lists

List all marketing lists

list_sms_subscribers

List subscribers for a specific list

send_transactional_sms

g., receipt, alert) to a phone number. Max 160 chars. Send a one-to-one transactional message

unsubscribe_phone_number

Remove a subscriber from a list

Connect Tatango to CrewAI via MCP

Follow these steps to wire Tatango into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind the 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 12 tools from Tatango

Why Use CrewAI with the Tatango MCP Server

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

Tatango + CrewAI Use Cases

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

01

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

03

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

Example Prompts for Tatango in CrewAI

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

01

"List all my SMS marketing lists."

02

"Send a broadcast to the 'Volunteer Alerts' list: 'Meeting relocated to Hall B. See you there!'."

03

"Add +15550199 to the 'Main Supporters' list."

Troubleshooting Tatango MCP Server with CrewAI

Common issues when connecting Tatango to CrewAI through the 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.

Tatango + CrewAI FAQ

Common questions about integrating Tatango 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.