Bring Whatsapp Api
to LangChain
Learn how to connect Wati to LangChain and start using 13 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Wati MCP Server?
Connect your Wati WhatsApp Business account to any AI agent and simplify how you engage with your customers through natural conversation and automated messaging workflows.
What you can do
- Direct Messaging — Send instant WhatsApp session messages to active contacts for real-time support and engagement.
- Template Automation — Send pre-approved WhatsApp templates to start conversations or send notifications with dynamic parameters.
- Contact Management — List and inspect your WhatsApp subscribers and contacts to keep your directory up-to-date.
- Chat History — Retrieve the complete message history for any specific contact to understand the conversation context.
- Template Catalog — List all available message templates to identify the best options for your communication strategy.
How it works
1. Subscribe to this server
2. Enter your Wati API Key and API Endpoint (found in your Wati API dashboard)
3. Start managing your WhatsApp communication from Claude, Cursor, or any MCP client
Who is this for?
- Customer Support Teams — quickly respond to inquiries and retrieve chat history via simple AI commands.
- Sales & Marketing — automate the sending of template-based notifications and manage lead contacts directly.
- Operations Managers — monitor communication flows and verify template availability without leaving the workspace.
Built-in capabilities (13)
Add a contact
Verify connectivity
Get contact details
Get template details
List broadcasts
List contacts
List messages
List tags
List message templates
Send media message
Send a session message
Send a template message
Update contact attributes
Why LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Wati through native MCP adapters. Connect 13 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 Wati 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 Wati queries for multi-turn workflows
Wati in LangChain
Wati and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Wati 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 Wati in LangChain
The Wati 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 13 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
Wati for LangChain
Every tool call from LangChain to the Wati MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
What is the difference between a session message and a template message?
Session messages can only be sent if the user has messaged you in the last 24 hours. Template messages are pre-approved by WhatsApp and can be used to initiate a conversation at any time.
How do I see the approved templates in my account?
Use the list_message_templates query. Your agent will retrieve the complete list of pre-approved WhatsApp templates available in your Wati dashboard.
Can I retrieve the last messages from a specific customer?
Yes! Use the list_chat_history tool and provide the customer's WhatsApp number. The agent will return the message history for that specific conversation.
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