Bring Whatsapp Api
to LlamaIndex
Learn how to connect Wati to LlamaIndex 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 LlamaIndex?
LlamaIndex agents combine Wati tool responses with indexed documents for comprehensive, grounded answers. Connect 13 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
- —
Data-first architecture: LlamaIndex agents combine Wati tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain Wati tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query Wati, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what Wati tools were called, what data was returned, and how it influenced the final answer
Wati in LlamaIndex
Wati and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Wati to LlamaIndex 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 LlamaIndex
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 LlamaIndex 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 LlamaIndex
Every tool call from LlamaIndex 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 LlamaIndex connect to MCP servers?
Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
Can I combine MCP tools with vector stores?
Yes. LlamaIndex agents can query Wati tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp