Bring Sms Marketing
to LangChain
Learn how to connect Tatango to LangChain 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 LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Tatango through native MCP adapters. Connect 12 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine Tatango MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across Tatango queries for multi-turn workflows
Tatango in LangChain
Tatango and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Tatango to LangChain 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 LangChain
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 LangChain 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 LangChain
Every tool call from LangChain 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 LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters
