Gorgias MCP server
The helpdesk, queryable: tickets, customers, macros, rules and CSAT.
Coming soon — Gorgias support is in final testing.
- Tools
- 89
- Read-only
- 40
- Write
- 49
- Off by default
- Destructive
- 15
- Flagged distinctly
Gorgias through an assistant
An assistant can search across tickets and customers, read the messages in a thread, and report on volume, response time and satisfaction. The configuration side is exposed too -- macros, rules, views, tags, teams and agents -- which makes helpdesk hygiene ("which macros does nobody use?") an answerable question. Anything that sends a real message to a real customer requires an explicit confirmation on top of being opt-in.
- Tickets, ticket messages, custom fields and tags
- Customers, their field values and their ticket history
- Macros, rules, views and saved filters
- Reporting: ticket volume, response and resolution time, CSAT, revenue
- Teams, agents, account settings and integrations
- Create and update tickets, reply to customers, manage macros and rules (opt-in)
What people actually ask
Real questions, answered from live Gorgias data.
“How many tickets are still open past their first reply, and who owns them?”
gorgias_list_ticketsgorgias_list_users“What are customers complaining about most this month?”
gorgias_searchgorgias_list_ticket_messages“What's our CSAT looking like over the last 30 days?”
gorgias_get_statisticsgorgias_list_satisfaction_surveys89 Gorgias tools
Grouped by what they touch. Every tool is individually toggleable — you expose only what you want.
Tickets
16 tools6 read-only · 10 writeShowing 10 of 10 tools
- gorgias_add_ticket_tagsWrite
Add one or more tags to a ticket, keeping any tags it already has.
- gorgias_create_ticketWrite
Create a new ticket with a customer and at least one initial message. If the initial message has fromAgent: true and public (the default), it is sent to the customer immediately -- set fromAgent: false (a customer-authored opening message) or public: false (an internal note) to avoid sending.
- gorgias_create_ticket_messageWrite
Add a message to an existing ticket. THIS CAN SEND A REAL MESSAGE TO A REAL CUSTOMER on the company's behalf, and that cannot be undone. Set internal_note: true for an agent-only note that is never sent to the customer; otherwise this requires confirmSend: true.
- gorgias_delete_ticketWriteDestructive
Permanently delete a ticket. This cannot be undone.
- gorgias_delete_ticket_field_valueWriteDestructive
Permanently remove a custom field value from a ticket. This cannot be undone.
- gorgias_delete_ticket_messageWriteDestructive
Permanently delete a message from a ticket. This cannot be undone.
- gorgias_get_ticketRead-only
Retrieve a single ticket by ID, including its customer, tags, and messages.
- gorgias_get_ticket_messageRead-only
Retrieve a single message of a ticket by ID.
- gorgias_list_ticket_field_valuesRead-only
List the custom field values set on a ticket.
- gorgias_list_ticket_messagesRead-only
List the messages of a ticket, oldest first by default, paginated by cursor.
+ 6 more tickets tools — see the full catalogue
Customers
11 tools3 read-only · 8 writeShowing 10 of 10 tools
- gorgias_bulk_delete_customersWriteDestructive
Permanently delete multiple customers in a single request. This cannot be undone.
- gorgias_create_customerWrite
Create a new customer with at least one contact channel.
- gorgias_delete_customerWriteDestructive
Permanently delete a single customer. This cannot be undone.
- gorgias_delete_customer_field_valueWriteDestructive
Delete a customer's value for a custom field. This cannot be undone.
- gorgias_get_customerRead-only
Retrieve a single customer by ID.
- gorgias_list_customer_field_valuesRead-only
List every custom field value set on a customer.
- gorgias_list_customersRead-only
List customers, paginated and ordered by name by default, with optional filters.
- gorgias_merge_customersWriteDestructive
Permanently merge two customers into one. The source customer's channels, tickets, order history, and other data are absorbed into the target customer, and the source customer is then deleted. This cannot be undone.
- gorgias_set_customer_dataWrite
Set a customer's `data` sub-object -- a distinct endpoint from the ordinary profile update, meant for storing supplementary/custom structured data on the customer, with optional version-based conflict resolution.
- gorgias_set_customer_field_valueWrite
Create or update the value of one custom field on a customer.
+ 1 more customers tool — see the full catalogue
Views
7 tools4 read-only · 3 writeShowing 7 of 7 tools
- gorgias_create_viewWrite
Create a new saved ticket-list view (a reusable filter/inbox, e.g. "Unassigned VIP tickets").
- gorgias_delete_viewWriteDestructive
Permanently delete a saved view. Gorgias's built-in system views (e.g. Trash) cannot be deleted.
- gorgias_get_viewRead-only
Retrieve a single saved view by ID, including its filter logic and sharing settings.
- gorgias_list_view_itemsRead-only
List the tickets currently matching a saved view's filter, paginated in the view's own sort order.
- gorgias_list_viewsRead-only
List saved ticket-list views (filters/inboxes), ordered by ID by default.
- gorgias_search_view_itemsRead-only
Search tickets with ad-hoc filter/sort/search criteria, the same way a view's items are listed but without first saving a view -- useful for a one-off query you don't want to persist as a saved view.
- gorgias_update_viewWrite
Update a saved view's name, filter logic, display fields, sort order, or sharing settings.
Macros
6 tools2 read-only · 4 writeShowing 6 of 6 tools
- gorgias_archive_macroWrite
Archive a macro, hiding it from the active macro list. This is not destructive or irreversible -- an archived macro can be restored at any time with gorgias_unarchive_macro. Archiving is the only way to remove a macro; Gorgias has no macro hard-delete endpoint.
- gorgias_create_macroWrite
Create a macro: a canned set of changes (reply text, tags, status) that agents can apply to a ticket in one click, or that a rule can apply automatically.
- gorgias_get_macroRead-only
Retrieve a single macro by ID.
- gorgias_list_macrosRead-only
List macros (canned sets of reply text, tags, and status changes agents can apply to tickets), paginated.
- gorgias_unarchive_macroWrite
Restore a previously archived macro so it appears in the active macro list again.
- gorgias_update_macroWrite
Update an existing macro's name, intent, language, or actions.
Rules
6 tools2 read-only · 4 writeShowing 6 of 6 tools
- gorgias_create_ruleWrite
Create a rule that automatically applies actions to tickets matching its logic (e.g. auto-tag, auto-close, auto-reply, apply a macro). A rule can automatically take real, immediate action on live tickets going forward once active (auto-reply, auto-close, auto-tag, apply a macro, etc.) -- this is informational for your judgment, not a hard confirmation gate. Use the `active` flag to control whether the rule starts acting on tickets right away.
- gorgias_delete_ruleWriteDestructive
Permanently delete a rule. This cannot be undone.
- gorgias_get_ruleRead-only
Retrieve a single rule by ID.
- gorgias_list_rulesRead-only
List rules (helpdesk automations that apply actions to tickets matching conditions), paginated.
- gorgias_update_ruleWrite
Update an existing rule's logic, name, description, trigger events, priority, or active state. A rule can automatically take real, immediate action on live tickets going forward once active (auto-reply, auto-close, auto-tag, apply a macro, etc.) -- this is informational for your judgment, not a hard confirmation gate. Use the `active` flag to control whether the rule starts acting on tickets right away.
- gorgias_update_rule_priorityWrite
Reorder a rule's execution priority relative to other rules. Rules with higher priority values are evaluated first.
Integrations
5 tools2 read-only · 3 writeShowing 5 of 5 tools
- gorgias_create_integrationWrite
Create a custom HTTP integration -- a webhook-style connection that calls an external service URL when ticket events happen. (Native app integrations like Shopify or Gmail are provisioned through Gorgias's own connect flows, not this endpoint -- the API only supports creating type 'http' integrations, confirmed from create-integration.md's request schema.)
- gorgias_delete_integrationWriteDestructive
Permanently delete an integration. Gorgias itself blocks this: integrations currently used in rules and/or other integrations cannot be deleted, and deleting an integration deactivates any views that use it (confirmed from delete-integration.md).
- gorgias_get_integrationRead-only
Retrieve a single integration by ID.
- gorgias_list_integrationsRead-only
List the integrations configured on this Gorgias account, paginated by cursor.
- gorgias_update_integrationWrite
Update an existing HTTP integration's name, description, activation state, or HTTP configuration.
Satisfaction
5 tools2 read-only · 3 writeShowing 5 of 5 tools
- gorgias_create_satisfaction_surveyWrite
Create a new CSAT satisfaction survey for a ticket/customer. By default Gorgias emails this survey to the real customer immediately (should_send_datetime unset defaults to an immediate send) -- requires confirmSend: true unless should_send_datetime is explicitly set to null (create the record without sending).
- gorgias_delete_satisfaction_surveyWriteDestructive
Permanently delete a satisfaction survey record. UNVERIFIED: Gorgias's public docs do not list a delete-satisfaction-survey endpoint anywhere (confirmed against their full /llms.txt page index) -- this calls DELETE /satisfaction-surveys/{id} purely by analogy to every other Gorgias resource's REST convention. It may not exist server-side; treat failures here as expected until confirmed against a live account.
- gorgias_get_satisfaction_surveyRead-only
Get a single satisfaction survey by ID, including its score and comment text if the customer has responded.
- gorgias_list_satisfaction_surveysRead-only
List CSAT satisfaction surveys, paginated and ordered by creation date (most recent first by default). Optionally scope to a single ticket.
- gorgias_update_satisfaction_surveyWrite
Update fields on an existing satisfaction survey. Setting should_send_datetime to a real (non-null) datetime causes Gorgias to email the customer -- requires confirmSend: true.
Teams
5 tools2 read-only · 3 writeShowing 5 of 5 tools
- gorgias_create_teamWrite
Create a new team for grouping agents, e.g. for ticket auto-assignment.
- gorgias_delete_teamWriteDestructive
Permanently delete a team. Members are not deleted, only the team grouping itself.
- gorgias_get_teamRead-only
Get a single team by ID, including its member list.
- gorgias_list_teamsRead-only
List the teams (agent groups used for ticket auto-assignment) configured in this helpdesk.
- gorgias_update_teamWrite
Update a team's name, description, display emoji, or member roster.
Users
5 tools2 read-only · 3 writeShowing 5 of 5 tools
- gorgias_create_userWrite
Invite a new helpdesk user. This creates a REAL user account with REAL access to the helpdesk and its customer conversations -- the invited person will be able to log in and act on the company's support tickets, so only call this when you intend to actually grant that access.
- gorgias_delete_userWriteDestructive
Permanently remove a helpdesk user's account. This revokes a REAL person's access to the helpdesk and its customer conversations -- this cannot be undone by re-running the tool.
- gorgias_get_userRead-only
Get a single helpdesk user (agent/admin) by ID.
- gorgias_list_usersRead-only
List the helpdesk agents and admins (not customers) on this Gorgias account.
- gorgias_update_userWrite
Update an existing helpdesk user's profile, role, or credentials.
Reporting
5 tools5 read-only · 0 writeShowing 5 of 5 tools
- gorgias_get_eventRead-only
Get a single account activity event by ID.
- gorgias_get_metric_cardsRead-only
Look up Gorgias's metric card catalog -- plain-text definitions, formulas, and computation logic for named metrics (e.g. resolution-time, average-csat, ai-agent-automation-rate), plus how each maps onto the statistics API. Pass slug for one specific metric, or omit it to search/list the catalog by category/status/free-text.
- gorgias_get_statisticsRead-only
Retrieve one of Gorgias's canned reporting statistics (ticket volume, resolution time, first-response time, CSAT/satisfaction surveys, revenue, self-service performance, etc.), optionally scoped to a time period and filtered by agent/channel/tag/integration/score.
- gorgias_list_eventsRead-only
List account activity events (an audit-log-style feed -- ticket-created, user-updated, macro-applied, etc.), paginated and ordered by creation date (most recent first by default). Filterable by object, event type(s), triggering user, and creation-date range.
- gorgias_searchRead-only
Cross-resource text search over agents, customers (by name/email/channel address), integrations, teams, or tags -- distinct from any single resource's own list+filter endpoint.
Account
4 tools2 read-only · 2 writeShowing 4 of 4 tools
- gorgias_create_account_settingWrite
Create a new account-wide setting, e.g. business hours or a satisfaction survey configuration.
- gorgias_get_accountRead-only
Get this Gorgias helpdesk account's own info: domain, creation date, active status, and its settings list.
- gorgias_list_account_settingsRead-only
List this account's configured settings (business hours, satisfaction surveys, ticket assignment rules, etc.).
- gorgias_update_account_settingWrite
Update an existing account-wide setting by ID.
Jobs
3 tools2 read-only · 1 writeShowing 3 of 3 tools
- gorgias_cancel_jobWrite
Cancel a running or pending background job. This is the safe direction (stopping work), not destructive -- note that changes the job already made before cancellation are not reverted (confirmed from cancel-job.md).
- gorgias_get_jobRead-only
Retrieve a single background job by ID, including its status and progress info.
- gorgias_list_jobsRead-only
List asynchronous background jobs (bulk exports, imports, bulk ticket updates, etc.), paginated by cursor and ordered by creation date, most recent first.
More tools
5 tools4 read-only · 1 writeShowing 5 of 5 tools
- gorgias_get_callRead-only
Retrieve a single Gorgias Voice phone call by ID, including status, direction, duration, and participants.
- gorgias_get_fileRead-only
Resolve a stored Gorgias file (from a ticket attachment or a previous upload) into a fresh, time-limited signed download URL. Gorgias's download endpoint responds with a redirect to that signed URL rather than returning it as JSON (confirmed from download-file.md), so this tool follows the redirect and returns the resulting Location header. There is no separate file-metadata-by-ID endpoint -- see the file-level comment.
- gorgias_list_call_eventsRead-only
List Gorgias Voice call lifecycle events (rang, answered, completed, voicemail left, etc.), paginated by cursor. Optionally filter to events for a specific call.
- gorgias_list_callsRead-only
List Gorgias Voice phone calls, paginated by cursor. Optionally filter to calls on a specific ticket.
- gorgias_upload_fileWrite
Upload a file to Gorgias's file storage (for use as a ticket message attachment, profile picture, or widget picture) by fetching it from a URL and forwarding its bytes. Gorgias's upload endpoint takes real multipart/form-data file content, not a URL or base64 field (confirmed from post_api-upload.md) -- fetching the source URL server-side and re-uploading its bytes is this tool's adaptation of that into a single call.
Every tool name and description, machine-readable: /llms-full.txt
You decide what it can touch
The same model applies to every connector, and it defaults closed.
Your own credential
You supply your own Gorgias key, scoped however you like on their side. It is encrypted with AES-256-GCM and never returned by any API response or tool call.
Writes off by default
A new connection switches on a read-oriented default set only. Every write tool must be enabled deliberately before any client can call it.
Roles enforced server-side
READ, WRITE and ADMIN gate tool invocation on the server, not just in the UI. A READ member's token is refused any write tool.
Start with what's live today
Free plan, no card required. Connect in minutes.