Helpdesk
Tawk.to MCP connector
The Tawk.to connector brings your chat conversations, tickets, agents, properties and widgets into Claude, ChatGPT, Cursor or any MCP client, so your team can ask about live chats and manage Tawk.to inside their own access.
-
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.
80 tools
How to connect
How to connect Tawk.to to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Tawk.to once
-
Open Connections, choose Add connection, and pick Tawk.to.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Tawk.to API key. One person generates a token in Tawk.to 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 Tawk.to 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 Tawk.to 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 Tawk.to 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 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.
Use cases
What teams do with Tawk.to through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
AI tools
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.
See it in Elaichi
What connecting Tawk.to gets you
6 screens from the product, each doing one job for your Tawk.to account.
The agent
Ask about Tawk.to tickets, read the answer.
Plain language questions return live Tawk.to conversations, tickets and agents.
- tickets
- conversations
- agents
- properties
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 or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Tawk.to.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
80 Tawk.to tools are ready to call.
Properties, conversations, tickets and agents are covered without any custom code.
- List all Tawk.to properties
- Get single Tawk.to property by ID
- Create a Tawk.to property
- List all Tawk.to conversations
ElaichiToolsToolboxes
Every team gets its own Tawk.to toolbox.
Curate Tawk.to tools per team, so support and sales see different sets.
- Support
- Sales
- Success
- Operations
ElaichiToolboxesShared connections
Teammates use Tawk.to without a credential.
Each connection shows who connected it and which teams and members share it.
- Support EMEA
- Support US
- Sales
- Success
ElaichiConnectionsAudit log
Every Tawk.to call is on the record.
When, who, what happened, type and resource, in an append only log.
- 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
A schedule fires, Tawk.to tickets get handled.
Fetch tickets, group them, draft a digest, approve it, post back to Tawk.to.
Tawk.to digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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 Michael Brennan
Approve Deny -
Post the digest
Tawk.to
Queued
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.
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 blocking widget deletion, agent removal or permission changes. A blocked action is never advertised to Claude, ChatGPT or any other client, so no prompt can reach it.
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 and every other client together.
Put Tawk.to in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.