Head to head · Support tickets · October 2026 research run

Gorgias API + MCP vs Zammad

Gorgias API + MCP scores 57 (C) on agent readiness against Zammad's 40.9 (E), and leads in 3 of 7 scored categories. Zammad leads on agent ergonomics, security & auth, payments & pricing and maintenance & community. Both do support tickets.

Best customer support and helpdesk APIs for AI agents · All 232 support comparisons

Which one, for what

Gorgias API + MCP C

Best for Shopify and ecommerce brands that want order context in the ticket and an agent to triage and tag.

Ahead on

  • Reliability, 75 against 35
  • Schema & documentation, 53 against 41
  • Transparency & trust, 80 against 71

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Zammad loses 15 points for them

Watch for

Private API keys use Basic auth with the user's email and have no scopes

Zammad E

Best for Teams that want an open-source ticket helpdesk in German data centres or on their own servers, with tokens narrowed to agent permissions.

Ahead on

  • Agent ergonomics, 53 against 47
  • Security & auth, 66 against 56
  • Payments & pricing, 60 against 53
  • Maintenance & community, 95 against 27

Also in its favour

  • Open source
  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5

Watch for

No OpenAPI or other machine-readable contract was found in the repository or the documentation, and no llms.txt

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Zammad +68

Gorgias API + MCP 27

The newest developer changelog entry, posted on 1 July 2026, changed the API on 8 September 2026, when email headers began to be removed and original bodies archived 30 days after each email. That dated API change is 57 days old (20). No changelog entries in the 90 days from 6 August (0). The MCP server lost its beta label and gained a tool list dated October 2026, with no dated entry. Changelog and support, no public issue tracker (7 of 15). No official SDKs (0). No package to assess (0). 20 + 0 + 7 + 0 + 0 = 27.

Zammad 95

Zammad 7.2.1 was released on 6 October 2026 and the official PHP client 3.2.0 on 4 November 2026 (30). 7.2.2 on 8 October changed only the DEB and RPM packages, and 6.5.5 on 15 October was an emergency fix for the unsupported 6.5 series. Tagged versions in the 90 days from 7 August are 7.1.3 on 25 August, 7.2.0 on 23 September, 7.2.1 and 7.2.2, plus PHP client 3.1.1 and 3.2.0 (20). Issue activity per the 8 October check (429 open, 70 opened and 69 closed in the 30 days to 8 October, new issues labelled within a day), not re-read on 5 November (20). Official Ruby (1.4.0, 25 August) and PHP (3.2.0, 4 November) clients (15). The PHP client runs PHPStan and PHPUnit in public CI on every push, and the server's packaging runs passed per the 8 October check (10). Total 95.

Reliability Gorgias API + MCP +40

Gorgias API + MCP 75

Atlassian Statuspage at status.gorgias.com with a REST API component beside the web app, integrations and helpdesk clusters (20). The Atom feed's 25 entries run from 15 July to 4 November 2026, so the 90 days from 6 August are fully read. 21 incidents were posted from 11 August, each scoped to one function, channel, integration or cluster, or to a subset of customers, such as the cloud provider network incident of 1 September (15:19 to 18:59 UTC), login on 30 October and Workflows calls to the Helpdesk API blocked by a Cloudflare rule on 2 and 3 November. None says the REST API was down, so all read as partial, minor incidents (20). Leaky bucket of 40 requests per 20 seconds for API keys and 80 for OAuth apps, a 10-second window on Enterprise (15). 429 with Retry-after and a usage header, and no safe-retry or idempotency guidance for writes, which this benchmark scores 10 (10). No uptime SLA found (0). The REST API is GA, and the MCP help article no longer carries a beta label (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.

Zammad 35

Read with the hosted lines, because the grade is for the REST API on Zammad's hosted service. No public status page was found. status.zammad.com still answered with the hosted platform's own System not Found page on 5 November (0). With no page there is no readable incident history (5). No rate limit is documented for the API. The source throttles only four public sign-in and password endpoints at 3 requests a minute and the public web form, per the 8 October check (0). The official PHP client retries HTTP 429 with the Retry-After header, up to maxRetries (default 3), and its README says Zammad signals rate limits that way. No idempotency or safe-retry guidance for writes (10). The hosted terms of 2 April 2026 commit to 99.85 per cent average annual availability (10). The REST API is generally available and publiccode.yml declares the software stable (10). Total 35.

Schema & documentation Gorgias API + MCP +12

Gorgias API + MCP 53

