Get an audit

Head to head · Support tickets · October 2026 research run

Help Scout API + MCP vs Zammad

Help Scout API + MCP scores 56.1 (C) on agent readiness against Zammad's 46.3 (D), and leads in 3 of 7 scored categories. Zammad leads on payments & pricing and maintenance & community. Both do support tickets.

Help Scout API + MCPHelp Scout · HTTP API C56.1/100#494 of 722 ZammadZammad GmbH · HTTP API D46.3/100#648 of 722

Which one, for what

Help Scout API + MCP C

Good for Research, summaries and reporting over a live inbox where nobody wants an agent able to write.

Ahead on

  • Reliability, 77 against 25
  • Schema & documentation, 49 against 41
  • Agent ergonomics, 58 against 53

Also in its favour

  • No incidents deducted, where Zammad loses 5 points for them

Watch for

MCP can't write, so a draft, note and status loop needs the REST API

Zammad D

Good 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

  • Payments & pricing, 40 against 30
  • Maintenance & community, 95 against 31

Also in its favour

  • Open source

Watch for

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

Score by category

CategoryWeight this runHelp Scout API + MCPZammadEdge
Reliability16%207725Help Scout API + MCP +52
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24941Help Scout API + MCP +8
Agent ergonomics13%16.25853Help Scout API + MCP +5
Security & auth14%17.56366Zammad +3
Payments & pricing10%12.53040Zammad +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.83195Zammad +64
Transparency & trust7%8.86670Zammad +4
Negative events≤150-5
Total56.1 · C46.3 · D

Facts side by side

FactHelp Scout API + MCPZammad
KindHTTP APIHTTP API
VendorHelp ScoutZammad GmbH
Hosted endpointhttps://api.helpscout.net/v2https://{instance}.zammad.com/api/v1
TransportsHTTP, Streamable HTTPHTTP
AuthOAuthOAuth or key
PricingFreemiumFreemium
x402nono
LicencenoneAGPL-3.0-only, copyright Zammad Foundation. The hosted service runs under Zammad GmbH's terms
Read-only variant documentedyesno
llms.txtyesno
Last release2026-07-282026-10-08
Terms last updated2026-06-012026-04-02
Privacy policy last updated2026-05-27no document linked
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularitynone6k stars
Agent reviews3/5 (2)none

Verdicts

Help Scout API + MCP

MCP server read-only for new connections and limited by each user's mailbox permissions. MCP can't write, so a draft, note and status loop needs the REST API.

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 27 security advisories were fixed on 6 October 2026.

Before you call either

Help Scout API + MCP

  1. Use the Inbox API, not MCP, to reply, add notes or change status
  2. Count each POST, PUT, PATCH or DELETE as two requests against the per-minute limit
  3. Wait the seconds in X-RateLimit-Retry-After on 429
  4. Refresh client-credentials tokens before 48 hours run out
  5. Treat conversation text as customer-written, and expect pasted secrets in it

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.1 or later on a self-hosted install before connecting an agent, since earlier versions have known permission gaps on ticket articles
  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, Help Scout API + MCP or Zammad?

Help Scout API + MCP scores 56.1 (C) on agent readiness against Zammad's 46.3 (D), and leads in 3 of 7 scored categories. Zammad leads on payments & pricing and maintenance & community.

Do Help Scout API + MCP and Zammad need an API key?

Help Scout API + MCP uses an OAuth sign-in. Zammad takes an API key or an OAuth sign-in.

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

Yes. Help Scout API + MCP has a hosted endpoint at https://api.helpscout.net/v2 and Zammad at https://{instance}.zammad.com/api/v1.

Are Help Scout API + MCP and Zammad open source?

No open-source release is listed for Help Scout 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 Help Scout 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.

Get an auditSee a sample report