Gorgias MCP connector
The Gorgias connector brings your helpdesk tickets, customers, messages, tags, and agents into Claude, ChatGPT, Cursor, Microsoft Copilot, or the Elaichi Agent, so your team can ask about and work Gorgias tickets in plain language, inside their own Gorgias access, with every action logged.
- Connects over OAuth
- Free 14-day trial
- No credit card
Show open Gorgias tickets from the last 48 hours.
Working in Gorgias with Elaichi
-
List all Gorgias users
-
Get single Gorgias user by ID
-
List all Gorgias tickets
How to connect Gorgias to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Gorgias MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Gorgias MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Gorgias MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Gorgias MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Gorgias MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Gorgias to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Gorgias through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Gorgias is logged.
-
Support
Find every open ticket about one order
Ask for the open Gorgias tickets that mention a specific order or customer and get the list with status, assignee, and last message, without scrolling through views.
-
Support
Catch up on a customer before replying
Pull a Gorgias customer's profile, their past tickets, and the message history in one ask, so the reply is written with the whole story in view.
-
Support
Tag and reassign tickets in bulk
Tell the agent to add a tag, change the status, or move a batch of Gorgias tickets to the right person after triage, instead of opening each one.
-
Customer experience
Summarize a week of ticket themes
Read through the messages on recent Gorgias tickets and group them by what customers are complaining about, ready to paste into the weekly review.
-
Store operations
Log a ticket from a warehouse report
When a shipment goes wrong, create a Gorgias ticket against the affected customer with the details filled in, so the support team sees it in their queue right away.
-
Admin
Clean up duplicate tags and stale agents
Merge Gorgias tags that mean the same thing, rename inconsistent ones, and add or remove helpdesk users as people join and leave the team.
Try asking
- “Show open Gorgias tickets from the last 48 hours.”
- “Which customers filed more than three tickets this month?”
- “Summarize ticket volume by Gorgias user this week.”
What connecting Gorgias gets you
6 screens from Elaichi, each doing one job for your Gorgias account.
Ask Elaichi to work across your apps.
Show open Gorgias tickets from the last 48 hours.
Which customers filed more than three tickets this month?
Summarize ticket volume by Gorgias user this week.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about tickets, read the answer.
Plain language questions answered from live Gorgias tickets, customers and users.
Copy the endpoint
AI apps
One Gorgias endpoint for every MCP client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, no SDK, no shared key.
Tool catalog
104 Gorgias tools ready on connect.
Tickets, customers, users and messages covered without writing custom code.
Toolboxes
Every team gets its own toolbox.
Support, billing and ops each see a Gorgias toolbox scoped to them.
Shared connections
Teammates work tickets without a credential.
Each Gorgias connection shows who added it and which teams use it.
Audit log
Answer who touched which ticket.
Every Gorgias call is logged with time, actor, action, type and resource.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Gorgias digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch tickets
Gorgias
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Gorgias
Queued
Automations
A schedule fires, the digest posts back.
Gorgias tickets are fetched, grouped, drafted, approved by a person, then posted.
Gorgias health
Refreshed 4 minutes ago · every 15 minutes · from the tickets collection
Tickets
1,284 ↓ 12%
Customers
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Tickets created
Last 14 days
By team
Share of activity
Support EMEA 34%
Support US 27%
Billing 21%
Retention 18%
Collections and dashboards
Gorgias health, counted on a schedule.
Four metrics, fourteen days of tickets created, split by team, no model.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Gorgias
All three can connect Gorgias to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Gorgias tools | Allow or restrict single Gorgias tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Gorgias call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Gorgias tools for your AI agents
104 tools are ready to call through Elaichi's MCP endpoint the moment you connect Gorgias, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Gorgias to Claude?
Connect Gorgias in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Gorgias asks you to register an OAuth application inside your own Gorgias account, so one person brings that client ID and secret to Elaichi once, then everyone else simply signs in to Gorgias with their usual login when prompted. After that, Claude can work with Gorgias tickets, customers, and tags as the person who signed in.
Does Gorgias work with ChatGPT and Cursor as well as Claude?
Yes. Once Gorgias is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Gorgias once and every client picks it up.
What can an AI agent actually do with my Gorgias data?
An agent connected to Gorgias can look up tickets, read the messages on them, find a customer and their history, create new tickets, update status, assignee, or tags on existing ones, and manage tags and helpdesk users. Because Gorgias has a lot of capabilities, the agent searches for the right one as it goes, so short concrete asks like "open tickets tagged refund from this week" work better than long paragraphs.
Does connecting Gorgias give the AI access to every ticket in the helpdesk?
No. Every call to Gorgias runs as the person who signed in, so the AI sees only the tickets, customers, and settings that person can already see in Gorgias. Elaichi can narrow that further with restrictions, but it can never grant more than the person's own Gorgias permissions allow.
Can I stop an agent from deleting or changing things in Gorgias?
Yes. Restrictions in Elaichi work per action, so you can allow reading Gorgias tickets and customers while restricting deletes, or restricting any change at all. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to a Gorgias connection when someone leaves?
Offboarding that person in Elaichi ends their access to Gorgias through every AI client at once. A shared Gorgias connection keeps working for everyone else on the team. If you ever want to remove Gorgias entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client together.
Does the Gorgias MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Gorgias is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Gorgias?
Yes. Both let Claude, ChatGPT or Cursor use Gorgias. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Gorgias call.
How is Elaichi different from Composio for Gorgias?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Gorgias: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Gorgias in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot