Shop MCP

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
AreaExamples
Support queueTickets, messages, tags, views, events, status and assignee context
Customer contextCustomers, custom fields, customer data, linked ticket history
Automation hygieneMacros, rules, views, satisfaction surveys, jobs, integrations, widgets
Operations playbooksQueue triage, SLA risk, repeat issues, ecommerce order support, CSAT trends, response context

1. Connect with OAuth

Open Settings - Integrations - Gorgias, enter your Gorgias subdomain, and choose Connect with OAuth. For https://acme.gorgias.com, enter acme.

OAuth is the preferred path for the public Gorgias app. 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 starts as an admin-only integration with writes globally off while the OAuth app and webhook behavior are sandbox-tested.

2. 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.
  • Write scopes are requested for staged testing, but ShopMCP hides write tools unless the global gate and workspace write toggle both allow them.

Writes and safety

Read tools are available once Gorgias is connected. Write tools are hidden by default. When enabled for a test workspace, writes can create/update tickets, add internal notes or public replies, update tags, update customer fields, adjust macros/rules/views/surveys, and manage ShopMCP-owned HTTP integration records.

  • Public replies and ticket status changes should be reviewed before sending.
  • Destructive deletes and merge operations are not part of v1.
  • Webhook requests are accepted only with a valid HMAC signature.

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.
  • Write tools missing - this is expected until ShopMCP enables writes for the integration and the workspace admin turns on the write toggle.

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.