Skip to content

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.

How to connect

How to connect Tawk.to to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Tawk.to once

  1. Open Connections, choose Add connection, and pick Tawk.to.

  2. Optionally set Share with to give a team access, then press Connect.

  3. 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.

tawk.to
Tawk.to
Acquire
Ada
Atomicwork
CM Mobile Service Cloud
Crisp
2

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.

Tawk.to MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Tawk.to MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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.”

See all 80 Tawk.to tools below

Compare

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.

Elaichi compared with Zapier MCP and Composio for Tawk.to, 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 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 $15 per user per month. 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.

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.

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 clients
Claude ChatGPT Cursor

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

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
ElaichiTools
Tool Action Description
List all Tawk.to properties List List properties for the authenticated agent. Supports pagination via body.
Get single Tawk.to property by ID Get Retrieve property details. Required: propertyId.
Create a Tawk.to property Create Create a new property of type site for an agent. Required: name.
List all Tawk.to conversations List List chats for a property. Required: propertyId. Optional filters/pagination via body.
Get single Tawk.to conversation by ID Get Get a single chat by ID. Required: propertyId, chatId.

Toolboxes

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
ElaichiToolboxes
Name Source template Tools Created

Support toolbox

Tawk.to · tickets and conversations

Tawk.to starter 18 Mar 4, 2026

Sales toolbox

Tawk.to · chat leads and follow ups

— 9 Mar 2, 2026

Success toolbox

Tawk.to · account conversations and escalations

— 24 Feb 27, 2026

Operations toolbox

Tawk.to · agents and permissions

Tawk.to starter 6 Feb 19, 2026

Marketing toolbox

Tawk.to · properties and chat widgets

— 31 Jan 30, 2026

Quality toolbox

Tawk.to · conversation reviews and reporting

— 12 Jan 22, 2026

Shared 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
ElaichiConnections
Connection Scope Status Access
TA

Tawk.to (Support EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
TA

Tawk.to (Support US)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
TA

Tawk.to (Sales)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
TA

Tawk.to (Success)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
TA

Tawk.to (Website Chat)

Connected by Ryan Hayes

Personal • Active Not shared
TA

Tawk.to (Operations)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit 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 log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Tawk.to Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Tawk.to Tickets Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Tawk.to Tickets List Toolbox

Launching 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 Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch tickets

    Tawk.to

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. 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

Live

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%

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 my team share one Tawk.to connection?

Yes. One person connects Tawk.to in Elaichi and shares the connection with a team, and nobody else ever handles the Tawk.to API key. Each teammate still signs in to Elaichi as themselves, so every chat they read or widget they change is logged under their own name.

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.

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, 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 on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.