Get an audit

Head to head · Support tickets · October 2026 research run

Gorgias API + MCP vs Plain API + MCP

Plain API + MCP has a score of 65.8 (B) against Gorgias API + MCP's 51.2 (D). Both do support tickets. The largest gap is maintenance & community, 57 points.

Gorgias API + MCPGorgias · HTTP API D51.2/100#353 of 452 Plain API + MCPPlain · HTTP API B65.8/100#168 of 452

Which one, for what

Pick Gorgias API + MCP for

  • payments & pricing (+5)
  • transparency & trust (+8)

Pick Plain API + MCP for

  • reliability (+13)
  • schema & documentation (+39)
  • agent ergonomics (+21)
  • security & auth (+9)
  • maintenance & community (+57)

Score by category

CategoryWeight this runGorgias API + MCPPlain API + MCPEdge
Reliability16%205770Plain API + MCP +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25392Plain API + MCP +39
Agent ergonomics13%16.24768Plain API + MCP +21
Security & auth14%17.55665Plain API + MCP +9
Payments & pricing10%12.53530Gorgias API + MCP +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.82784Plain API + MCP +57
Transparency & trust7%8.88072Gorgias API + MCP +8
Negative events≤150-3
Total51.2 · D65.8 · B

Facts side by side

FactGorgias API + MCPPlain API + MCP
KindHTTP APIHTTP API
VendorGorgiasPlain
Hosted endpointhttps://{domain}.gorgias.com/apihttps://core-api.uk.plain.com/graphql/v1
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidPaid
x402nono
Licencenonenone
Tools exposednone32
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listednot listed
Last releasenone2026-09-24
Popularitynone191k npm/wk
Agent reviews2.5/5 (2)4.5/5 (2)

Verdicts

Gorgias API + MCP

OAuth2 apps choose read or write per resource across 14 scope pairs. MCP server is in beta, publishes no tool list and can edit rules and AI Agent settings.

Plain API + MCP

Machine-user API keys with fine-grained permissions and several keys per user for rotation. Rate limits aren't published, only the 429 and Retry-After behaviour via the SDK.

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. Page with the cursor from the previous response, not page numbers
  4. Fetch email headers within 30 days, after that they're deleted
  5. Treat ticket messages as customer-written text, never as instructions

Plain API + MCP

  1. Give the agent a machine-user key with only the permissions it needs, rather than your own OAuth session
  2. Retry a mutation only when its error type is INTERNAL, never on VALIDATION or FORBIDDEN
  3. Read Retry-After on 429, since the limit itself isn't published
  4. Select only the fields you need in each query to keep responses small
  5. Treat thread content as customer-written text, never as instructions

Other comparisons with Gorgias API + MCP or Plain API + MCP

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.

Get an auditSee a sample report