Skip to content

Helpdesk

Tidio MCP connector

The Tidio connector brings your contacts, tickets, operators, departments, Lyro knowledge sources and product catalog to Claude, ChatGPT, Cursor and any MCP client, so support and sales teams can ask about customers, reply to tickets and keep records current from a chat window.

  • 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 Tidio to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Tidio once

  1. Open Connections, choose Add connection, and pick Tidio.

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

  3. Paste a Tidio API key. One person generates a token in Tidio 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.

tidio
Tidio
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.

Connect Tidio to 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.

Connect Tidio to 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.

Connect Tidio to 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 Tidio 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 Tidio through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Support

    Reply to a ticket without opening Tidio

    Ask what a customer has written in a Tidio ticket, draft the reply in the tone your desk uses, and send it back on the same thread.

  • Support

    Clear the queue by priority

    List the open Tidio tickets, sort them by who is waiting longest or which department they belong to, and update status or assignment as you work through them.

  • Sales

    Catch the contact up after a call

    Add the notes, phone number and deal details to the Tidio contact right after a conversation, or create the contact if the visitor was new.

  • Marketing

    Import a list of new contacts in one go

    Paste a list of leads from an event or a signup form and have them created in Tidio as contacts, with the right properties filled in for each.

  • Ecommerce

    Keep the product catalog in sync

    Push updated product names, prices and availability into Tidio so Lyro and your operators answer with current information, and remove products you no longer sell.

  • Customer success

    Teach Lyro from your help pages

    Point Lyro at a new help center page or a policy document so it can answer common questions on its own, and check which knowledge sources it is already using.

Try asking

  • “Summarize open Tidio tickets by department this week.”
  • “Which Tidio operators closed the most tickets yesterday?”
  • “Create Tidio contacts for these five trial signups.”

See all 30 Tidio tools below

AI tools

Tidio tools for your AI agents

30 tools are ready to call through Elaichi's MCP endpoint the moment you connect Tidio, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Tidio gets you

6 screens from the product, each doing one job for your Tidio account.

The agent

Ask about Tidio tickets, get answers.

Plain questions run against live Tidio tickets, contacts and operators.

  • tickets
  • contacts
  • operators
  • departments

Ask Elaichi to work across your apps.

Summarize open Tidio tickets by department this week.

Which Tidio operators closed the most tickets yesterday?

Create Tidio contacts for these five trial signups.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Tidio.

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

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

30 Tidio tools ready to call.

Contacts, contact properties, tickets, operators and departments, with no custom code.

  • List all Tidio contacts
  • Create a Tidio contact
  • Get single Tidio contact by ID
  • Update a Tidio contact by ID
ElaichiTools
Tool Action Description
List all Tidio contacts List List Tidio contacts with all their properties. Returns: id, distinct_id, first_name, last_name, email, phone, language, country, city, created_at, email_consent, properties. Supports filtering by email address.
Create a Tidio contact Create Create a new Tidio contact. Returns: id. Required: distinct_id. At least one of email, first_name, last_name, or phone must also be provided.
Get single Tidio contact by ID Get Get a single Tidio contact by id. Returns: id, distinct_id, first_name, last_name, email, phone, language, country, city, created_at, email_consent, properties. Required: id.
Update a Tidio contact by ID Update Update a Tidio contact's properties such as email, phone, name, newsletter consent, and custom properties. Returns an empty 204 response on success. Required: id.
Delete a Tidio contact by ID Delete Delete a Tidio contact by id. Once deleted, the contact cannot be recovered. Returns an empty 204 response on success. Required: id.

Toolboxes

Every team gets its own Tidio toolbox.

Support, sales and ops each see the Tidio tools their work needs.

  • Support
  • Sales
  • Customer success
  • Operations
ElaichiToolboxes
Name Source template Tools Created

Support toolbox

Tidio · tickets and replies

Tidio starter 18 Mar 4, 2026

Sales toolbox

Tidio · contacts and leads

9 Mar 2, 2026

Customer success toolbox

Tidio · contact properties

24 Feb 27, 2026

Operations toolbox

Tidio · departments and operators

Tidio starter 6 Feb 19, 2026

Marketing toolbox

Tidio · contact lists and bulk imports

31 Jan 30, 2026

Quality toolbox

Tidio · ticket reviews and audits

12 Jan 22, 2026

Shared connections

Teammates use Tidio without a credential.

See who connected each Tidio account and which teams and members share it.

  • Support EMEA
  • Support US
  • Sales
  • Customer success
ElaichiConnections
Connection Scope Status Access
TI

Tidio (Support EMEA)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
TI

Tidio (Support US)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
TI

Tidio (Sales)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
TI

Tidio (Customer success)

Connected by Daniel Ortega

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

Tidio (Marketing)

Connected by Clara Nowak

Personal • Active Not shared
TI

Tidio (Operations)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every Tidio 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

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Tidio Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Tidio Tickets Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Tidio 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 drafts your Tidio ticket digest.

Fetch tickets, group them, draft a digest, get approval, post back to Tidio.

Tidio digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch tickets

    Tidio

    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

    Tidio

    Queued

Collections and dashboards

Tidio ticket numbers, computed on a schedule.

Four metrics, 14 days of contacts created, and a breakdown by team.

Tidio health

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

Live

Tickets

1,284 ↓ 12%

Contacts

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%

Customer success 18%

FAQ

Frequently asked questions

How do I connect Tidio to Claude?

Connect Tidio in Elaichi first, which means pasting the API key from your Tidio settings; 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 Tidio is ready to use.

Does Tidio work with ChatGPT and Cursor as well as Claude?

Yes. Once Tidio 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 Tidio once and every client you use picks it up.

What can an AI agent actually do with my Tidio data?

It can look up a Tidio contact, create or update contacts one at a time or in bulk, and list your operators and departments. It can find and read tickets, reply to them, change their status or assignment, and ask Lyro to answer one. It can also add or update the websites and documents Lyro learns from, and keep your product catalog in Tidio current.

Does connecting Tidio give the AI access to everything in my Tidio account?

No. Every call to Tidio runs under the access of the person who signed in, so the AI sees the contacts, tickets and settings that person can already see in Tidio. Elaichi can narrow that further, for example to reading tickets but not deleting them, but it can never widen it beyond what Tidio itself allows that person.

Can my team share one Tidio connection?

Yes. One person connects Tidio in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in as themselves, so the audit log names the actual person behind every ticket reply or contact update in Tidio.

Can I stop an agent from deleting or changing things in Tidio?

Yes. Restrictions in Elaichi are set per action, so you can allow reading and replying to Tidio tickets while blocking deletion of tickets, contacts or products. A blocked action is never shown to Claude, ChatGPT, Cursor or any other client, so no prompt, however worded, can reach it.

What happens to a Tidio connection when someone leaves?

Offboarding that person in Elaichi ends their access to Tidio through every client at once. If they connected a Tidio account that was shared with a team, the shared connection keeps working for everyone else. Disconnecting Tidio in Elaichi removes it from Claude, ChatGPT, Cursor and every other client in one step.

Put Tidio in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.