[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Tidio API and MCP server

> Tidio has a REST API, the OpenAPI, for contacts, tickets, operators and departments, but only on the Plus and Premium plans, and its two official MCP servers cannot work your inbox (checked 17 Oct 2026). One MCP connector installs the chat widget; the other reads analytics and "can't send messages, change settings, or modify anything".

Customer service platform that combines live chat, email tickets, chatbot Flows and the Lyro AI agent in one inbox for small and mid-size businesses.

## What is the Tidio API?

Cotlet's Tidio API exposes 14 endpoints for your own Tidio account: list conversations, get conversation, list tickets, get ticket, list contacts, get contact, list macros, list flows, list operators, reply to ticket, reply in live chat, update ticket, update contact and create macro. The list_conversations endpoint returns live chat conversations in the Tidio Inbox, in the order the Inbox shows them. Each endpoint takes simple JSON inputs like limit, cursor or ticket_id and works both as an operation of the tidio_read or tidio_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Customer support](https://cotlet.dev/integrations/category/customer-support.md)
- **Endpoints:** 14 (9 read, 5 write)
- **Updated:** 2026-10-18

Tidio has a REST API, the OpenAPI, for contacts, tickets, operators and departments, but only on the Plus and Premium plans, and its two official MCP servers cannot work your inbox (checked 17 Oct 2026). Cotlet is a hosted MCP server and REST API for Tidio with 14 endpoints (9 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Tidio have an official API?

Tidio has a REST API, the OpenAPI, for contacts, tickets, operators and departments, but only on the Plus and Premium plans, and its two official MCP servers cannot work your inbox (checked 17 Oct 2026). One MCP connector installs the chat widget; the other reads analytics and "can't send messages, change settings, or modify anything".

| Task | Tidio official | Cotlet |
|---|---|---|
| List and read tickets | Partly: OpenAPI, Plus and Premium; the list has no filters and carries no messages | Yes |
| Reply to a ticket or add an internal note | Partly: OpenAPI, Plus and Premium; no official MCP server | Yes |
| Change a ticket | Partly: OpenAPI update ticket, Plus and Premium | Yes |
| List contacts and update their properties | Partly: OpenAPI, Plus and Premium; list filters by email only | Yes |
| Read the conversation history of a contact | Partly: OpenAPI, Plus and Premium; per contact, no list of conversations | Yes |
| Reply in a live chat as an operator | No: The API can only post a message as the contact | Yes |
| List and create macros | No | Yes |
| Read your Flows | No: The Analytics API reports Flow statistics, not the Flows themselves | Yes |

Sources: [Tidio developers: Enable Tidio OpenAPI](https://developers.tidio.com/docs/openapi-enable), [Tidio developers: Rate limiting](https://developers.tidio.com/docs/openapi-rate-limiting.md), [Tidio developers: Analytics API MCP](https://developers.tidio.com/docs/analytics-api-mcp.md), [Tidio MCP Connector (widget install tools)](https://github.com/TidioPoland/tidio-mcp-connector)

## For AI agents

```text
Tidio has a REST API, the OpenAPI, for contacts, tickets, operators and departments, but only on the Plus and Premium plans, and its two official MCP servers cannot work your inbox (checked 17 Oct 2026). One MCP connector installs the chat widget; the other reads analytics and "can't send messages, change settings, or modify anything".
Cotlet provides a hosted MCP server and REST API for Tidio: 14 tools (9 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=tidio, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    tidio_read, tidio_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/tidio, each operation at its own route, e.g. POST /api/v1/tidio/tickets/{ticket_id}/replies
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_conversations, get_conversation, list_tickets, get_ticket, list_contacts, get_contact, list_macros, list_flows, list_operators, reply_to_ticket, reply_in_conversation, update_ticket, update_contact, create_macro
Confirm      reply_to_ticket, reply_in_conversation (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/tidio-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=tidio, requests Tidio in the Cotlet console and creates an API key there.
2. The user signs in to Tidio once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Tidio for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Tidio server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Tidio MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Tidio in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Tidio only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Tidio login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Tidio's terms; Cotlet is not affiliated with Tidio.
```

## What can an AI agent do in Tidio?

Cotlet is best for Tidio support teams on Free, Starter or Growth, or on Plus without a developer, who want an agent to triage tickets, draft replies and keep contacts current without running or fixing a server.

- **[Triage new support tickets](https://cotlet.dev/integrations/tidio-api-mcp-server/triage-support-tickets.md)** (runs: daily): "Go through the Unassigned tickets in Tidio. Set the priority from what the customer wrote, put refund requests with the Billing department and add a tag, and leave anything unclear for me." → `list_tickets`, `get_ticket`, `list_operators`, `update_ticket`
- **[Reply to waiting support tickets](https://cotlet.dev/integrations/tidio-api-mcp-server/reply-to-support-tickets.md)** (runs: daily): "Find Open tickets in Tidio with no reply from us yet. Draft an answer from my help articles to each simple one and send it after I confirm, and add an internal note on the rest." → `list_tickets`, `get_ticket`, `reply_to_ticket`
- **[Update contact properties in bulk](https://cotlet.dev/integrations/tidio-api-mcp-server/update-contact-properties.md)** (runs: weekly): "List Tidio contacts with an email on our domain list, set their plan property to customer and add the tag vip to the ones I name, then tell me how many changed." → `list_contacts`, `get_contact`, `update_contact`
- **Build a macro library from answered chats** (runs: weekly): "Look at last week's answered Tidio conversations, find the questions we answered by hand more than 3 times, and create a macro for each one that is not already in Macros." → `list_conversations`, `get_conversation`, `list_macros`, `create_macro`
- **Review chatbot flows each week** (runs: weekly): "List my Tidio Flows with their triggers, and tell me which ones start on the same trigger so I can check they do not overlap." → `list_flows`

## Can Tidio automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Tidio connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to triage new support tickets, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/tidio/tickets. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/tidio/tickets with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 14 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Tidio.

### list_conversations

Live chat conversations in the Tidio Inbox, in the order the Inbox shows them. Access: read. REST: `GET /api/v1/tidio/conversations`. MCP: `tidio_read → list_conversations`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_email` | string | no | Only conversations of the contact with this email. |
| `limit` | integer | no | 1 to 50. Default: 25. |
| `cursor` | string | no | Next page cursor from the previous call. |

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.

Example response:

```json
{
  "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
}
```

### get_conversation

Every message of one live chat conversation, with who wrote each. Access: read. REST: `GET /api/v1/tidio/conversations/{conversation_id}`. MCP: `tidio_read → get_conversation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | string | yes | Conversation ID from list_conversations. |

Returns the messages of one conversation from the oldest to the newest. Each message has an author type of operator, contact or bot, the text and the time. It also returns the link that opens the conversation in the Tidio panel.

Example response:

```json
{
  "conversation_id": "cv_5a21",
  "url": "https://www.tidio.com/panel/inbox/conversations/cv_5a21",
  "messages": [
    {
      "author_type": "contact",
      "message": "Does the blue one come in size L?",
      "created_at": "2026-10-16T14:02:00Z"
    },
    {
      "author_type": "bot",
      "message": "Let me get a teammate for you.",
      "created_at": "2026-10-16T14:02:05Z"
    },
    {
      "author_type": "operator",
      "message": "Yes, L is in stock.",
      "created_at": "2026-10-16T14:09:40Z"
    }
  ]
}
```

### list_tickets

Email tickets from a folder, with status, priority, assignee and department. Access: read. REST: `GET /api/v1/tidio/tickets`. MCP: `tidio_read → list_tickets`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `folder` | enum | no | unassigned, my_open or solved. Default: unassigned. |
| `status` | enum | no | open, pending or solved. Default: any. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists tickets of one Inbox folder: unassigned, my_open or solved. Each ticket has an ID, subject, contact, status (open, pending or solved), priority (low, normal or urgent), assignee and department. Messages are not included; use get_ticket for them. Pages hold up to 100 tickets; pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "tickets": [
    {
      "ticket_id": 10477,
      "subject": "Charged twice for order 2290",
      "contact_email": "mark.dole@example.com",
      "status": "open",
      "priority": "normal",
      "assignee": null,
      "department": null
    },
    {
      "ticket_id": 10482,
      "subject": "When does my order ship?",
      "contact_email": "mark.dole@example.com",
      "status": "open",
      "priority": "normal",
      "assignee": null,
      "department": null
    }
  ],
  "next_cursor": null
}
```

### get_ticket

One ticket with all its messages, tags and internal notes. Access: read. REST: `GET /api/v1/tidio/tickets/{ticket_id}`. MCP: `tidio_read → get_ticket`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from list_tickets. |

Returns the ticket fields plus every message from the oldest to the newest, public replies and internal notes marked apart, and the ticket tags. Use it before replying so the answer fits the whole thread.

Example response:

```json
{
  "ticket_id": 10482,
  "subject": "When does my order ship?",
  "status": "open",
  "priority": "normal",
  "tags": [],
  "messages": [
    {
      "author_type": "contact",
      "visibility": "public",
      "body": "Hi, I ordered on Monday. When does it ship?",
      "created_at": "2026-10-16T08:12:00Z"
    }
  ]
}
```

### list_contacts

Contacts with email, tags and contact properties. Access: read. REST: `GET /api/v1/tidio/contacts`. MCP: `tidio_read → list_contacts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `email` | string | no | Only the contact with this email. |
| `tag` | string | no | Only contacts with this tag. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the contacts of your account with name, email, country, tags and the contact properties you created in Settings > Fields. Filter by email for one contact, or by tag. Pages hold up to 100 contacts; pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "contacts": [
    {
      "contact_id": "c4d9e1a2-77b0-4e0f-9a31-5b2c8e6f0d13",
      "name": "Mark Dole",
      "email": "mark.dole@example.com",
      "country": "US",
      "tags": [],
      "properties": {
        "plan": "trial"
      }
    }
  ],
  "next_cursor": null
}
```

### get_contact

One contact with every property and tag. Access: read. REST: `GET /api/v1/tidio/contacts/{contact_id}`. MCP: `tidio_read → get_contact`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Contact ID from list_contacts. |

Returns the full record of one contact: name, email, phone, language, country, email consent, tags and all contact properties by name. Use it to check which properties exist before writing with update_contact.

Example response:

```json
{
  "contact_id": "c4d9e1a2-77b0-4e0f-9a31-5b2c8e6f0d13",
  "name": "Mark Dole",
  "email": "mark.dole@example.com",
  "phone": null,
  "language": "en",
  "country": "US",
  "email_consent": "subscribed",
  "tags": [],
  "properties": {
    "plan": "trial"
  }
}
```

### list_macros

Macros (saved replies) with name, label and text. Access: read. REST: `GET /api/v1/tidio/macros`. MCP: `tidio_read → list_macros`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `label` | string | no | Only macros with this label. |

Lists the macros in Settings > General > Macros with their name, label, whether they are private and their text. Use it before create_macro so the agent does not add a duplicate. Macros need the Growth plan or higher.

Example response:

```json
{
  "macros": [
    {
      "name": "Shipping time",
      "label": "Orders",
      "private": false,
      "text": "Orders ship within 2 business days. You will get a tracking link by email."
    }
  ]
}
```

### list_flows

Chatbot Flows from My Flows, with their trigger. Access: read. REST: `GET /api/v1/tidio/flows`. MCP: `tidio_read → list_flows`.

No parameters.

Lists the Flows in the Flows section with the name and the trigger of each, for example Visitor opens a specific page or Visitor Says. Use it to spot Flows that start on the same trigger. It reads the Flows and changes none of them.

Example response:

```json
{
  "flows": [
    {
      "name": "Welcome new visitors",
      "trigger": "First visit on site"
    },
    {
      "name": "Pricing page help",
      "trigger": "Visitor opens a specific page"
    }
  ]
}
```

### list_operators

Operators of your account with their departments. Access: read. REST: `GET /api/v1/tidio/operators`. MCP: `tidio_read → list_operators`.

No parameters.

Returns the operators who can be assigned to a ticket or chat, with name, email and department. Use the names it returns as the assignee of update_ticket.

Example response:

```json
{
  "operators": [
    {
      "name": "Dana Reyes",
      "email": "dana@example.com",
      "department": "Support"
    },
    {
      "name": "Piotr Nowak",
      "email": "piotr@example.com",
      "department": "Billing"
    }
  ]
}
```

### reply_to_ticket

Send a public reply or an internal note on a ticket. Access: write, asks the user first. REST: `POST /api/v1/tidio/tickets/{ticket_id}/replies`. MCP: `tidio_write → reply_to_ticket`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from list_tickets. |
| `body` | string | yes | Message text. |
| `visibility` | enum | no | public or internal. Default: public. |

Adds a message to a ticket as you. A public reply is emailed to the customer; an internal note stays with your team and reaches no one. Pass the text in body. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "ticket_id": 10482,
  "visibility": "public",
  "status": "sent",
  "url": "https://www.tidio.com/panel/inbox/tickets/10482"
}
```

### reply_in_conversation

Send a message to a visitor in a live chat as an operator. Access: write, asks the user first. REST: `POST /api/v1/tidio/conversations/{conversation_id}/replies`. MCP: `tidio_write → reply_in_conversation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | string | yes | Conversation ID from list_conversations. |
| `body` | string | yes | Message text. |

Posts a message in a live chat conversation as you, and the visitor sees it in the chat widget. It cannot be unsent. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "conversation_id": "cv_5a21",
  "status": "sent"
}
```

### update_ticket

Change priority, status, assignee, department or tags of a ticket. Access: write. REST: `PATCH /api/v1/tidio/tickets/{ticket_id}`. MCP: `tidio_write → update_ticket`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `ticket_id` | integer | yes | Ticket ID from list_tickets. |
| `status` | enum | no | open, pending or solved. |
| `priority` | enum | no | low, normal or urgent. |
| `assignee` | string | no | Operator name from list_operators. |
| `department` | string | no | Department name from list_operators. |
| `add_tags` | string[] | no | Ticket tags to add, from Settings > Tags. |
| `remove_tags` | string[] | no | Ticket tags to remove. |

Changes the fields you pass and leaves the rest. Status is open, pending or solved and priority is low, normal or urgent. It sends no message to the customer, and a wrong change is undone by calling it again with the old values, so it needs no confirmation by default. It returns the ticket as it is after the change.

Example response:

```json
{
  "ticket_id": 10477,
  "status": "open",
  "priority": "urgent",
  "assignee": null,
  "department": "Billing",
  "tags": [
    "refund"
  ]
}
```

### update_contact

Set contact properties and add or remove tags on a contact. Access: write. REST: `PATCH /api/v1/tidio/contacts/{contact_id}`. MCP: `tidio_write → update_contact`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Contact ID from list_contacts. |
| `properties` | object | no | Property names and their new values. |
| `add_tags` | string[] | no | Customer tags to add. |
| `remove_tags` | string[] | no | Customer tags to remove. |

Sets the contact properties you pass by name and leaves the others. The property must already exist in Settings > Fields, and the agent cannot create one with it. It sends nothing to the contact, and a wrong value is undone by calling it again, so it needs no confirmation by default. It returns the contact after the change.

Example response:

```json
{
  "contact_id": "c4d9e1a2-77b0-4e0f-9a31-5b2c8e6f0d13",
  "properties": {
    "plan": "customer"
  },
  "tags": [
    "vip"
  ]
}
```

### create_macro

Add a macro (saved reply) to Settings > General > Macros. Access: write. REST: `POST /api/v1/tidio/macros`. MCP: `tidio_write → create_macro`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `text` | string | yes | Macro text. |
| `name` | string | no | Name used to find the macro by typing. |
| `label` | string | no | Label used to group macros. |
| `private` | boolean | no | true keeps the macro private to you. Default: false. |

Creates a macro with a text, an optional name for finding it by typing a slash in a chat, and an optional label. A macro reaches no customer until someone sends it, and it is removed in one click in Settings, so it needs no confirmation by default. It needs the Growth plan or higher.

Example response:

```json
{
  "name": "Shipping time",
  "label": "Orders",
  "private": false,
  "status": "created"
}
```

## How do I connect Tidio to Claude Code, Codex or Cursor?

Connecting Tidio takes three steps: sign up, sign in to Tidio once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Tidio to your agent.

1. **Create an account** Sign up and add Tidio in the console. Your API key is there too.

2. **Sign in to Tidio in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Tidio there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Tidio tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Go through the Unassigned tickets in Tidio. Set the priority from what the customer wrote, put refund requests with the Billing department and add a tag, and leave anything unclear for me.
```

### Call Tidio from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/tidio with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
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"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "ticket_id": 10482,
  "visibility": "public",
  "status": "sent",
  "url": "https://www.tidio.com/panel/inbox/tickets/10482"
}
```

## Why use Cotlet for Tidio?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Tidio yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Tidio changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Tidio to Cotlet?

Yes. You sign in to Tidio yourself, in your own Cloud Browser, and we never save your password. Your agents only get Tidio once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Tidio integration?**

No, Cotlet is independent of Tidio. Tidio's own API is too limited for this work. Cotlet works through your own Tidio account, the way you use Tidio in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Tidio in your console: your agents lose access at once and you stay signed in. Signing out of Tidio in the browser works too, and Reset browser deletes the whole profile.

## Is there a Tidio MCP server on GitHub?

Yes. Community Tidio MCP servers exist on GitHub, usually maintained by one person. You install one on your own computer, connect it to Tidio, and keep it running yourself; when Tidio changes, it stops working until you or the maintainer fix it. Cotlet hosts the same kind of server for you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, install it, connect it to Tidio, add it to each MCP client | Sign up, sign in to Tidio once, add one MCP server or API key |
| When Tidio changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Tidio session | In a file on your computer, readable by any program you run | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | Tools fail until you sign in again by hand | Your Cloud Browser keeps you signed in; if Tidio logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Tidio changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Tidio API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Tidio API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Tidio account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Tidio yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Tidio only after you enable it. When Tidio signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Tidio, sign out of Tidio in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Tidio's terms:** You use your own Tidio account and stay responsible for following Tidio's terms. Cotlet is independent and not affiliated with Tidio. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Tidio in the console and press Request access. Then you create your API key and connect Tidio there.

**Do I need to be technical?**

No. You sign in to Tidio once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Tidio to Cotlet?**

Yes. You sign in to Tidio yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Tidio once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Tidio sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Tidio cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Tidio's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Tidio sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Tidio login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Tidio offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**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.

**Can my agent post or send messages in Tidio without asking me?**

No. Every call to reply_to_ticket or reply_in_conversation waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. update_ticket, update_contact, create_macro runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Tidio API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/tidio from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

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.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.