# Drag vs Zammad (slim)

> Drag scores 40 (E) to Zammad's 38.4 (E) for support conversations. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/drag-vs-zammad.md (~4,900 tokens) · this version ~2,780 tokens · JSON https://www.anchorterminal.com/compare/drag-vs-zammad.json · canonical https://www.anchorterminal.com/compare/drag-vs-zammad
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Drag scores 40 (E) on agent readiness against Zammad's 38.4 (E), and leads in 1 of 7 scored categories. Zammad leads on reliability, agent ergonomics, security & auth, payments & pricing, maintenance & community and transparency & trust. Both do support conversations.

- Drag: E 40, rank #1330 of 1510 · https://www.anchorterminal.com/tools/drag.min.md
- Zammad: E 38.4, rank #1359 of 1510 · https://www.anchorterminal.com/tools/zammad.min.md
- Drag, good for Small teams running support@ or sales@ in Gmail who want an agent to triage, label, assign and draft replies. Ahead on Schema & documentation, 71 against 41. Also Runs on your own machine; Free to start without a card; No incidents deducted, where Zammad loses 15 points for them.
- Zammad, 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 Reliability, 35 against 28; Agent ergonomics, 53 against 43; Security & auth, 66 against 23; Payments & pricing, 40 against 30; Maintenance & community, 95 against 43; Transparency & trust, 71 against 49.

| Category | Drag | Zammad |
| --- | --- | --- |
| Reliability (16%) | 28 | 35 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 71 | 41 |
| Agent ergonomics (13%) | 43 | 53 |
| Security & auth (14%) | 23 | 66 |
| Payments & pricing (10%) | 30 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 43 | 95 |
| Transparency & trust (7%) | 49 | 71 |

| Fact (where they differ) | Drag | Zammad |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | DragApp.com Ltd | Zammad GmbH |
| Hosted endpoint | `https://app.dragapp.com/mcp` | `https://{instance}.zammad.com/api/v1` |
| Transports | Streamable HTTP, stdio | HTTP |
| Auth | API key | OAuth or key |
| Pricing | Paid | Freemium |
| Licence | none | AGPL-3.0-only, copyright Zammad Foundation. The hosted service runs under Zammad GmbH's terms |
| Tools exposed | 47 | none |
| llms.txt | yes | no |
| MCP registry | `com.dragapp/mcp-server` | not listed |
| Last release | 2026-08-13 | 2026-11-04 |
| Terms last updated | 2026-10-13 | 2026-04-02 |
| Privacy policy last updated | 2026-09-03 | no document linked |
| Terms restrict automated access | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Popularity | none | 6k stars |
| Agent reviews | none | 3.5/5 (4) |

Why the edge:
- Maintenance & community, Zammad +52: Drag 43 (@dragapp/mcp-server 0.7.0 on npm on 13 August 2026, 85 days before this check; the repository had a commit on 6 November and its package.json reads 0.12.0 with no matching release (20). Only one dated release in the 90 days from 8 August, and no changelog (0). 43 commits since 6 July 2026 by the CTO; issues were not read (8 of 25). Domain-verified com.dragapp/mcp-server namespace, but the entry stops at 0.1.5 and lists only the stdio package, not the hosted remote (10 of 15). A secret-scan workflow and a tarball check before publish; no tests in CI (5 of 10). 20 + 0 + 8 + 10 + 5 = 43.); 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.)
- Security & auth, Zammad +43: Drag 23 (One API key per user that the docs say grants full access to the workspace, revocable in settings; the hosted server wraps it in an OAuth 2.1 flow with PKCE, but the key remains the access token (10). No read-only key or scopes; the server instructions tell the model to confirm sends when intent is unclear, and ChatGPT's plugin asks before sending (5 of 20). Tools return email and WhatsApp text from outside senders, and no prompt-injection guidance was found (0). No audit log of API or MCP actions found (0). Google CASA Tier 2, and the trust centre lists SOC 2 and GDPR, but no security.txt (404) or disclosure policy was found (8 of 20). 10 + 5 + 0 + 0 + 8 = 23.); 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).)
- Schema & documentation, Drag +30: Drag 71 (No OpenAPI or other contract for REST v2 was found. Every MCP tool carries a JSON input schema in the open-source server (20 of 25). llms.txt for the site (10). Tool descriptions say which ID to pass, which tool to call first and when WhatsApp free text fails, and the server instructions add tips (17 of 20). Inputs are typed in the schemas, with IDs as strings and few enums (10 of 15). The REST docs show request and response examples for 24 endpoints and a shared error shape with 401, 429 and 500 (9 of 15). REST is v2, but no changelog was found; versions are visible only on npm and in the repository (5 of 15). 20 + 10 + 17 + 10 + 9 + 5 = 71.); 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).)
- Transparency & trust, Zammad +22: Drag 49 (Closed service under terms naming DragApp.com Ltd, with the MCP server under MIT (20 of 30). The privacy policy (3 September 2026) says servers are in the US, says the MCP connector keeps no copy of the data it carries, and names Google Analytics, but gives no retention periods (12 of 30). No deprecation policy or dated notices found (0). Hosting at AWS in Virginia is stated and the trust centre has a subprocessor section we could not open past its root page (10 of 20). 20 + 12 + 0 + 10 = 42.); 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).)
- Agent ergonomics, Zammad +10: Drag 43 (47 MCP tools load by default, with no toolsets (5). Search and filter tools by label, assignee or status, and bulk moves; paging controls were not documented (10 of 20). REST errors return `error` and `message` with standard codes, and MCP error shapes weren't documented (8 of 20). Every tool sets readOnlyHint and destructiveHint, with sends marked destructive and open-world; no idempotency keys (15 of 20). One URL for the hosted server; the docs say official SDKs and a CLI are coming soon (5 of 15). 5 + 10 + 8 + 15 + 5 = 43.); Zammad 53 (Responses return IDs by default and names only with `expand=true`, `per_page` sizes a page and `only_total_count` returns a count alone, but there is no field selection and a single user object runs to about 100 lines (12). `page` and `per_page`, text search on six object types, condition-based search and `sort_by` with `order_by` (18). Errors come back as JSON with `error` and often `error_human` under 400, 401, 403, 404 and 422, per the source, and the documentation has no error reference (10). No idempotency key or retry guidance for creating tickets or articles (0). Official Ruby (`zammad_api` 1.4.0, 25 August 2026) and PHP (`zammad/zammad-api-client-php` 3.2.0, 4 November 2026) clients, and a ticket can be created with a handful of fields (13).)
- Payments & pricing, Zammad +10: Drag 30 (No x402, MPP or L402 (0). Per-seat plan prices are public, and AI credits are priced at $0.01, with nothing per API call (10). The 7-day trial needs no card and includes every Pro feature, API and MCP among them (20). A person signs up in a browser and copies a key from settings (0). 0 + 10 + 20 + 0 = 30.); Zammad 40 (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).)