100+ integrations are ready to connect to your AI.Connect your first MCP

Tidio MCP server for your AI

Find and assign tickets, reply to customers, read a contact's chats, teach Lyro what it should know, and report on your team's week, all by asking.

PopMCPTidio

Which tickets are open and urgent, and what does each customer need?

Supported Tidio tools

Every endpoint in Tidio's API is here, on both its live records and its analytics tables: contacts, tickets, operators, departments, Lyro knowledge and product recommendations, plus daily statistics for your project, agents, Flows and Lyro. The everyday tools load by default and the rest are one search away. A few do a whole job at once, such as assigning a ticket to a person by name or filtering tickets, which Tidio's own list cannot do.

56 tools in the full catalog: 37 read and 19 write. 38 load by default, and the rest are found with tool search.

tidio_query_agent_details

Analytics: every human agent, with name, email, role, and whether active or deleted.

tidio_query_agent_statistics_daily

Analytics: each agent's day, with conversations replied to, first response time, conversation length and satisfaction.

tidio_query_agent_thread_details

Analytics: one row per human agent conversation thread, with times, first response, intent, and whether it was missed.

tidio_query_live_chat_rating_details

Analytics: customer satisfaction ratings on live chats, for human agents and Lyro.

tidio_query_lyro_thread_details

Analytics: one row per conversation Lyro handled, with how it ended and whether it went to a human.

tidio_query_project_statistics_daily

Analytics: the whole project per day: tickets, agent threads, Lyro, Flows, sales and new leads.

tidio_query_ticket_details

Analytics: one row per ticket with status, priority, source, tags, and when created and solved.

tidio_query_ticket_rating_details

Analytics: customer satisfaction ratings on tickets.

tidio_support_report

A support report for a date range: totals, each day, and each agent by name, covering tickets, live chat, Lyro and Flows.

tidio_assign_ticket

Assign a ticket by name: assignee is an operator's name or email, or a department's name, or an id.

tidio_contact_overview

Everything about one person in one call: the contact, their live chat messages and the pages they viewed in the past 30 days.

tidio_create_contact

Add one contact.

tidio_create_ticket

Open a new ticket in a contact's name, from their email address, with a subject and a first message.

tidio_delete_contact

Delete a contact for good.

tidio_delete_ticket

Delete a ticket.

tidio_find_tickets

Find tickets by status, priority, assignee, contact or words in the subject.

tidio_get_contact

Get one contact and its properties.

tidio_get_ticket

Get one ticket with all its messages, public and internal.

tidio_list_contact_properties

List the contact properties this project has, with name, label and type.

tidio_list_contact_viewed_pages

List the pages a contact viewed on your website in the past 30 days, with times.

tidio_list_contacts

List contacts with their properties, or find them by exact email.

tidio_list_ticket_custom_fields

List this project's ticket custom fields with id, name, type, whether required, and allowed values.

tidio_list_ticket_tags

List this project's ticket tags with id and name, in alphabetical order.

tidio_list_tickets

List tickets with subject, status, priority, contact and who is assigned, without messages.

tidio_reply_to_ticket

Add a message to a ticket.

tidio_ticket_overview

One ticket in one call: its messages, its contact, and the names of the operator and department it is assigned to.

tidio_update_contact

Change a contact.

tidio_update_ticket

Change a ticket's status (open, pending, solved), priority (low, normal, urgent), assignee, tags or custom fields.

tidio_upsert_contact

Save a contact without making a duplicate: updates the contact with this email if there is one, otherwise adds them.

tidio_add_lyro_website

Have Tidio read a website and add it to what Lyro knows.

tidio_create_lyro_qa

Teach Lyro one question and answer.

tidio_list_lyro_data_sources

List what Lyro knows: question and answer items (kind qa) and folders such as websites and files (kind folder).

tidio_update_lyro_qa

Replace the title and content of a question and answer Lyro uses.

tidio_list_contact_messages

Read a contact's live chat conversation: messages from the contact, operators and bots, plus a link to the conversation in Tidio.

tidio_project_overview

Start here: this Tidio project's id and status, its operators, departments, ticket tags, ticket custom fields and contact properties, with the ids other tools need.

tidio_upsert_lyro_products

Send up to 100 products for Lyro to recommend, one entry per variant.

tidio_list_departments

List departments with id and name.

tidio_list_operators

List the people on this project with id, name, email, role, and when last seen.

tidio_get_analytics_identity

Check the keys work with the Analytics API and see which project they belong to.

tidio_get_analytics_status

Check whether Tidio's Analytics API is up.

tidio_query_agent_thread_intent_statistics_daily

Analytics: human agent threads per day, counted by the reason people got in touch.

tidio_query_flow_statistics_daily

Analytics: each Flow's day, with triggers, interactions, actions and helpfulness votes.

tidio_query_live_chat_message_details

Analytics: one row per live chat message from anyone, for reading or counting chat history.

tidio_query_lyro_data_source_details

Analytics: what Lyro knows, question by question, with when it was added and changed.

tidio_query_lyro_message_intent_statistics_daily

Analytics: Lyro messages per day, counted by the reason people got in touch.

tidio_query_lyro_suggestion_details

