Tidio MCP Server
Tickets, chats, contacts, macros and flows in your Tidio, worked by your agent.
Hosted MCP Server
npx add-mcp 'https://cotlet.dev/mcp/v1/tidio'Installs into Claude Code, Codex, Cursor and more
Documentation
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Tidio API and MCP server: Let your AI agent work your Tidio inbox.
Tidio has an OpenAPI for tickets, contacts and operators and an Analytics MCP server, and both work only on Plus (from $300 a month plus usage) and Premium (checked 27 Oct 2026). Cotlet runs 14 Tidio tools hosted, over MCP for agents and REST for scripts, on any Tidio plan.
Tickets, chats, contacts, macros and flows in your Tidio, worked by your agent. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.
- Free 7-day trial, no card
- Unofficial, not affiliated with Tidio
- Page: https://cotlet.dev/integrations/tidio-api-mcp-server
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Tidio. Tidio is a trademark of its owner. If Tidio's own integrations cover what you need, use them first.
What can you automate in Tidio?
- Set priority, team and tags on new tickets
- Answer simple tickets after your OK
- Reply in a live chat as your operator
- Update contact properties from your CRM
- Turn repeat answers into macros
- Find Flows that start on the same trigger
Does Tidio have an MCP server or an API?
- On Free there is no API. On Starter and Growth the API reaches only Lyro product recommendations, 10 requests a minute.
- The official MCP server reads analytics only. A second one from Tidio installs the chat widget and does nothing in the inbox.
- The OpenAPI has no endpoint for macros or Flows, and it can post into a live chat only as the visitor, not as your operator.
| What you need | Tidio OpenAPI | Tidio Analytics MCP | Cotlet |
|---|---|---|---|
| Read and update tickets | Yes | Reports only | Yes |
| Reply to a ticket or add a note | Yes | No | Yes, replies after your OK |
| Reply in a live chat as an operator | Only as the visitor | No | Yes, after your OK |
| Macros and Flows | No | Flow statistics | List and add macros, read Flows |
| Tidio plan needed | Plus or Premium | Plus or Premium | Any; macros on Growth |
| Who runs it | Your developer | Tidio | Cotlet, hosted |
Checked 27 Oct 2026. Sources: Tidio developers: Enable Tidio OpenAPI, Tidio developers: Rate limiting by plan, Tidio developers: Analytics API MCP, Tidio MCP Connector on GitHub, Tidio pricing
How does Cotlet connect to Tidio?
- Sign in to Tidio. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never see your Tidio password, and no reply reaches a customer by email or in the chat widget until you approve it.
Connect Tidio to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Sign in to Tidio in a Cloud Browser. Create a Cotlet account, open Tidio in its Cloud Browser, sign in with your own operator login and press Enable for agents. An admin login also lets the agent add macros.
- Add the Cotlet address. Paste https://cotlet.dev/mcp/v1 into the MCP server or connector field of your agent.
- Approve the connection. Chat apps show a Cotlet sign-in page. Code editors, n8n and scripts send an API key from the console.
Every app you enable shares one address, https://cotlet.dev/mcp/v1, Tidio included. If you enable Tidio after the agent is already connected, refresh the connector and the 14 Tidio tools appear.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: tidio_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: tidio_write
How to use the Tidio REST API
Create your Cotlet API key
Create a Cotlet API key with access to Tidio and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect Tidio in Cotlet and enable it for agents. Account access: Your own Tidio operator login (an admin account to change Settings, Macros and Flows). You sign in once in your own browser and keep your own 2-step verification.
Make your first Tidio API request
REST:
curl https://cotlet.dev/api/v1/tidio/conversations \
-H "Authorization: Bearer $COTLET_API_KEY"
Read conversations and apply the operation limits
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "tidio",
"tool": "list_conversations",
"result": {
"conversations": [
{
"conversation_id": "cv_5a21",
"contact_id": "c4d9e1a2-77b0-4e0f-9a31-5b2c8e6f0d13",
"contact_name": "Mark Dole",
"assigned_operator": "Dana Reyes",
"last_message": "Does the blue one come in size L?",
"last_message_from": "contact",
"last_message_at": "2026-10-16T14:02:00Z"
}
],
"next_cursor": null
}
}
Returns the live chat conversations of your account with the contact, the assigned operator and the last message. Filter by contact email to find one customer.
Pages hold up to 50 conversations; pass next_cursor back as cursor for the next page. Reading does not mark anything as seen for the customer.
limit: 1 to 50. Default: 25.
cursor: Next page cursor from the previous call.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
Tidio workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Every message of one live chat conversation, with who wrote each. Use get_conversation in your configured support report. |
| Make | HTTP > Make a request | Email tickets from a folder, with status, priority, assignee and department. Use list_tickets in your configured support report. |
| Python or Node.js | REST API | One contact with every property and tag. Use get_contact in your configured support report. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads Tidio; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
Tidio API endpoints and MCP tools
Email tickets
Tickets come from the Unassigned, My open and Solved folders. A change of priority, status, department or tags reaches no customer; a public reply is emailed and waits for your OK.
- List tickets (
list_tickets, read): Email tickets from a folder, with status, priority, assignee and department. - Get ticket (
get_ticket, read): One ticket with all its messages, tags and internal notes. - Update ticket (
update_ticket, write): Change priority, status, assignee, department or tags of a ticket. - Reply to ticket (
reply_to_ticket, write, asks first): Send a public reply or an internal note on a ticket.
Live chat
Reading a chat marks nothing as seen for the visitor. A reply shows in the chat widget under your operator name and cannot be unsent.
- List conversations (
list_conversations, read): Live chat conversations in the Tidio Inbox, in the order the Inbox shows them. - Get conversation (
get_conversation, read): Every message of one live chat conversation, with who wrote each. - Reply in live chat (
reply_in_conversation, write, asks first): Send a message to a visitor in a live chat as an operator.
Contacts
Only properties that already exist in Settings > Fields can be written, and customer tags stay apart from ticket tags.
- List contacts (
list_contacts, read): Contacts with email, tags and contact properties. - Get contact (
get_contact, read): One contact with every property and tag. - Update contact (
update_contact, write): Set contact properties and add or remove tags on a contact.
Operators, macros and Flows
Macros need Growth or higher and an admin login to add. Flows are read only; no tool edits or publishes one.
- List operators (
list_operators, read): Operators of your account with their departments. - List macros (
list_macros, read): Macros (saved replies) with name, label and text. - Create macro (
create_macro, write): Add a macro (saved reply) to Settings > General > Macros. - List flows (
list_flows, read): Chatbot Flows from My Flows, with their trigger.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/tidio-api-mcp-server#tools
Who can see my Tidio session, and how do I revoke it?
- What we store. Your signed-in Tidio browser profile, AES-256-GCM encrypted, in Finland. No password.
- What your agent gets. The 14 Tidio tools. The session cookie never leaves the browser.
- What the session sees. What your operator role sees: chats, tickets, contacts and the pages they viewed.
- What no tool touches. Billing and plan, Lyro settings, Developer keys, Flow editing, deletes.
- If Tidio signs you out. You sign in again yourself in the same Cloud Browser.
- How to cut access. Disable for agents, reset the browser, or remove the operator in Tidio.
Chats can hold order numbers, addresses and what a visitor typed before they hit send, and the agent reads them as your operator would. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Approvals, undo and mistakes
- Reads the Unassigned folder. Every page of it, not only the first 50 tickets.
- Reads each thread. Priority comes from what the customer wrote, not the subject.
- Sorts at once. Priority, department and tags reach no customer, so no wait.
- Drafts, then waits. Each public reply shows in your Cotlet console before Tidio emails it.
| Action | Undo |
|---|---|
| Change priority, status, department, tags | Yes, call update_ticket with the old values |
| Set a contact property or tag | Yes, write the old value back |
| Add a macro | Delete it in Settings > General > Macros |
| Internal note on a ticket | Stays in the thread; only your team sees it |
| Public ticket reply or chat message | No, the customer already has it |
2 of 14 tools ask first: reply_to_ticket and reply_in_conversation. An internal note goes through reply_to_ticket too and waits unless you turn the wait off for it. Ticket, contact and macro changes reach no customer, so they run at once.
Right before a reply goes out, the agent reads the ticket again and sends nothing if a colleague answered in the meantime.
MCP call:
{
"name": "reply_to_ticket",
"arguments": {
"ticket_id": 10482,
"body": "Hi Mark, your order ships within 2 business days and you will get a tracking link by email. Reply here if it has not arrived by Friday.",
"visibility": "public"
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/tidio/tickets/10482/replies \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"body":"Hi Mark, your order ships within 2 business days and you will get a tracking link by email. Reply here if it has not arrived by Friday.","visibility":"public"}'
Response:
{
"ticket_id": 10482,
"visibility": "public",
"status": "sent",
"url": "https://www.tidio.com/panel/inbox/tickets/10482"
}
Scripts reach the same tools over REST at /api/v1/tidio, with the same key and price: say a cron job at 8 am that posts the count of urgent tickets to Slack. A ticket ID that does not exist returns an error, and failed calls cost nothing. Each tool row above lists its REST path.
How much does the Tidio MCP server cost?
About $60 a month for a Shopify store on Tidio Growth with 3 operators, 10,300 credits. Your Tidio plan stays as it is; Plus is not needed.
| Job | Calls | Credits |
|---|---|---|
| Triage the Unassigned folder, each workday | 18 × 22 | 3,960 |
| Reply to waiting tickets, each workday | 12 × 22 | 2,640 |
| Copy the plan field from your CRM, weekly | 28 × 4 | 1,120 |
| New macros from answered chats, weekly | 26 × 4 | 1,040 |
| Check Flows for clashing triggers, weekly | 1 × 4 | 40 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 10,300 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Works on Free, Starter, Growth and Plus
Tidio publishes no ticket counts per account, so the month is our example. For scale, Tidio Plus, the cheapest plan with the API, starts at $300 a month before usage. A reply the agent sends from your login is a reply from you, so Tidio counts that conversation as billable, the same as one you type. Dollars at the $29 pack rate.
Tidio MCP server on GitHub, Zapier or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| adrmrn/tidio-mcp | Python server on the OpenAPI with a Docker image: contacts, tickets, operators. 3 stars, last push 10 Jun 2026. | Needs Plus and your own Client ID and Secret; no live chat replies or macros. |
| ufarooqm/tidio-mcp-server | Node server for Claude Desktop that reads chats, tickets and operators. 0 stars. | Plus or Premium; last push 11 Jun 2025. |
| AnythingMCP | 10 OpenAPI tools, hosted in the EU or self-hosted, AGPL-3.0. | Plus or Premium; replies only on tickets. |
| Truto | Managed MCP on the OpenAPI, also Lyro data sources and Lyro ticket answers. | Same OpenAPI limits; price on a sales call. |
Zapier has one Tidio trigger, Contact Sent From Bot, and no actions, and n8n has no Tidio node. If you already pay for Plus and need tickets and contacts only, one of the OpenAPI servers above is the cheaper route. For live chat replies, macros, Flows, or a Tidio on Free, Starter or Growth, Cotlet works in the inbox you already use.
Who runs Cotlet
Cotlet belongs to Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Tidio tools go to contact@cotlet.dev.
Tidio API and MCP: questions
How do I get access?
Sign up free at https://cotlet.dev, open Tidio under Integrations in the console and sign in to Tidio in its Cloud Browser. Your trial starts when you sign up, and no card is asked for.
How do I connect Tidio to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Tidio once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Tidio account through Cotlet, in their phone apps too.
What can ChatGPT do in Tidio?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Tidio: triage new support tickets; reply to waiting support tickets; update contact properties in bulk. You ask in plain words, and anything that reaches other people waits for your OK first.
Do I need the Plus plan to use Cotlet with Tidio?
No. Cotlet works in your own Tidio account, not through the OpenAPI, which Tidio limits to the Plus and Premium plans. Macros need the Growth plan or higher, so create_macro and list_macros need it too. Changing Settings needs an admin account.
Is the official Tidio Analytics MCP enough?
For reports, yes: it reads analytics only and cannot send messages or change anything. Cotlet is for the work around it: replying to tickets, changing tickets and contacts and creating macros.
Does this replace Lyro?
No. Lyro answers visitors in the widget from your knowledge base. Cotlet gives your own agent the operator side: sorting tickets, drafting the replies Lyro hands over, keeping contacts and macros current.
Do agent replies use my billable conversations?
Yes. Tidio counts a conversation once a human operator replies, and a reply sent from your login is yours. Replies from Lyro and Flows do not count, and each conversation counts once however many messages it has.
Can it react the moment a ticket comes in?
Cotlet has no Tidio trigger, and Tidio webhooks need Plus. Run your agent on a schedule, for example every hour during opening hours.
Do I call it differently over MCP and REST?
The transport differs and nothing else: the same 14 tools, inputs, answers, API key and price. Agents call MCP; scripts and HTTP steps call REST.
Is Cotlet affiliated with Tidio?
No. Cotlet is independent and not affiliated with Tidio LLC.
Can I use the Tidio API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.