Connect Tidio to Claude Code

Let Claude draft replies and manage tickets in Tidio. From the terminal, inside the sessions where you already work.

How do you connect Tidio to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Tidio, you add a Tidio MCP server: a small hosted service that exposes Tidio's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Tidio account. No API keys pasted into config files.

claude mcp add --transport http tidio https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Tidio once connected?

Full read-write Tidio access lets Claude reply to a ticket, open and update tickets, change ticket status, assignment, and tags, and update contact properties, all in the same workspace your agents use. The triage and drafting that used to mean copy-paste happen where your tickets already live, once you approve outbound replies.

Draft and post a reply on a Tidio ticket after you approve it
Create a ticket from a chat and set its priority and status
Assign or reassign a ticket to the right agent or department
Set or replace the tags on a ticket to keep queues organized
Update contact properties such as name, email, or phone
Find conversations matching a query and propose batched responses

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Tidio access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Tidio API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Tidio changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Tidio connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Tidio connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Tidio account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Tidio's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Tidio?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Tidio account it signs in with. Revoking access is one click in Tidio.

More on the Tidio connector

Tidio connector for claude.ai Gorgias + Claude Code Kustomer + Claude Code Zoho Desk + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us