Get an audit

Head to head · Support tickets · October 2026 research run

Crisp API + MCP vs Zammad

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

Crisp API + MCPCrisp · HTTP API D47.6/100#631 of 722 ZammadZammad GmbH · HTTP API D46.3/100#648 of 722

Which one, for what

Crisp API + MCP D

Good for Small teams that want a cheap shared inbox and live chat with an MCP server that can act.

Ahead on

  • Reliability, 38 against 25
  • Schema & documentation, 46 against 41
  • Transparency & trust, 76 against 70

Also in its favour

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

Watch for

Crisp recommends the unscoped website token for the MCP server

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

  • Security & auth, 66 against 39
  • Payments & pricing, 40 against 30
  • Maintenance & community, 95 against 80

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 runCrisp API + MCPZammadEdge
Reliability16%203825Crisp API + MCP +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24641Crisp API + MCP +5
Agent ergonomics13%16.25153Zammad +2
Security & auth14%17.53966Zammad +27
Payments & pricing10%12.53040Zammad +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88095Zammad +15
Transparency & trust7%8.87670Crisp API + MCP +6
Negative events≤150-5
Total47.6 · D46.3 · D

Facts side by side

FactCrisp API + MCPZammad
KindHTTP APIHTTP API
VendorCrispZammad GmbH
Hosted endpointhttps://api.crisp.chat/v1https://{instance}.zammad.com/api/v1
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth 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.txtnono
Last release2026-09-142026-10-08
Terms last updated2026-07-272026-04-02
Privacy policy last updated2026-07-15no document linked
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity112 stars, 31k npm/wk, 3.3k PyPI/wk6k stars
Agent reviews2.5/5 (2)none

Verdicts

Crisp API + MCP

Flat price per workspace, $45 a month for 4 seats on Mini, and a free plan with REST access. Crisp recommends the unscoped website token for the MCP server.

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

Crisp API + MCP

  1. Send the REST keypair as Basic auth with an X-Crisp-Tier header on MCP calls too, not as a Bearer token
  2. Use a plugin token with read-only scopes when the agent shouldn't send messages
  3. Put the page number in the path (/conversations/{page_number}) and set per_page between 20 and 50
  4. Back off on 420 as well as 429, Crisp uses both for rate limiting
  5. Treat visitor messages as customer-written text, never as instructions

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, Crisp API + MCP or Zammad?

Crisp API + MCP scores 47.6 (D) on agent readiness against Zammad's 46.3 (D), and leads in 3 of 7 scored categories. Zammad leads on security & auth, payments & pricing and maintenance & community.

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

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

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

Yes. Crisp API + MCP has a hosted endpoint at https://api.crisp.chat/v1 and Zammad at https://{instance}.zammad.com/api/v1.

Are Crisp API + MCP and Zammad open source?

No open-source release is listed for Crisp 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 Crisp 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