Marketing Automation
Wati MCP connector
The Wati connector brings your WhatsApp contacts, broadcasts, chatbots and channels into Claude, ChatGPT, Cursor and other AI clients, so your team can ask about them and update them in plain language, with every action logged.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
94 tools
How to connect
How to connect Wati to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Wati once
-
Open Connections, choose Add connection, and pick Wati.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Wati API key. One person generates a token in Wati and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Wati to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Wati to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Wati to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Wati to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Wati through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Marketing
Check how a broadcast performed
Ask for the overview of last night's WhatsApp broadcast in Wati, see who was on the recipient list, and turn on automatic retry for the messages that did not go through.
-
Marketing
Estimate campaign cost before sending
Get a cost estimate for a planned broadcast and check the credits left on your Wati account before anything goes out.
-
Sales
Add a new lead after a call
Create the contact in Wati straight from your notes, fill in attributes like company, region and deal stage, and assign the contact to the right sales team.
-
Support
Route customers to the right team
Find a customer's contact in Wati and hand it to the billing, returns or onboarding team so the next WhatsApp message lands with the right people.
-
Customer success
Start a chatbot flow for a customer
Kick off an onboarding or feedback chatbot in Wati for a specific contact without opening the app, and confirm which chatbots are available first.
-
Operations
Clean up contact attributes in bulk
Ask how many contacts are in Wati, spot the ones with missing or outdated attributes, and update them in one pass instead of one at a time.
Try asking
- “Which contacts opened last week's broadcast?”
- “Assign this batch of contacts to the support team.”
- “How many contacts do we have per team?”
AI tools
Wati tools for your AI agents
94 tools are ready to call through Elaichi's MCP endpoint the moment you connect Wati, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Wati gets you
6 screens from the product, each doing one job for your Wati account.
The agent
Ask Wati questions, get live answers.
Type a question in plain language and get answers pulled straight from Wati contacts and broadcasts.
- contacts
- broadcasts
- attributes
- recipients
Ask Elaichi to work across your apps.
Which contacts opened last week's broadcast?
Assign this batch of contacts to the support team.
How many contacts do we have per team?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One Wati endpoint, any client, no api keys.
Claude, ChatGPT and Cursor all reach Wati through a single governed org endpoint.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
94 Wati tools, zero custom code.
Every Wati contact, broadcast and attribute method cataloged and ready to call.
- List all Wati contacts
- Get single Wati contact by ID
- Create a Wati contact
- Delete a Wati contact by ID
ElaichiToolsToolboxes
Every team gets its own Wati toolbox.
Marketing, support and sales each work from a toolbox scoped to their Wati needs.
- Marketing
- Support
- Sales
- Operations
ElaichiToolboxesShared connections
Teammates use Wati without seeing credentials.
See who connected each Wati account and how many teams and members share it.
- Marketing EMEA
- Support APAC
- Sales US
- Growth Team
ElaichiConnectionsAudit log
Every Wati action lands in one log.
See who did what in Wati, when, and on which contact or broadcast.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
Wati broadcasts run themselves, with your approval.
A schedule fires, Wati contacts are fetched and grouped, an agent drafts, a person approves, Wati posts back.
Wati digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch contacts
Wati
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Wati
Queued
Collections and dashboards
Wati health, computed, not asked for.
Four metrics and a 14 day contact chart refresh on schedule, broken down by team.
Wati health
Refreshed 4 minutes ago · every 15 minutes · from the contacts collection
Contacts
1,284 ↓ 12%
Broadcasts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Contacts created
Last 14 days
By team
Share of activity
Marketing EMEA 34%
Support APAC 27%
Sales US 21%
Growth Team 18%
FAQ
Frequently asked questions
How do I connect Wati to Claude?
Connect Wati in Elaichi first, which asks for the API key from your Wati account and nothing else. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in as yourself and your Wati contacts, broadcasts and chatbots are available in the chat.
Does Wati work with ChatGPT and Cursor as well as Claude?
Yes. Once Wati is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Wati once and every client picks it up.
What can an AI agent actually do with my Wati data?
With Wati connected, an agent can look up or create contacts, update their attributes one at a time or in bulk, assign contacts to teams, and start a chatbot for a customer. It can also review your broadcasts, pull the overview and recipient list for one, estimate what a broadcast will cost, turn on automatic retry, check remaining credits, and list your channels and what they are allowed to do. Wati has a large set of actions, so short concrete asks like "show me yesterday's broadcast overview" work better than long paragraphs.
Does connecting Wati give the AI access to my whole account?
Access to Wati follows the person who signed in and the key they connected with, so the agent can only reach the contacts, broadcasts and channels that person can already reach in Wati. Elaichi can narrow that further, for example to reading contacts but not deleting them, and it never widens it. Nothing becomes reachable through Elaichi that was not reachable in Wati already.
Can I stop an agent from deleting or changing things in Wati?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Wati contacts and broadcasts while blocking deleting contacts, editing attributes or starting chatbots. A blocked action is never shown to Claude, ChatGPT or Cursor at all, so no prompt, however worded, can reach it.
What happens to a Wati connection when someone leaves?
Offboarding a person in Elaichi ends their access to Wati at once, in every client they had connected. If they were using a shared Wati connection, it keeps working for everyone else on the team. If you want to remove Wati entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Put Wati in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.