Tawk.to MCP connector
The Tawk.to connector brings your chat conversations, tickets, agents, properties and widgets into Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client, so your team can ask about live chats and manage Tawk.to inside their own access.
- Connects with an API key
- Free 14-day trial
- No credit card
Show me open Tawk.to tickets from this week.
Working in Tawk.to with Elaichi
-
List all Tawk.to properties
-
Get single Tawk.to property by ID
-
List all Tawk.to conversations
How to connect Tawk.to to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Tawk.to 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.
Tawk.to MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith 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.
Tawk.to 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.
Tawk.to 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.
Tawk.to 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 Tawk.to 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.
What teams do with Tawk.to through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Tawk.to is logged.
-
Support
Catch up on chats before a shift
Ask for the conversations that came in overnight across your Tawk.to properties and get a short rundown of who wrote in and what they needed, before the first chat of the day lands.
-
Support
Find the ticket a customer is asking about
A customer replies quoting a ticket number. Pull up that Tawk.to ticket, read the history, and answer them without leaving the tool you are already working in.
-
Sales
Spot buying questions hidden in support chats
Read through recent Tawk.to conversations for anyone asking about pricing, plans or a demo, and turn them into a follow-up list for the sales team.
-
Marketing
Change the chat widget on the website
Update a Tawk.to widget, add a card promoting a new offer, or remove one when a campaign ends, without asking a developer to touch the site.
-
Operations
Bring new chat agents on and off
Enable a new hire as a Tawk.to agent, set their permissions, and disable or remove agents who have moved on, all from a plain request.
-
Operations
Set up chat for a new website
Create a Tawk.to property for a new site or brand, add a widget to it, and check the global widget settings match the rest of your properties.
Try asking
- “Show me open Tawk.to tickets from this week.”
- “Which agents handled the most conversations yesterday?”
- “List conversations on our support property missing a reply.”
What connecting Tawk.to gets you
6 screens from Elaichi, each doing one job for your Tawk.to account.
Ask Elaichi to work across your apps.
Show me open Tawk.to tickets from this week.
Which agents handled the most conversations yesterday?
List conversations on our support property missing a reply.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Tawk.to tickets, read the answer.
Plain language questions return live Tawk.to conversations, tickets and agents.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Tawk.to.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
80 Tawk.to tools are ready to call.
Properties, conversations, tickets and agents are covered without any custom code.
Toolboxes
Every team gets its own Tawk.to toolbox.
Curate Tawk.to tools per team, so support and sales see different sets.
Shared connections
Teammates use Tawk.to without a credential.
Each connection shows who connected it and which teams and members share it.
Audit log
Every Tawk.to call is on the record.
When, who, what happened, type and resource, in an append only log.
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.
Tawk.to digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch tickets
Tawk.to
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
Tawk.to
Queued
Automations
A schedule fires, Tawk.to tickets get handled.
Fetch tickets, group them, draft a digest, approve it, post back to Tawk.to.
Tawk.to health
Refreshed 4 minutes ago · every 15 minutes · from the tickets collection
Tickets
1,284 ↓ 12%
Conversations
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Tickets created
Last 14 days
By team
Share of activity
Support EMEA 34%
Support US 27%
Sales 21%
Success 18%
Collections and dashboards
Tawk.to ticket numbers land before anyone asks.
Four metrics, 14 days of tickets created and a team breakdown, computed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Tawk.to
All three can connect Tawk.to to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| 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 Tawk.to tools | Allow or restrict single Tawk.to 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 Tawk.to 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.
Tawk.to tools for your AI agents
80 tools are ready to call through Elaichi's MCP endpoint the moment you connect Tawk.to, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Tawk.to to Claude?
Two steps. In Elaichi, add the Tawk.to connector and paste in a Tawk.to API key when asked, then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. There is no OAuth application to register with Tawk.to and no client ID or secret to generate. The whole thing takes a few minutes.
Does Tawk.to work with ChatGPT and Cursor as well as Claude?
Yes. Once Tawk.to is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Tawk.to once and every client picks it up.
What can an AI agent actually do with my Tawk.to data?
It can read your Tawk.to conversations and tickets, look up a specific chat or ticket, list your properties and the agents on your account, and manage widgets, including adding or removing cards and adjusting global widget settings. It can also enable, disable or remove agents and change their permissions. Because Tawk.to has a lot of tools, short concrete asks such as "show me yesterday's tickets" work better than long paragraphs.
Does connecting Tawk.to give the AI access to every property and every chat?
No. The AI only sees what the Tawk.to API key it is connected with can see, so the properties, conversations and agents available are the same ones that person could already reach in Tawk.to. Elaichi can narrow that access further with restrictions, but it can never widen it beyond what Tawk.to itself allows.
Can I stop an agent from deleting or changing things in Tawk.to?
Yes. Restrictions in Elaichi work per action, so you can allow reading Tawk.to conversations and tickets while restricting widget deletion, agent removal or permission changes. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
What happens to a Tawk.to connection when someone leaves?
Offboarding that person in Elaichi ends their access to Tawk.to through every client at once. If they connected a shared Tawk.to account, the connection keeps working for everyone else on the team. Disconnecting Tawk.to once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.
Does the Tawk.to MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Tawk.to 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 Tawk.to?
Yes. Both let Claude, ChatGPT or Cursor use Tawk.to. 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 Tawk.to call.
How is Elaichi different from Composio for Tawk.to?
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 Tawk.to: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Tawk.to in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
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