Analytics: the suggestions Lyro makes for its knowledge: questions people ask and how often.

tidio_query_smart_action_statistics_daily

Analytics: each Smart Action's day, with how often it ran and its results.

tidio_query_ticket_message_details

Analytics: one row per ticket message.

tidio_query_visitor_details

Analytics: one row per visitor to your website.

tidio_create_contacts

Add up to 100 contacts in one call.

tidio_update_contacts

Update up to 100 contacts in one call, each with its id.

tidio_ask_lyro_to_answer_ticket

Ask Lyro, Tidio's AI agent, to answer the first message of a ticket from the details you send, and get the text back.

tidio_upsert_lyro_web_page

Give Lyro a web page's content as HTML you provide, under a URL that identifies it.

tidio_delete_lyro_product

Remove one product from Lyro's recommendations for good.

tidio_get_project

Get this Tidio project's id and whether it is online.

tidio_send_message_as_contact

Add a message as if the contact wrote it, 1 to 5000 characters.

Connect Tidio to Claude, ChatGPT and Claude Code

Credentials off one Tidio screen, then an endpoint your client signs into. Nothing to deploy, and nothing to install.

In your Tidio panel, open Settings, then Developer, then OpenAPI, and select Generate OpenAPI key. Copy the Client ID and the Client Secret, because Tidio only shows the secret once. Open Tidio in PopMCP, paste both and connect. PopMCP finds your project from them, so there is nothing else to fill in.

Client IDci_...
Client Secret••••••••••••3f7a
ConnectionVerified

Then just ask for the work

  • “Which tickets are open and urgent, and what does each customer need?”

    • list_tickets
    • get_ticket
  • “Reply to this ticket and mark it as solved”

    • get_ticket
    • list_operators
    • reply_to_ticket
    • update_ticket
  • “Find this customer by email and show me their chats and the pages they viewed”

    • list_contacts
    • list_contact_messages
    • list_contact_viewed_pages
  • “Add our new returns policy to what Lyro knows”

    • list_lyro_data_sources
    • create_lyro_qa
  • “How did my team and Lyro do last month, and which chats did we miss?”

    • query_project_statistics_daily
    • query_agent_statistics_daily
    • query_agent_thread_details

Use Tidio from the assistant you already open

One hosted endpoint, registered once per client. The same tools and the same permissions, whichever window the request comes from.

Claude DesktopCustom connector

Add the PopMCP URL under Customize → Connectors and the tools appear in every chat.

Claude WebCustom connector

The same endpoint, registered in the browser. Nothing to install on the machine you are working from.

ChatGPTCustom connector

Register PopMCP as a custom connector, then let ChatGPT read and update the account.

CodexDesktop & CLI

Wire the endpoint into Codex or the Codex CLI when a task needs live business context, not a fixture.

OpenCodeCoding agent

Register the remote MCP server in OpenCode's config for terminal-first and scripted agent runs.

ZCodeDesktop app

Add PopMCP as an MCP server in Z.ai's desktop app and work the account from the same window.

Tidio MCP server questions

What teams ask before putting Tidio behind an AI client.

Do I need a developer app?

No. An owner or admin of the project generates a key pair under Settings, Developer, OpenAPI in the Tidio panel, and pastes the Client ID and Client Secret into PopMCP.

Which Tidio plan do I need?

Tidio's documentation says its API is on the Plus and Premium plans. With a paid Lyro plan alone, only product uploads for Lyro work, and PopMCP tells you so when you connect.

Can the AI answer live chats?

It can read them, but Tidio's API has no way to send an operator's live chat reply. It can reply to tickets, publicly or as an internal note, and it can mark, assign and tag them.

Why are today's numbers missing from reports?

Tidio loads its analytics once a day, and yesterday's arrive at about 10:00 UTC. Contacts, tickets and chat messages are live, so the AI uses those for what is happening now.

Can the AI change or delete things?

Only if you allow it. New connections start read-only. Once writes are on, replies, updates and deletions are real, so ask it to confirm first.

Does this set up Tidio webhooks?

No. Tidio's webhooks are set up by hand in its panel, under Settings, Developer, Webhooks, and it has no API to manage them.

Do I have to run or host the Tidio MCP server myself?

No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.

Which AI clients can use this MCP server?

Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, Claude Code, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.

How do I connect Tidio to Claude Code?

Connect Tidio in PopMCP first, then run claude mcp add --transport http popmcp https://app.popmcp.com/mcp in a terminal. Inside Claude Code, run /mcp and sign in to PopMCP in the browser window it opens, ticking Tidio on the consent screen. The Tidio tools are then available in that session, and no Tidio credential is stored on your machine.

Why do only 38 of the 56 tools load by default?

Loading 56 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 38-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. Every tool stays searchable, and on Scale the owner can load the full catalog for a teammate's connection.

What is the difference between a tool and a trigger?

A tool is something your AI calls, and there are 56 here. A trigger is something PopMCP watches for you: 9 Tidio events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Tidio.

Connect Tidio to your AI in minutes

Launch a hosted MCP endpoint for Tidio, keep tool access under control, and start testing real workflow prompts right away.

Connect your first MCP