Gorgias MCP: tools, roles and customer-record checks
Connect an approved AI client to Gorgias MCP, checking the actual role, retrieved ticket and available actions before relying on customer-facing changes.
- Published
- Last updated
Gorgias MCP connects an approved AI client to your helpdesk, with actions limited by your Gorgias role. Use it to retrieve the correct support record before approving any change. A connected assistant can still select the wrong customer or run a tool with immediate effects.
Model Context Protocol (MCP) is the connection standard. Your client’s approval settings and your Gorgias permissions are separate controls. Permission to run a tool doesn’t establish that the proposed action is correct.
Identify the connection and role
Connect through your approved client’s Gorgias directory entry, then confirm which account and user the connection uses. Gorgias’s connection guide requires a Helpdesk account and your account subdomain. Managed workspaces can require an administrator to enable the connection first.
- Select the Gorgias connector in your client and start its connection flow.
- Enter the intended Gorgias subdomain, sign in and review access before authorising it.
- Return to the client. Request
get_current_userand compare the returned identity with the account you intended to use. - Confirm your assigned role in Gorgias. Inspect the selected tool’s schema and minimum role before running the task.
Gorgias’s user-permissions guide distinguishes ticket and customer work from AI Agent configuration, which needs a Lead or Admin. Don’t infer authority from an assistant saying it can help. A suggested tool call and a successful authorised call are different observations.
Before approving a call, identify whether it reads records, changes configuration or can send a customer message. Record the target ID and intended effect alongside the tool name. This gives the person approving it something concrete to check.
Verify the actual support task
Start with a bounded lookup and compare the returned record with the original support request. In this fictional exercise, a customer asks whether the navy jacket in order 7301 has shipped. Ticket 4602 is the intended test record.
- Retrieve ticket 4602 with
get_ticket, including its messages. Read the customer’s actual request instead of relying on the ticket subject. - Retrieve its customer profile with
get_customer. Compare the customer ID with the ticket’s customer reference. A shared name alone is insufficient. - Compare order 7301 with the customer’s order record in the connected store. Match the jacket variant and shipping state. Keep a customer’s claim that it shipped separate from a store’s fulfilment status.
- If product context is needed, use
search_productsonly where available. Gorgias lists this connected-product search for Lead and Admin roles. Match the exact variant before using its details. - Prepare an answer using the retrieved fields. If the order lookup hasn’t returned a fulfilment state, leave that state out of the answer.
An incorrect result would combine ticket 4602 with another customer’s order 7301 from a different store. The correct result keeps the store and customer identity attached to the order throughout the lookup.
Read each tool’s actual input schema before supplying IDs or filters. A tool list describes possible operations, while the connected schema tells the client what inputs this operation accepts. Restrict the lookup to the records needed for this question.
Control customer-facing changes
Check the specific operation’s effect before approving a change. Gorgias documents create_draft_guidance as a draft and publish_guidance as making that draft available to AI Agent. Both need Lead or Admin access. Updating an enabled rule can take effect immediately.
For a fictional guidance change about jacket dispatch, approve the draft text separately from publication. After saving, retrieve the guidance and compare its draft with the approved wording. Before publication, confirm that the draft remains unpublished. After an authorised publication, retrieve the published content and confirm that the intended wording is active.
A preview also needs an explicit choice. Gorgias documents preview_ai_agent as simulating actions. Its preview_ai_agent_with_live_actions counterpart can change real store data. Choose the simulated tool for an exercise and inspect the returned test conversation. Treat a request for live actions as a separate decision.
For a customer reply, review the recipient and complete message before approval. After an authorised send, inspect the ticket’s saved message and delivery state. An assistant’s confirmation alone doesn’t establish which recipient received it.
Diagnose refused or stale access
Use the failure’s actual evidence to choose the correction. A wrong record needs a different response from a missing permission.
| Symptom | Check | Correction |
|---|---|---|
| Role refusal | Compare the tool’s minimum role with your assigned role | Have an authorised colleague run the task, or request the specific access your job needs |
| Tool absent | Inspect the connected server’s discovered tools and account | Correct the selected connection before changing permissions |
| Authentication failure | Check whether the client requests sign-in again | Reconnect to the intended account and repeat a permitted read |
| Wrong customer or store | Compare returned IDs with the original ticket | Stop the answer and retrieve the correct records |
| Change outcome uncertain | Read the saved record and any returned job status | Establish whether the first call completed before attempting another write |
When withdrawing access, disconnect the integration in the AI client and remove its authorisation through the available account or administrator controls. Confirm that a fresh read from that client is refused. Closing a conversation alone doesn’t prove the connection has lost access.
If a reply might already have been sent, inspect the ticket before retrying. Keep the tool error and target ID for your administrator, with customer details removed from anything shared outside your support team. Resume only after the connection and the saved record agree about what happened.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.