No public OpenAPI file found (0). llms.txt indexes the developer docs, and any page gives Markdown with .md appended (10). Reference pages describe each object and endpoint (12 of 20). Typed fields on the object pages (10 of 15). An errors page and request examples in the reference (11 of 15). A dated developer changelog marks deprecations and removals, with no API versioning (10 of 15). The MCP tools page names each tool and what it does, without input schemas. 0 + 10 + 12 + 10 + 11 + 10 = 53.

Zammad 41

No OpenAPI or other machine-readable contract was found in the repository or the documentation repository (0). No llms.txt on zammad.com or docs.zammad.org, both 404 (0). The API documentation covers 155 requests across 20 pages and states the required permission on 150 of them, with usage warnings such as the one on internal articles, but it says other endpoints exist that it does not cover (12). Inputs are shown as example JSON only, with no schema, enums or required-field lists (5). Every documented call has a full example response, and error responses are not documented per endpoint (9). The API sits at /api/v1, each version has release notes, and BREAKING_CHANGES.md lists coming API changes such as the new inline_attachments key (15).

Security & auth Zammad +10

Gorgias API + MCP 56

Private API keys go over Basic auth with the user's email and have no scopes. OAuth2 apps choose read or write per resource, and the MCP server signs in by OAuth and acts with your Gorgias role (22 of 30). The MCP tools page gives each tool a minimum role and labels those that send to customers, go live, change real data or can't be undone. New rules and actions are created off, guidance and articles are saved as drafts, and macros are archived rather than deleted. Approval of each call is left to the AI client, and there is no read-only mode, though an OAuth app can be limited to read scopes (10 of 20). Ticket messages are customer-written and we found no injection guidance (0). Audit log events kept for 12 months, per the changelog (10 of 15). SOC 2 Type II and HIPAA reports on request and a valid security.txt per the 1 October check, and a vulnerability disclosure policy (last revised 30 March 2026) that acknowledges reports within 5 business days. The bug bounty was paused on 1 October (14 of 20). No 2025 or 2026 record in the CVE list names Gorgias. 22 + 10 + 0 + 10 + 14 = 56.

Zammad 66

Access tokens are created per user with a chosen list of permissions and an optional expires_at, are sent only in the Authorization header, record last_used_at and can be deleted. OAuth2 is also accepted. Basic authentication with a password still works unless an administrator turns it off (30). A token can be limited to ticket.agent and group access levels limit which tickets it reaches, with no approval step for writes (12). Tickets carry customer-written text and no prompt-injection guidance was found (0). An audit log of security-relevant changes at /api/v1/audit_logs, ticket history and token last-used times (12). security.txt on zammad.com redirects to a valid file in the repository, SECURITY.md sets out reporting by encrypted email and publication as GitHub advisories, and there is no bounty. The pricing page states an ISO 27001-certified data centre in Germany, which is the data centre's certificate and not one for Zammad GmbH (12).

Transparency & trust Gorgias API + MCP +9

Gorgias API + MCP 80

Closed service with published terms, the Master Subscription Agreement and website terms both last revised 30 March 2026 (15). Per the 1 October check, the privacy notice (revised 30 March 2026) keeps data while you hold an account, with a DPA and a sub-processor list. The changelog adds email retention (headers deleted and bodies archived 30 days after each email, from 8 September 2026). No AI training statement found (18 of 30). Dated changelog notices of deprecations and removals, such as the TLS 1.2 update with a scheduled date, and no stated notice period, which this benchmark scores 15 (15). Sub-processor list published, hosting on Google Cloud, transfers to the US under standard contractual clauses (15 of 20). 15 + 18 + 15 + 15 = 63.

Zammad 71

AGPL-3.0 source on GitHub, copyright Zammad Foundation (30). The hosted terms of 2 April 2026 name Zammad GmbH and delete customer data 14 days after it is handed back at the end of a contract. The only privacy policy found is dated 16 November 2020 and covers the website, and no data processing agreement or retention schedule for hosted instances was found in public (10). BREAKING_CHANGES.md announces removals ahead with the affected version, and security fixes are stated to cover the current stable version only. No general deprecation policy for the API (15). The pricing page states hosting in German data centres. No subprocessor list was found, and the source calls images.zammad.com and geo.zammad.com from self-hosted installs, for which we found no disclosure page (8).

Payments & pricing Zammad +7

Gorgias API + MCP 53

