Can my team share one Wati connection?

Yes. One person connects Wati with the API key and shares the connection with a team in Elaichi, and nobody else ever sees or handles the key. Each teammate still signs in as themselves, so every contact update or chatbot start in Wati is logged with their name, not a shared account.

Marketing Automation

Wati MCP connector

The Wati connector brings your WhatsApp contacts, broadcasts, chatbots and channels into Claude, ChatGPT, Cursor, Microsoft Copilot and other AI clients, so your team can ask about them and update them in plain language, with every action logged.

Connect on Elaichi How to connect

Connects with an API key
Free 14-day trial
No credit card

Claude Elaichi connected

Which contacts opened last week's broadcast?

Working in Wati with Elaichi

List all Wati contacts
Get single Wati contact by ID
Wati contacts get count

Ask anything…

Governance / Audit log Last 24 hours

Wati contacts get count Emily Carter ·

9:41 AM Done

Get single Wati contact by ID Emily Carter ·

9:41 AM Done

List all Wati contacts Emily Carter ·

9:41 AM Done

Create a Wati contact Megan Brooks ·

9:38 AM Done

Wati contacts assign teams Ryan Hayes ·

9:35 AM Done

How to connect Wati to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Wati MCP connector for 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.

Wati MCP connector for Claude Code

1

In a terminal, run claude mcp add with the endpoint.

https://api.elaichi.ai/mcp
2

Start Claude Code and run /mcp.
3

Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Wati MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.

Wati MCP connector for 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.

Wati MCP connector for Microsoft Copilot

1

In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2

Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

https://api.elaichi.ai/mcp
3

Create a new connection, sign in and approve, then press Add to agent.
4

Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL: https://api.elaichi.ai/mcp
Authentication: OAuth 2.0
Type: Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

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.

Connect Wati on Elaichi See pricing

What teams do with Wati through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Wati is logged.

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?”

See all 94 Wati tools →

What connecting Wati gets you

6 screens from Elaichi, each doing one job for your Wati account.

Elaichi Agent

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, Cursor or Microsoft Copilot

The agent

Ask Wati questions, get live answers.

Type a question in plain language and get answers pulled straight from Wati contacts and broadcasts.

ElaichiAI apps

Claude

ChatGPT

Cursor

Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp

Client	Connected by	Status	Last used
Claude	E Emily Carter	• Connected	4 minutes ago
Cursor	M Megan Brooks	• Connected	2 hours ago
ChatGPT	R Ryan Hayes	• Connected	Yesterday

AI apps

One Wati endpoint, any client, no api keys.

Claude, ChatGPT, Cursor and Microsoft Copilot all reach Wati through a single governed org endpoint.

ElaichiTools

Tool	Action	Description
List all Wati contacts	List	List Wati contacts with pagination. Returns: id, phone, name, bsuid, parentBsuid, username. Max 100 items per page.
Get single Wati contact by ID	Get	Get a single Wati contact by id. The id can be a ContactId, PhoneNumber, BSUID, or Channel:format identifier — the system auto-detects. Returns: id, phone, name, bsuid, parentBsuid, username. Required: id.
Create a Wati contact	Create	Create a new Wati contact with a WhatsApp number and name, optionally including custom parameters. Returns: id, phone, name, bsuid, parentBsuid, username. Required: whatsapp_number, name.
Delete a Wati contact by ID	Delete	Soft-delete a Wati contact by id, removing the contact and its linked records. The id can be a ContactId, PhoneNumber, or Channel:PhoneNumber. Returns: id, status. Required: id.
Wati contacts assign teams	Assign	Assign a Wati contact to one or more teams using a polymorphic target identifier (phone, Contact ID, or BSUID). Returns: id, name, phone, bsuid, parentBsuid, username, customParams. Required: target, teams.

Tool catalog

94 Wati tools, zero custom code.

Every Wati contact, broadcast and attribute method cataloged and ready to call.

ElaichiToolboxes

Name	Source template	Tools	Created
Marketing toolbox Wati · broadcasts and campaigns	Wati starter	18	Mar 4, 2026
Support toolbox Wati · contact attributes and replies	—	9	Mar 2, 2026
Sales toolbox Wati · contact assignment and follow up	—	24	Feb 27, 2026
Operations toolbox Wati · bulk contact updates	Wati starter	6	Feb 19, 2026
Customer success toolbox Wati · contact segmentation	—	31	Jan 30, 2026
Growth toolbox Wati · broadcast recipient lists	—	12	Jan 22, 2026

Toolboxes

Every team gets its own Wati toolbox.

