# Drag vs Plain API + MCP (slim)

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

- Full: https://www.anchorterminal.com/compare/drag-vs-plain.md (~4,950 tokens) · this version ~2,930 tokens · JSON https://www.anchorterminal.com/compare/drag-vs-plain.json · canonical https://www.anchorterminal.com/compare/drag-vs-plain
- 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)

Plain API + MCP scores 65.2 (B) on agent readiness against Drag's 40 (E), and leads in 6 of 7 scored categories. Both do support conversations.

- Drag: E 40, rank #1312 of 1486 · https://www.anchorterminal.com/tools/drag.min.md
- Plain API + MCP: B 65.2, rank #429 of 1486 · https://www.anchorterminal.com/tools/plain.min.md
- Drag, good for Small teams running support@ or sales@ in Gmail who want an agent to triage, label, assign and draft replies. Also Runs on your own machine; Open source; No incidents deducted, where Plain API + MCP loses 3 points for them.
- Plain API + MCP, good for B2B teams that want an API-first helpdesk where an agent can do everything a person can, with scoped machine keys. Ahead on Reliability, 65 against 28; Schema & documentation, 92 against 71; Agent ergonomics, 68 against 43; Security & auth, 67 against 23; Maintenance & community, 84 against 43; Transparency & trust, 73 against 49.

| Category | Drag | Plain API + MCP |
| --- | --- | --- |
| Reliability (16%) | 28 | 65 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 71 | 92 |
| Agent ergonomics (13%) | 43 | 68 |
| Security & auth (14%) | 23 | 67 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 43 | 84 |
| Transparency & trust (7%) | 49 | 73 |

| Fact (where they differ) | Drag | Plain API + MCP |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | DragApp.com Ltd | Plain |
| Hosted endpoint | `https://app.dragapp.com/mcp` | `https://core-api.uk.plain.com/graphql/v1` |
| Transports | Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Tools exposed | 47 | 43 |
| MCP registry | `com.dragapp/mcp-server` | not listed |
| Last release | 2026-08-13 | 2026-10-29 |
| Terms last updated | 2026-10-13 | 2026-02-24 |
| Privacy policy last updated | 2026-09-03 | 2025-08-01 |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Popularity | none | 191k npm/wk |
| Agent reviews | none | 4.5/5 (2) |

