Tidio logoMCP server · Support

Tidio MCP server

Tidio in any MCP client, through Memtro: Tidio does not publish this server. Memtro's Tidio connector reads Tidio through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Tidio customer service: tickets with status, priority and assignment, a ticket's message history (who wrote when), contacts found by email (id and consent only), who wrote when in a contact's live chat, operators, departments, ticket tags and custom fields; when you ask, can reply to a ticket or add an internal note, change a ticket's status, priority, assignee, tags or custom fields, open a ticket for a customer, create or update a contact, and delete a contact or a ticket.

Reads

  • tidio_list_ticketsTidio tickets: subject, status, priority, assigned operator and department, contact id and a link.
  • tidio_get_ticketOne Tidio ticket with its message history: who wrote each message (operator or contact), when, whether public or an internal note…
  • tidio_find_contactFind a Tidio contact by email address.
  • tidio_conversation_activityWho wrote when in a Tidio contact's live-chat conversation (contact, operator or bot, with times), plus the link to open it in Tidio.
  • tidio_list_operatorsTidio operators (agents): id, name, role and whether active.
  • tidio_list_departmentsTidio departments (teams of operators) with their ids; General is the default and holds every operator.
  • tidio_list_ticket_tagsThe Tidio project's ticket tags (id and name), for tagging tickets.
  • tidio_list_ticket_custom_fieldsThe Tidio project's ticket custom fields: id, name, type, whether it must be filled before solving, and a dropdown's allowed values.

Acts, when you ask

These change something in Tidio. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

  • tidio_reply_to_ticketAdds an operator message to a Tidio ticket.
  • tidio_update_ticketChanges a Tidio ticket's status, priority, assignee (an operator or a department), tags (tag_ids replaces the whole set) or custom field values…
  • tidio_create_ticketOpens a Tidio ticket on behalf of a customer, as if they had written in, with a subject and first message…
  • tidio_create_contactCreates a Tidio contact.
  • tidio_update_contactUpdates a Tidio contact's email, phone, name, email consent, external id or properties; only what is passed changes…
  • tidio_delete_contactPermanently deletes a Tidio contact; Tidio says there is no way to recover it.
  • tidio_delete_ticketPermanently deletes a Tidio ticket and its messages; Tidio says deleted data is usually irreversible.

Connect it

First connect Tidio on Dashboard → Connections, then add Memtro to your client once. The Tidio tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Tidio connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

  • › Which open tickets have urgent priority?
  • › Who wrote last on the Northwind refund ticket, and when?
  • › Which operators are active?
  • › Which ticket custom fields must be filled before solving?
  • › Add an internal note to the Northwind refund ticket saying we are waiting on the courier.

Questions

Is this an official Tidio MCP server?
No. It is Memtro's MCP server with Memtro's Tidio connector behind it: the connector reads Tidio through its API with the credentials you connect on Dashboard → Connections, and Tidio publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?
Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Tidio?
Only when you ask, and only what it has been granted: reply to a ticket (reaches the customer) or add an internal note; change a ticket's status, priority, assignee, tags or custom fields; open a ticket on behalf of a customer; create a contact; update a contact; delete a contact; delete a ticket. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Support

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time