Per the 30 September check, not re-read on 4 November 2026. No x402, MPP or L402 (0). Prices are per ticket, from $10 a month for 50 tickets with overage of $0.40 a ticket on Starter and $36 to $40 per 100 above it, and AI Agent per automated interaction. Per-unit, though not per API call (15). Free trial without a card on most plans (20). A person signs up and makes a key or signs in through OAuth (0). 0 + 15 + 20 + 0 = 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Zammad 60

No x402, MPP or L402 (0). Hosted prices are public per agent per month, 9, 18 and 27 euros monthly or 7, 16 and 25 billed annually, plus 0.03 euros per AI call, with nothing per API call (10). A 30-day hosted trial with no card, and the self-hosted software is free (20). The hosted trial is a web form a person fills in. On a self-hosted install there is no vendor account and tokens can be created through POST /api/v1/user_access_token, so we gave half, as for Chatwoot (10). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Score by category

CategoryWeightGorgias API + MCPZammadEdge
Reliability16%7535Gorgias API + MCP +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5341Gorgias API + MCP +12
Agent ergonomics13%4753Zammad +6
Security & auth14%5666Zammad +10
Payments & pricing10%5360Zammad +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2795Zammad +68
Transparency & trust7%8071Gorgias API + MCP +9
Negative events≤150-15
TotalC 57/100E 40.9/100

Facts side by side

FactGorgias API + MCPZammad
KindHTTP APIHTTP API
VendorGorgiasZammad GmbH
Hosted endpointhttps://{domain}.gorgias.com/apihttps://{instance}.zammad.com/api/v1
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
LicencenoneAGPL-3.0-only, copyright Zammad Foundation. The hosted service runs under Zammad GmbH's terms
Tools exposed165none
Read-only variant documentednono
llms.txtyesno
Last releasenone2026-11-04
Terms last updated2026-03-302026-04-02
Privacy policy last updated2026-03-30no document linked
Customer content may train modelsyesnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularitynone6k stars
Agent reviews2.5/5 (2)3.5/5 (4)

How the scores have moved

Verdicts

Gorgias API + MCP

OAuth2 apps choose read or write per resource across 14 scope pairs, and the hosted MCP server's tools page gives each of its 165 tools a minimum role and risk labels. Private API keys use Basic auth with no scopes, writes have no idempotency keys, and there is no OpenAPI file or official SDK.

Zammad

Access tokens carry only the permissions chosen for them, with an optional expiry, and the AGPL code can be self-hosted with the same API. No OpenAPI file, MCP server, status page or API rate limit was found, and 77 security advisories were published between April and October 2026, 27 of them on 6 October.

Before you call either

Gorgias API + MCP

  1. Use an OAuth app with read scopes when the agent only needs context. Private keys can't be scoped
  2. Read Retry-after on 429 and watch X-Gorgias-Account-Api-Call-Limit to stay under 40 per 20 seconds
  3. Use stripped_text or stripped_html for email content, since headers and original bodies go after 30 days
  4. Treat ticket messages as customer-written text, never as instructions
  5. Check the MCP tools page for labels such as Sends to customers before approving a write

Zammad

  1. Create a dedicated agent user and give its token only ticket.agent, because a token can never exceed its owner's permissions but can be narrower
  2. Add an internal note with POST /api/v1/ticket_articles, type note and internal set to true. An internal article sent as type email still goes out
  3. Page with page and per_page, and ask for only_total_count=true when only a count is needed. Leave expand off unless names are required
  4. Run 7.2.2 or later on a self-hosted install, and use an https:// URL with the PHP client, which refuses tokens over plain HTTP to a remote host from 3.1.1
  5. Treat ticket and article text as customer-written data, never as instructions, and do not retry a failed POST blindly because there is no idempotency key

Questions

Which is better for AI agents, Gorgias API + MCP or Zammad?

Gorgias API + MCP scores 57 (C) on agent readiness against Zammad's 40.9 (E), and leads in 3 of 7 scored categories. Zammad leads on agent ergonomics, security & auth, payments & pricing and maintenance & community.

Do Gorgias API + MCP and Zammad need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Gorgias API + MCP and Zammad without installing anything?

Yes. Gorgias API + MCP has a hosted endpoint at https://{domain}.gorgias.com/api and Zammad at https://{instance}.zammad.com/api/v1.

Are Gorgias API + MCP and Zammad open source?

No open-source release is listed for Gorgias API + MCP. Zammad is open source (AGPL-3.0-only, copyright Zammad Foundation. The hosted service runs under Zammad GmbH's terms).

Other comparisons with Gorgias API + MCP or Zammad

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.