Connect a module

Gorgias

Connect Gorgias so your AI workspace can triage ecommerce support queues, inspect customer/ticket context, review macros and rules, scan CSAT trends, and draft support responses with the rest of your commerce data nearby.

What Gorgias adds

Gorgias is the helpdesk layer for ecommerce support. ShopMCP brings that support context into the same MCP workspace as Shopify, Magento, Neto, Klaviyo, Stripe, GA4, Google Search Console, Help Center content, and the rest of your operating stack.

Gorgias coverage in ShopMCP
Area	Examples
Support queue	Tickets, messages, tags, views, events, status and assignee context
Customer context	Customers, custom fields, customer data, linked ticket history
Automation hygiene	Macros, rules, views, satisfaction surveys, jobs, integrations, widgets
Operations playbooks	Queue triage, SLA risk, repeat issues, ecommerce order support, CSAT trends, response context

1. Install from Gorgias

The preferred public app flow starts inside Gorgias so OAuth is triggered from the Gorgias app listing.

From your Gorgias account, open Settings - App Store - All Apps.
Find ShopMCP in the app list.
Select the app, then click Connect App.
Authorize the app when Gorgias opens the OAuth approval screen.

ShopMCP stores the access token and refresh token encrypted at rest, refreshes tokens when needed, and does not expose credentials to MCP clients.

Private rollout status

Gorgias is read-only during the current public app review. ShopMCP does not create a Gorgias HTTP integration or write any records in this version.

2. ShopMCP admin fallback

Admins can also start OAuth from Settings - Integrations - Gorgias by entering the Gorgias subdomain and choosing Connect Gorgias. For https://acme.gorgias.com, enter acme.

3. Private API-key beta

Admins can also connect with a Gorgias REST API key for sandbox validation. Enter the subdomain, admin email, API key, and an optional label. ShopMCP verifies the credentials with a lightweight account probe before storing them.

Use API keys for validation only

API-key mode is for Igor/admin testing and troubleshooting. Customer-facing installs should use OAuth once the Gorgias app is approved.

Required scopes

Basic OAuth identity: openid, email, profile, offline.
Read scopes: account, users, customers, tickets, custom fields, events, integrations, jobs, macros, rules, satisfaction surveys, statistics, tags, and apps.

Read-only posture

Read tools are available once Gorgias is connected. ShopMCP does not create tickets, update customers, add notes, change tags, adjust macros or rules, or create HTTP integrations in the current public app version.

There should be no ShopMCP-created HTTP integration visible inside Gorgias.
Future write or webhook features will be submitted for Gorgias review before release.
Credentials remain encrypted at rest and are never sent to Claude, ChatGPT, Cursor, or another MCP client.

Try these prompts

Show my riskiest open Gorgias tickets and explain which ones need escalation first.
Find repeat delivery-delay issues from the last 14 days and group them by likely root cause.
For order #12345, pull the Gorgias ticket history and join it with Shopify order context.
Review our Gorgias macros and rules for stale or overlapping support automation.
Draft a response context for this ticket using customer history, messages, tags, and relevant macros.

Troubleshooting

OAuth button is disabled - the operator still needs to set GORGIAS_CLIENT_ID and GORGIAS_CLIENT_SECRET.
State mismatch - restart the OAuth flow from ShopMCP. The state cookie expires after 10 minutes.
401 or 403 - reconnect the account and confirm the Gorgias app has the required read scopes.

Use it from Claude, ChatGPT, or Cursor

Once connected, use your workspace MCP URL in any MCP-compatible client. The tool names start with gorgias_, but you usually do not need to call them by name. Ask the support question naturally and ShopMCP routes to the right Gorgias tools.