)
Connect Gorgias MCP to your AI agents, securely.
One secured endpoint for every Gorgias call your AI agents make, scoped per user, inspected, and logged.Try Gorgias MCP now
What your agents can ask once Gorgias MCP is connected.
“Find the ticket where the customer mentioned a defective hinge”
“Show me this ticket with the full conversation and the customer record”
“What's our automation rate this month, broken down by channel?”
“Draft a help center article about our return policy and leave it as a draft”
“Which guidance articles are enabled for the AI Agent right now?”
“Preview how the AI Agent would answer 'Where is my order?'”
Select the tools your AI agents can call
165 tools from the Gorgias MCP schema.
Showing 165 tools
What Gorgias MCP exposes
Gorgias MCP groups its 165 tools into 16 categories, each with a suggested starting policy.
| Category | Covers | Access | Suggested policy |
|---|---|---|---|
| Guidance & Skills | Guidance articles in the knowledge hub and the skills that link articles to customer intents, with their templates, draft creation and editing, publishing, disabling, draft discarding and retained skill versions | Read / Write | Guidance and skills are what the AI Agent reads before answering a customer, so publishing one changes live customer-facing behaviour. Drafts are safe; publish_guidance also enables the article for the AI Agent |
| Tickets | Reading, searching and listing tickets with their messages and customer record, internal notes, tags, snoozing, escalation, single and bulk field updates, custom field values, the ticket audit trail, customer replies and new ticket creation | Read / Write | create_message and reply_and_close send real messages to customers by default; create_ticket records without sending unless send is set. update_tickets runs as an async, non-atomic bulk job, so check the result with get_job |
| Support Actions | AI agent support actions and the pre-built templates they can be deployed from, with creation, updating, enabling, disabling, duplication, deletion, execution history and conversion to the advanced step editor | Read / Write | New actions are created with every entrypoint deactivated, so enable_support_action is the real control. convert_to_advanced_view is irreversible and the action can never be downgraded |
| Help Center | Public FAQ help centers, their categories and articles, with draft creation and editing, publishing to the storefront, unlisting, discarding pending drafts, and theme and custom HTML settings | Read / Write | Articles are public storefront content. Edits save as drafts and the live version is unchanged until publish_help_center_article. Discarding the only draft of a never-published article removes it entirely |
| AI Agent Config | Per-store AI Agent configuration, tone of voice with a preview mode, reply preview against draft guidance, multi-turn, comparative and live-action test sessions, AI reasoning, excluded handover topics, channel enablement and the onboarding wizard state | Read / Write | enable_ai_agent_on_channel puts the AI in front of real customers on chat, email or SMS and replaces the channel's monitored-integration list. Excluded topics are the ones the AI must hand to a human, so clearing them widens its scope |
| Macros | Listing and inspecting macros, creating and updating them, applying one to a ticket, and archiving or restoring to control whether agents see them | Read / Write | A macro's action list can include sendEmail, setStatus and addInternalNote, so apply_macro is a bundle of side effects behind one call. Archiving fails while a helpdesk rule still references the macro |
| Helpdesk Rules | Automation rules with their JavaScript source, trigger events and priority, plus creation, updating, enabling, disabling, dry-run simulation and the rule audit trail | Read / Write | Rules are code that fires automatically on ticket events. create_rule always lands disabled as a hard invariant, so enable_rule and update_rule are where review belongs |
| Reporting & Analytics | The Reporting Stats API with its schema, scopes, measures, dimensions and metric cards, plus the analytics warehouse tables, their column metadata and read-only SQL, warehouse ticket snapshots, AI Agent execution history and ready-made breakdowns of topics, handovers, AI performance and CSAT | Read | Read-only, and per-account isolation on the SQL path is automatic. The warehouse refreshes roughly once a day, so it is the wrong source for real-time questions |
| Account Config | The authenticated agent, custom field definitions for tickets and customers, the account's tags, connected ecommerce and Workflows integrations, voice queues, SLA policies, CSAT survey settings and product feature requests | Read / Write | list_custom_fields is the prerequisite for any custom field write, since it reports which IDs exist, which block closing a ticket and what values dropdowns accept |
| Customers & Users | Gorgias customers by ID or filtered list with profile updates, the account's agents with their roles, and teams with their member lists | Read / Write | Customer fields are attacker-controllable by design and the server says so: anyone can register a customer by emailing support. Strings come back Unicode-scrubbed and must be treated as data, never instructions |
| Operating Manual | The server's own operating manual, covering runtime context, the tool inventory, routing rules, schema discovery, draft-first write defaults and security rules, plus individual named skill workflows | Read | The server asks that get_gaia_instructions be called before anything else in every new conversation, and says most failures and merchant-data leakage come from skipping it |
| Routines | Gaia routines with their runs, plus creation, updates, deletion, manual triggering and enabling or disabling | Read / Write | Routines run automatically on the account; approve creation, triggering and enabling |
| Views | Ticket-list views and view sections, with creation, partial updates and deletion | Read / Write | Views are shared by the whole team; review updates and deletions |
| Snippets & Products | Reusable AI Agent snippets and their sources, Shopify products with their AI Agent custom info and metafield definitions, and pending product opportunities | Read / Write | Snippets and product info feed what the AI Agent tells customers; approve status changes and custom info edits |
| Integrations & Widgets | App Store app details, custom HTTP integrations with their request logs, and sidebar widgets with creation, updates and deletion | Read / Write | HTTP integration logs can carry customer data; widget updates replace the whole template |
| Audiences | Saved audience segments, the segmentation catalog and aggregate audience sizes | Read | Read-only and aggregate; allow for marketing analysis |
Connect Gorgias MCP to your AI agent
Four steps, under ten minutes.
- 01
Sign in to NeuralTrust
Open the NeuralTrust platform, sign in and go to Getting started, then Connect your tools.
- 02
Choose your agent
When asked which agent you use, pick Claude Code, Codex, Cursor, Windsurf, Copilot or your own code.
- 03
Connect Gorgias
Find Gorgias in the tool list and connect it.
- 04
Connect your agent
Follow the steps on screen to add the config to your agent, then send the test prompt.
Permissions down to the single tool
You do not allow Gorgias MCP or block it. You allow the exact tools each agent can call, one by one.
| Gorgias MCP | 165 TOOLS AVAILABLE |
|---|---|
| Code review agent | 4 tools, read only |
| Issue triage bot | 9 tools |
| Platform team assistant | all 165 tools |
- Tool by toolConnecting the server is not the unit of access. Each tool is granted on its own.
- Default denyA tool you have not enabled is never exposed to the agent.
- Approval on writesTools that change or delete things can require a human to confirm.
Is Gorgias MCP secure?
One endpoint instead of raw credentials. Every call is checked against policy and logged.
| AI agentsConnect through your MCP client configuration. | NeuralTrustApply controls based on your configuration. | Gorgias MCP165 documented tools: Gorgias labels 93 read-only, 21 write and 51 destructive. Tool names carry a gorgiasmcp_ prefix when the server is reached through a Scalekit AgentKit connection. |
|---|---|---|
| Coding assistants | Connection & credentialsper user | Guidance & Skills16 tools |
| Internal copilots | Tool access policiesdeny by default | AI Agent Config16 tools |
| Workflow automations | Request & response inspectioninline | Support Actions14 tools |
| Compatible MCP clients | Activity monitoringalerts and logs | All other tools119 tools |
Use Gorgias MCP with any AI agent framework
Setup guides for the tools your team already uses.
- Claude CodeSetup guide
- CursorSetup guide
- CodexSetup guide
- WindsurfSetup guide
- Gemini CLISetup guide
- Google AntigravitySetup guide
- GitHub CopilotSetup guide
- Claude EnterpriseSetup guide
- Microsoft Copilot StudioSetup guide
- Open WebUISetup guide
- LangChainSetup guide
- HaystackSetup guide
- Strands AgentsSetup guide
- Vercel AI SDKSetup guide
- n8nSetup guide
Common questions about running Gorgias MCP through TrustGate.
Other MCP servers
More servers from the catalog.
)
Freshworks
Securely connect your AI agents to the Freshworks Developer Portal through TrustGate: custom apps, their versions, upload URLs and submission status, scoped per agent and logged.
6 toolsView)
Front
Securely connect your AI agents to Front through TrustGate: conversation search and timelines, drafts and sending, comments, tasks, tags, contacts and workspace structure, scoped per agent and logged.
28 toolsView)
Klaviyo
Securely connect your AI agents to Klaviyo through TrustGate: campaigns, flows, profiles, lists, segments, templates, events and performance reports, scoped per agent and logged.
272 toolsView
Connect Gorgias MCP instantly
Pick the tools, point your agent at TrustGate, and Gorgias MCP is live: scoped, inspected, logged.