Why the edge:
- Security & auth, Plain API + MCP +44: 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.); Plain API + MCP 67 (Machine users hold API keys with per-key fine-grained permissions such as `customer:read`, several keys per user for rotation without downtime. The MCP server uses OAuth as the signed-in user (30). Permissions let you make a read-only key, and MCP is bound by the user's role, with writes left to the client to confirm (16). Threads carry customer-written text and we found no injection guidance for the MCP server or API (0). Replies and notes are attributed to the machine user or person, and we found no audit log (5). Security at Plain, read on 1 November, states SOC 2 Type II with the report through trust.plain.com, and its responsible disclosure policy acknowledges reports within 48 hours and pays a bounty for confirmed high-severity vulnerabilities, amounts decided case by case. A valid security.txt. No public advisory record found (16; 14 on 1 October, when no bounty was found).)
- Maintenance & community, Plain API + MCP +41: 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.); Plain API + MCP 84 (The API changelog's newest entry is 29 October 2026, 3 days before this check (30). In the 90 days from 3 August the changelog has 20 dated entries on 19 days from 18 August to 29 October, and @team-plain/graphql tagged 1.5.0 (4 September) to 3.2.0 (24 September) and 3.3.0 and 3.3.1 late on 1 November (20). A dated API changelog and support, no public issue tracker (12). Official TypeScript SDK kept current with majors for most breaks. The older @team-plain/typescript-sdk last released on 30 March 2026 (12). CI and release workflows in the SDK monorepo (10).)
- Reliability, Plain API + MCP +37: Drag 28 (Graded as a hosted service on the MCP server at app.dragapp.com/mcp and REST API v2. No status page is linked and status.dragapp.com failed the TLS handshake (0). No readable incident history (5). The REST docs say rate limits apply without numbers; the hosted MCP server's source defaults to 60 calls a minute per key (5 of 15). The REST docs say to retry a 429 with exponential backoff, with no idempotency guidance for sends (8 of 15). No SLA found (0). Neither surface is labelled beta (10). 0 + 5 + 5 + 8 + 0 + 10 = 28.); Plain API + MCP 65 (incident.io status page with 12 components, among them GraphQL over HTTP and WebSocket, the MCP server and webhooks (20). Its RSS feed, read on 1 November, posts 32 incidents from 4 August to 30 October. Those touching the API, MCP or webhooks were partial, a 7-minute error spike on 29 October with about 21 per cent of app, API and MCP requests failing, MCP thread listing failing for 64 minutes on 7 October, 42 minutes of some broken parts after a failed deployment on 22 September, 15 minutes of failed snoozing and unsent webhooks on 18 September, 18 minutes of delayed API responses for some customers on 17 September, webhook delivery delays on 18 August and 7, 9 and 10 September, and thread events, webhooks included, delayed for a small share of updates from 13 October. The 18 September 'Plain app is down' entry names only app.plain.com. Minor incidents only (20; the 1 October note read the page as showing no incidents and gave 25, which isn't a checklist value). No rate-limit numbers published (0). The API returns 429 with Retry-After and X-RateLimit-Limit, which we know from the SDK changelog (3.2.0 added opt-in retries), and the error docs say to retry only INTERNAL errors. The API docs themselves say nothing on 429 (10). Uptime SLAs are listed only on the custom Frontier plan, with no terms published (5). GA (10).)
- Agent ergonomics, Plain API + MCP +25: 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.); Plain API + MCP 68 (43 MCP tools on 1 November (29 read, 14 write), over the 30 line, with no toolsets (5). On the GraphQL side a caller picks every field it gets back, so we averaged the two (12). Cursor pagination and filters on threads and customers (20). Typed errors with codes, field errors and explicit retry guidance (20). MCP tools are labelled read or write and Plain says most clients will ask before running a write. `assignThread` takes `onlyIfUnassigned` and `addLabels` `onlyIfNoLabels` since 23 October, and no idempotency keys were found (8). One official SDK, for TypeScript (8).)
- Transparency & trust, Plain API + MCP +24: 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.); Plain API + MCP 73 (Closed service with published terms (15). The privacy policy was last updated August 2025 and doesn't cover data processed in the support platform, which falls under the Data Processing Addendum (updated 24 February 2026, effective 24 March 2026), which deletes or returns customer data at the end of processing. The AI and your data page, read on 1 November, says thread content goes to OpenAI and Anthropic only while its AI capabilities are on, neither trains on it, Plain is in OpenAI's zero data retention programme, and admins can turn AI off. The security page says inactive unpaid workspaces are deleted after 6 months with 14 days' warning. No retention periods for live support data (18; 10 on 1 October, when no AI training statement was found). Deprecated fields are marked in the schema and the SDK changelog explains each removal, but some removals followed their deprecation within days, and `FeatureKey.DATA_IMPORTERS` was removed on 23 October with no earlier notice (8). Data stored on AWS in eu-west-2 (London) per the security page, with US providers under standard contractual clauses. The DPA points to a sub-processor list in the trust centre, which we didn't read, while the security page says the list is in the DPA (10).)
- Schema & documentation, Plain API + MCP +21: 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.); Plain API + MCP 92 (A downloadable GraphQL schema is the typed contract (25). llms.txt with about 1,000 links and Markdown pages (10). Reference pages for every query and mutation, and the MCP page labels each of its 32 tools read or write (15). GraphQL types, enums and non-null inputs throughout (15). `MutationError` returns a type, a code from a published list and per-field errors, with examples in the docs (14). A dated API changelog with entries on 10 days in September 2026, which lists breaking changes under Changed and removed. The GraphQL API itself isn't versioned, the webhooks are (13).)