--- title: "Tidio MCP server for AI agents - actionlake" description: "Give Claude 47 Tidio actions through one MCP server: analytics, contacts, lyro, tickets. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/tidio updated: 2026-10-23 --- Connectors · Service desk & support # Tidio MCP server for AI agents. actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Tidio and the rest of your systems. It gives your agent 47 Tidio actions (30 reads, 14 writes and 3 that wait for a confirmation) and holds the Tidio credential itself, so the agent never does. It paces Tidio's limits and records every call. [Connect Tidio free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you. `claude mcp add --transport http actionlake https://connect.actionlake.com/mcp` the first call ``` do { action: "tidio.contacts.list", intent: "check which Tidio account is connected" } # Get contacts · read · 1 upstream call ``` - 47 actions in one signed file - 30 read look, never change - 14 write create and update - 3 wait for a yes destructive, confirmed first Set up ## Connect Tidio in three steps. 1. 01 ### Add actionlake to Claude. Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us. `https://connect.actionlake.com/mcp` 2. 02 ### Connect Tidio. Header credentials. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key. - `client_id` OpenAPI Client ID (starts with ci_ - `client_secret` OpenAPI Client Secret (starts with cs_) ``` account { op: "connections.requirements", service: "tidio" } # free: exactly what to paste, and what is found for you ``` 3. 03 ### Make the first call. Check before a write. Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free. ``` do { action: "tidio.contacts.list" } # get contacts · read · 1 upstream call check { action: "tidio.contacts.create", input: { … } } # free: inputs, permissions, cost and confirmations, nothing sent ``` Tidio at a glance **Sign-in** Header credentials. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. **You provide** `client_id` `client_secret` **Limits we pace to** 120 calls a minute, per connection **API covered** Tidio OpenAPI version 1 (api.tidio.com) + Tidio Analytics API (taa.data.tidio.com)`api.tidio.com` **Built from** Tidio's documentation, read 23 October 2026[developers.tidio.com](https://developers.tidio.com/llms.txt) **Service file** Version 1.0.0, signed (Ed25519) **Cached reads** 30 of 30 reads, for up to an hour; a write clears what it affects **Shared entities** 2, so ask can line Tidio up with your other systems **Data** Processed and stored in Sydney, Australia. No US region yet Capabilities ## What an AI agent can do in Tidio. 47 actions in 11 areas. Every one carries its effect, so a key can allow the reads and hold the rest. - **30** read look, never change - **14** write create and update - **3** destructive wait for a confirmation 1. ### Analytics 17 17 read · 0 write · 0 destructive Get agent_details · Get agent_statistics_daily · Get agent_thread_details · Get agent_thread_intent_statistics_daily 2. ### Contacts 10 4 read · 5 write · 1 destructive Get contacts · Create contact · Get single contact · Update contact properties 3. ### Lyro 6 1 read · 5 write · 0 destructive Get Lyro data sources · Create Lyro QA data source · Add website as Lyro data source (scraping) · Ask Lyro to answer ticket 4. ### Tickets 6 2 read · 3 write · 1 destructive Get tickets · Get ticket details · Update ticket · Delete ticket 5. ### Products 2 0 read · 1 write · 1 destructive Delete product · Upsert products 6. ### Contact properties 1 1 read · 0 write · 0 destructive Get contact properties 7. ### Departments 1 1 read · 0 write · 0 destructive Get departments 8. ### Operators 1 1 read · 0 write · 0 destructive Get operators **3 more areas · 3 actions** - Project **1** - Ticket custom fields **1** - Ticket tags **1** Top actions ## The Tidio API, shaped for agents. The ids your agent types, what each does, and the one name it shares with other systems. 9 of Tidio's 9 action names are shared with at least one other connector, so an agent learns them once. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `tidio.contacts.list` Get contacts | Contacts are site visitors who have interacted with the Tidio widget and have been identified by their name, email address, or phone number. Each contact can… | read | `crm.contact.list` 177 connectors | | `tidio.contacts.create` Create contact | Contacts are site visitors who have interacted with the Tidio widget and have been identified by their name, email address, or phone number. Each contact can… | write | `crm.contact.create` 161 connectors | | `tidio.tickets.list` Get tickets | Ticket is a record of more complex conversations between operators and customers, which often require additional interactions or cannot be closed in a single… | read | `service.ticket.list` 56 connectors | | `tidio.contacts.delete` Delete contact | This API endpoint allows you to delete a specific contact identified by ID. Please be aware that once the contact is deleted, there's no way to recover it, so… | destructive | `crm.contact.delete` 147 connectors | | `tidio.tickets.get` Get ticket details | Ticket is a record of more complex conversations between operators and customers, which often require additional interactions or cannot be closed in a single… | read | `service.ticket.get` 56 connectors | | `tidio.tickets.reply` Reply to a ticket | This endpoint allows you to add a reply message to an existing ticket, based on its unique ID. This can be either a message from an operator or from a contact… | write | this connector | | `tidio.operators.list` Get operators | Operators are chat agents or customer service representatives who interact with customers or website visitors in real-time. They use a chat interface to… | read | this connector | | `tidio.departments.list` Get departments | Departments are teams or groups of operators that handle specific types of customer inquiries or problems. You can use this endpoint to retrieve a complete… | read | this connector | | `tidio.ticket_tags.list` Get ticket tags | Returns the project's tickets tags as a flat list of `{id, name}` objects, sorted alphabetically by `name`. | read | this connector | | `tidio.contacts.batch_create` Create multiple contacts | The same as `[POST] /contacts`, but for multiple contacts. Contacts are saved with `all or nothing` strategy, so all contacts must be valid. The maximum… | write | this connector | | `tidio.contact_properties.list` Get contact properties | The contacts have their properties. In Tidio there are some default properties like `name`, `email`, `phone` etc. and any other properties [that can be… | read | this connector | | `tidio.tickets.create_as_contact` Create ticket (as Contact) | This API endpoint creates a ticket as Contact based on the data provided. | write | this connector | Try it ## Prompts to paste into Claude. Each one names the Tidio actions it will call, so you know what it reads and what it changes before you send it. 1. Read read Which Tidio tickets have been open the longest? Show me the ten oldest with their status. calls `tidio.tickets.list` 2. Write write Create contact in Tidio. Show me exactly what you will send before you save it. calls `tidio.contacts.create` 3. Across systems read Which contacts are in both Tidio and HaloPSA, and how many are in only one of them? calls `tidio.contacts.list` `halopsa.users.list` Across your systems ## Tidio, joined to the rest of your business. One `ask` fetches from Tidio and another system, joins the rows on the same customer on our side, and hands your agent the answer, not every row. - Which contacts are in both Tidio and HaloPSA, and how many are in only one of them? `tidio.contacts.list` + `halopsa.users.list`, on `crm.contact` · [HaloPSA](https://actionlake.com/connectors/halopsa) - Which contacts are in both Tidio and NetSuite, and how many are in only one of them? `tidio.contacts.list` + `netsuite.views.contacts`, on `crm.contact` · [NetSuite](https://actionlake.com/connectors/netsuite) Also mapped by other connectors `crm.contact` **192** `service.ticket` **62** ask ``` ask { intent: "which contacts are in both Tidio and HaloPSA, and how many are in only one of them", steps: [ { action: "tidio.contacts.list", as: "people", input: {}, limit: 100, max_pages: 5 }, { action: "halopsa.users.list", as: "people2", input: {}, limit: 100, max_pages: 5 }, { join: { left: "people", right: "people2", on: "crm.contact", group_by: "people.email", select: ["people.email", "count(people2.id) as in_halopsa"] } } ] } ``` Example. Run it through check first: it validates the steps and prices them, and it is free. Governance for Tidio ## Destructive actions wait for a yes. 3 Tidio actions are destructive. These are all of them: - Delete contact `tidio.contacts.delete` - Delete ticket `tidio.tickets.delete` - Delete product `tidio.products.delete` A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after. do tidio.contacts.delete confirm_policy: **human** Delete contact? **intent:** the user asked me to delete contact run suspended · waiting for a named person · key _tidio-agent_ cannot confirm itself In the console, or from an emailed signed link. a key for this connector ``` account { op: "keys.create", name: "tidio-agent", allowed_actions: ["tidio.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "tidio.contacts.delete", approver: "lead@example.com" }, { match: "tidio.tickets.delete", approver: "lead@example.com" }, { match: "tidio.products.delete", approver: "lead@example.com" } ] } ``` Illustrative. Scoped to Tidio only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person. Cost ## What Tidio costs on actionlake. Every Tidio action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Tidio refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. - 1 upstream call per action all 47 Tidio actions - 47 actions page each page of a long list is one call - 30 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every Tidio action. 47 actions by area: the id your agent calls, what it does, and its effect. **Analytics 17** - `tidio.analytics.agent_details.list` Get agent_details read - `tidio.analytics.agent_statistics_daily.list` Get agent_statistics_daily read - `tidio.analytics.agent_thread_details.list` Get agent_thread_details read - `tidio.analytics.agent_thread_intent_statistics_daily.list` Get agent_thread_intent_statistics_daily read - `tidio.analytics.flow_statistics_daily.list` Get flow_statistics_daily read - `tidio.analytics.live_chat_message_details.list` Get live_chat_message_details read - `tidio.analytics.live_chat_rating_details.list` Get live_chat_rating_details read - `tidio.analytics.lyro_data_source_details.list` Get lyro_data_source_details read - `tidio.analytics.lyro_message_intent_statistics_daily.list` Get lyro_message_intent_statistics_daily read - `tidio.analytics.lyro_suggestion_details.list` Get lyro_suggestion_details read - `tidio.analytics.lyro_thread_details.list` Get lyro_thread_details read - `tidio.analytics.project_statistics_daily.list` Get project_statistics_daily read - `tidio.analytics.smart_action_statistics_daily.list` Get smart_action_statistics_daily read - `tidio.analytics.ticket_details.list` Get ticket_details read - `tidio.analytics.ticket_message_details.list` Get ticket_message_details read - `tidio.analytics.ticket_rating_details.list` Get ticket_rating_details read - `tidio.analytics.visitor_details.list` Get visitor_details read **Contacts 10** - `tidio.contacts.batch_create` Create multiple contacts write - `tidio.contacts.batch_update` Update multiple contacts write - `tidio.contacts.create` Create contact write - `tidio.contacts.delete` Delete contact destructive - `tidio.contacts.get` Get single contact read - `tidio.contacts.list` Get contacts read - `tidio.contacts.messages.create` Send a message on behalf of the contact write - `tidio.contacts.messages.list` Get contact messages read - `tidio.contacts.update` Update contact properties write - `tidio.contacts.viewed_pages.list` Get viewed pages history read **Lyro 6** - `tidio.lyro.data_sources.list` Get Lyro data sources read - `tidio.lyro.data_sources.qa_create` Create Lyro QA data source write - `tidio.lyro.data_sources.qa_update` Update Lyro QA data source write - `tidio.lyro.data_sources.website_scrape` Add website as Lyro data source (scraping) write - `tidio.lyro.data_sources.website_upsert` Upsert Lyro data source write - `tidio.lyro.tickets.answer` Ask Lyro to answer ticket write **Tickets 6** - `tidio.tickets.create_as_contact` Create ticket (as Contact) write - `tidio.tickets.delete` Delete ticket destructive - `tidio.tickets.get` Get ticket details read - `tidio.tickets.list` Get tickets read - `tidio.tickets.reply` Reply to a ticket write - `tidio.tickets.update` Update ticket write **Products 2** - `tidio.products.batch_upsert` Upsert products write - `tidio.products.delete` Delete product destructive **Contact properties 1** - `tidio.contact_properties.list` Get contact properties read **Departments 1** - `tidio.departments.list` Get departments read **Operators 1** - `tidio.operators.list` Get operators read **Project 1** - `tidio.project.get` Get project info read **Ticket custom fields 1** - `tidio.ticket_custom_fields.list` Get ticket custom fields read **Ticket tags 1** - `tidio.ticket_tags.list` Get ticket tags read Questions ## The Tidio MCP server, answered. **Is there a Tidio MCP server for Claude?** Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 47 Tidio actions across analytics, contacts, lyro and tickets, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Tidio. **What do I need to connect Tidio?** OpenAPI Client ID (starts with ci_ and OpenAPI Client Secret (starts with cs_). The free call account { op: "connections.requirements", service: "tidio" } lists exactly what to paste. **Can an AI agent delete or change things in Tidio?** Only if its key allows it, and only with an explicit confirmation. 3 Tidio actions are destructive, including delete contact, delete ticket and delete product. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it. **Will an AI agent use up my Tidio API limit?** actionlake paces every call to the limits in the Tidio service file: 120 calls a minute per connection. Repeated reads are answered from cache (30 Tidio actions can be), which never reaches Tidio. **What does a Tidio action cost?** One upstream call, the only unit actionlake bills. A list that pages bills one call per page (47 Tidio actions page). Cache hits, searches, dry runs and calls Tidio refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. **Which Tidio API does it cover?** The Tidio OpenAPI version 1 (api.tidio.com) + Tidio Analytics API (taa.data.tidio.com) at api.tidio.com. It is built from Tidio's documentation as read on 23 October 2026. 47 actions in 11 areas, each one in the signed service file (version 1.0.0). **Can I combine Tidio with my other systems?** Yes. ask joins Tidio to HaloPSA or NetSuite on the same customer and returns the answer rather than every row. Tidio maps crm.contact, which 192 other connectors also map. **Does actionlake keep my Tidio data, and where?** actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Tidio credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models. **Which AI clients can use it?** Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names. ## More connectors like Tidio Shares the most action names with - [Gorgias 9](https://actionlake.com/connectors/gorgias) - [SysAid 8](https://actionlake.com/connectors/sysaid) - [Zoho Desk 7](https://actionlake.com/connectors/zoho-desk) - [Plain 6](https://actionlake.com/connectors/plain) - [Birdeye 5](https://actionlake.com/connectors/birdeye) - [Freshworks Freshchat 5](https://actionlake.com/connectors/freshworks-freshchat) Joins with, on shared entities - [ConnectWise PSA 2](https://actionlake.com/connectors/connectwise-psa) - [HaloPSA 2](https://actionlake.com/connectors/halopsa) - [NetSuite 2](https://actionlake.com/connectors/netsuite) - [HubSpot CRM 2](https://actionlake.com/connectors/hubspot-crm) - [Salesforce Sales Cloud 2](https://actionlake.com/connectors/salesforce-sales-cloud) - [Acumatica Cloud ERP 2](https://actionlake.com/connectors/acumatica-cloud-erp) Browse - [All Service desk & support connectors](https://actionlake.com/connectors/category/service-desk-and-support) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by Tidio; the name is the vendor's own. Counts are from the Tidio service file, version 1.0.0. ## Give your agent Tidio today. [Connect Tidio free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/tidio More: https://actionlake.com/llms.txt