Marketing, support and sales each work from a toolbox scoped to their Wati needs.

ElaichiConnections

Connection	Scope	Status	Access
WA Wati (Marketing EMEA) Connected by Emily Carter	Personal	• Active	1 team · 6 members
WA Wati (Support APAC) Connected by Jake Morgan	Organization	• Active	3 teams · 24 members
WA Wati (Sales US) Connected by Megan Brooks	Organization	• Active	2 teams · 11 members
WA Wati (Growth Team) Connected by Tyler Reed	Personal	• Needs re-auth	1 team · 3 members
WA Wati (Customer Success) Connected by Ryan Hayes	Personal	• Active	Not shared
WA Wati (Operations) Connected by Ashley Parker	Personal	• Active	2 teams · 9 members

Shared connections

Teammates use Wati without seeing credentials.

See who connected each Wati account and how many teams and members share it.

ElaichiAudit log

When	Who	What happened	Type
2 minutes ago Mar 6, 2026, 3:10 PM	E Emily Carter [email protected]	Restriction Created	Access
8 minutes ago Mar 6, 2026, 3:04 PM	J Jake Morgan [email protected]	Restriction Updated	Access
14 minutes ago Mar 6, 2026, 2:58 PM	M Megan Brooks [email protected]	Role Assigned	Access
20 minutes ago Mar 6, 2026, 2:52 PM	T Tyler Reed [email protected]	Wati Users Updated	MCP
26 minutes ago Mar 6, 2026, 2:46 PM	R Ryan Hayes [email protected]	Wati Contacts Created	MCP
32 minutes ago Mar 6, 2026, 2:40 PM	A Ashley Parker [email protected]	Wati Contacts List	Toolbox

Audit log

Every Wati action lands in one log.

See who did what in Wati, when, and on which contact or broadcast.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.

Wati digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

Run now

✓

Schedule

Every weekday at 8:00 AM

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 Jake Morgan

Approve Deny
Post the digest

Wati

Queued

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 health

Refreshed 4 minutes ago · every 15 minutes · from the contacts collection

Live

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%

Collections and dashboards

Wati health, computed, not asked for.

Four metrics and a 14 day contact chart refresh on schedule, broken down by team.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Wati

All three can connect Wati to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Wati, by what to check
What to check	Elaichi	Zapier MCP	Composio
Where the AI connects	One address for the whole organization. `https://api.elaichi.ai/mcp`	A server per member, created at sign-in.	An MCP endpoint per team, or an SDK.
Control over Wati tools	Allow or restrict single Wati tools, per role or user.	App and action restrictions on the account.	Role permissions, down to the action.
Record of calls	One audit entry per Wati call.	A History tab of tool calls.	A log of every tool call.
Single sign-on	SAML or OIDC, plus SCIM, on Gold.	SAML on Enterprise.	SAML and OIDC on Enterprise.
Price	Free for one person; $15 per user per month on Gold.	2 tasks per successful call.	Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

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.

More from the catalog

Browse all 650+ connectors →

Questions, answered

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, Microsoft Copilot, 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 restricting deleting contacts, editing attributes or starting chatbots. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.

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, Microsoft Copilot and every other client together.

Does the Wati MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Wati is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Wati?

Yes. Both let Claude, ChatGPT or Cursor use Wati. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Wati call.

How is Elaichi different from Composio for Wati?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Wati: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Wati in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

Connect Wati Talk to us

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp

ChatGPT
Claude
Cursor
Microsoft Copilot

Wati MCP connector

How to connect Wati to Claude, ChatGPT, Cursor or Microsoft Copilot

Wati MCP connector for Claude

Wati MCP connector for Claude Code

Wati MCP connector for ChatGPT

Wati MCP connector for Cursor

Wati MCP connector for Microsoft Copilot

Connect Wati to any MCP client

What teams do with Wati through Elaichi

Check how a broadcast performed

Estimate campaign cost before sending

Add a new lead after a call

Route customers to the right team

Start a chatbot flow for a customer

Clean up contact attributes in bulk

What connecting Wati gets you

Ask Wati questions, get live answers.

One Wati endpoint, any client, no api keys.

94 Wati tools, zero custom code.

Every team gets its own Wati toolbox.

Teammates use Wati without seeing credentials.

Every Wati action lands in one log.

From answering questions to doing the work

Wati broadcasts run themselves, with your approval.

Wati health, computed, not asked for.

Elaichi vs Zapier MCP vs Composio for Wati

Wati tools for your AI agents

More from the catalog

Questions, answered

Put Wati in front of your team