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.
In Elaichi
Connect Tidio once
-
Open Connections, choose Add connection, and pick Tidio.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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.
Tidio 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.
Tidio 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 today. The plugin directory lives at chatgpt.com/plugins.
Tidio 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.
Connect Tidio 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 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.”
Compare
Elaichi vs Zapier MCP vs Composio for Tidio
All three can connect Tidio 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 Tidio tools | Allow or restrict single Tidio 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 Tidio 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
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.
No tools match your search.
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.
Copy the endpoint
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
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
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
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
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 Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch tickets
Tidio
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
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
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%
Related connectors
More from the catalog
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 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.
Does the Tidio MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Tidio 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 Tidio?
Yes. Both let Claude, ChatGPT or Cursor use Tidio. 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 Tidio call.
How is Elaichi different from Composio for Tidio?
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 Tidio: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Tidio in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
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.