Connect Gorgias to Claude Code

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

How do you connect Gorgias to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Gorgias, you add a Gorgias MCP server: a small hosted service that exposes Gorgias'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 Gorgias account. No API keys pasted into config files.

claude mcp add --transport http gorgias 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 Gorgias once connected?

Full read-write Gorgias access lets Claude reply inside the original ticket, keep the customer and channel intact, apply tags, set status, assign to an agent or team, and add internal notes. The triage and drafting that used to mean switching tabs happen where the ticket already lives, once you approve.

Draft a reply inside an existing ticket, preserving the customer and channel
Add or remove tags to triage and route incoming tickets
Assign a ticket to a specific agent or team
Set ticket status to open or closed as you clear the queue
Add an internal note for the next agent without messaging the customer
Find every ticket 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 Gorgias 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 Gorgias API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Gorgias 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 Gorgias 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 Gorgias 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 Gorgias 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 Gorgias'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 Gorgias?

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 Gorgias account it signs in with. Revoking access is one click in Gorgias.

More on the Gorgias connector

Gorgias connector for claude.ai Kustomer + Claude Code Zoho Desk + Claude Code HappyFox + 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