# Chatway MCP vs Drag (slim)

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

- Full: https://www.anchorterminal.com/compare/chatway-mcp-vs-drag.md (~5,450 tokens) · this version ~3,330 tokens · JSON https://www.anchorterminal.com/compare/chatway-mcp-vs-drag.json · canonical https://www.anchorterminal.com/compare/chatway-mcp-vs-drag
- 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)

Chatway MCP scores 58.6 (C) on agent readiness against Drag's 40 (E), and leads in 5 of 7 scored categories. Drag leads on schema & documentation. Both do support conversations.

- Chatway MCP: C 58.6, rank #740 of 1510 · https://www.anchorterminal.com/tools/chatway-mcp.min.md
- Drag: E 40, rank #1330 of 1510 · https://www.anchorterminal.com/tools/drag.min.md
- Chatway MCP, good for A small support team on Chatway that wants an assistant to triage, summarise, tag, note and draft or send replies on demand. Ahead on Reliability, 40 against 28; Agent ergonomics, 76 against 43; Security & auth, 70 against 23; Maintenance & community, 78 against 43; Transparency & trust, 57 against 49.
- 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 64. Also Runs on your own machine; Open source.

| Category | Chatway MCP | Drag |
| --- | --- | --- |
| Reliability (16%) | 40 | 28 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 64 | 71 |
| Agent ergonomics (13%) | 76 | 43 |
| Security & auth (14%) | 70 | 23 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 78 | 43 |
| Transparency & trust (7%) | 57 | 49 |

| Fact (where they differ) | Chatway MCP | Drag |
| --- | --- | --- |
| Vendor | Chatway (Poptin Ltd) | DragApp.com Ltd |
| Hosted endpoint | `https://mcp.chatway.app/mcp` | `https://app.dragapp.com/mcp` |
| Transports | Streamable HTTP | Streamable HTTP, stdio |
| Auth | OAuth | API key |
| Pricing | Freemium | Paid |
| Licence | Proprietary hosted service under Chatway's Terms of Use (Poptin Ltd). The GitHub repository holds only listing metadata and client manifests, under MIT | none |
| Tools exposed | 23 | 47 |
| Read-only variant documented | yes | no |
| MCP registry | `io.github.Chatway-app/chatway` | `com.dragapp/mcp-server` |
| Last release | 2026-10-26 | 2026-08-13 |
| Terms last updated | no date given | 2026-10-13 |
| Privacy policy last updated | 2026-10-06 | 2026-09-03 |
| Terms restrict automated access | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Agent reviews | 3.3/5 (4) | none |

Why the edge:
- Security & auth, Chatway MCP +47: Chatway MCP 70 (OAuth 2.1 with PKCE, dynamic client registration and one scope, `mcp:use`, with 18 permissions, widget and channel scoping and immediate revocation per connection. Roles bound it again, and tokens stop working when their user leaves the team (28 of 30). A connection can be read-only and members can't connect. The README of 4 November (commit 4591c85) says only resolving, reopening or assigning more than one conversation needs a confirmation token, and other actions, single resolves, tag and custom-data removals and send-message included, run straight away. On 17 October five tools needed the token (14 of 20, from 16). Tools return visitor-written text. The Gemini extension, Cursor rule and llms-install.md tell the model to treat it as untrusted data, but the developer docs don't (8 of 15). Per-connection audit log of tools called, targets and times, kept after disconnect, and writes attributed to a named agent (13 of 15). SECURITY.md is a disclosure policy asking for private reports through live chat, with no acknowledgement time, which this run scores 7 (7 of 20, from 5). No security.txt on chatway.app or mcp.chatway.app on 17 October, and no bug bounty, SOC 2 or ISO 27001 found. Total 70.); 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.)
- Maintenance & community, Chatway MCP +35: Chatway MCP 78 (The repository's newest tag, v1.2.2, is dated 26 October 2026, and v1.2.0 the same day changed the five Agent Skills and added Claude and Grok Build plugins (30 of 30). In the last 90 days the tags run v1.0.0 to v1.0.3 (12 and 13 October), v1.1.0 (20 October, five new Agent Skills), v1.2.0, v1.2.1 and v1.2.2 (26 October). v1.1.0 and v1.2.0 change skill content and count in full; the 1.0.x manifest versions and the icon and plugin-file bumps of 1.2.1 and 1.2.2 count half, 5 in all (20 of 20, from 10). An installation skill and two installation tools landed on main on 2 November with no tag. Closed service with dated product posts on the blog and support by live chat. Its merged pull requests, up to #26 on 4 November, come from the maintainer's own develop branch, and its issues couldn't be read (8 of 15). In the official MCP registry under io.github.Chatway-app, published by GitHub OIDC from the organisation's repository on each version tag, per the 17 October registry reading (15 of 15). Validate and publish workflows pin mcp-publisher by SHA-256. There is no package to assess (5 of 10). Total 78.); 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.)
- Agent ergonomics, Chatway MCP +33: Chatway MCP 76 (23 tools (21 in the 17 October tool reference plus the two installation tools in the README of 2 November) sits in the 11 to 30 band (15). Only tools for granted permissions are published, so a connection can expose a read-only subset (7 of 10 back). Definition sizes couldn't be measured without a token. Total 22 of 25. list-conversations pages with page and per_page up to 100 and a status filter, list-conversation-messages pages by cursor with limit up to 100 and hides system and internal messages by default, searches cap at 50 and return a lighter shape (18 of 20). Errors are documented per tool, the troubleshooting table maps symptoms to fixes, and an ambiguous agent_query returns candidates rather than guessing (16 of 20). readOnlyHint and destructiveHint are documented, but no tool is idempotent and there are no idempotency keys. Since the README change of 4 November only bulk resolve, unresolve and assign calls return a confirmation token (12 of 20). Defaults stated and few required parameters, setup guides for 14 clients, no official SDK (8 of 15). Docs readings are per the 17 October check, not re-read on 4 November. Total 76.); 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.)
- Reliability, Chatway MCP +12: Chatway MCP 40 (Graded with the hosted lines. No status page found, linked or at status.chatway.app, which did not resolve on 17 October (0 of 20). So there is no readable incident history (5 of 30). MCP is limited to 120 requests a minute per connection, counted separately for each (15 of 15). Over the limit the server returns 429 and the docs say to retry after a short pause, without a Retry-After figure for MCP, and they warn that a repeated call does the work twice. That is retry guidance alone, which this run scores 10 (10 of 15). No SLA, and the terms of 6 October 2026, re-read on 4 November, say the service may be unavailable through planned or unplanned downtime and that Chatway isn't liable for it (0 of 10). Live since 12 October 2026 with no beta or preview label (10 of 10). The docs host and the main site are paused for this run under the terms, so the rate-limit and status readings are per the 17 October check, not re-read on 4 November. Total 40.); 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.)
- Transparency & trust, Chatway MCP +8: Chatway MCP 57 (Closed hosted service under Terms of Use of 6 October 2026 naming Poptin Ltd, with a clause on MCP connections (re-read on 4 November). The repository is MIT but holds only manifests, skills and plugin files (15 of 30). Privacy Policy of 6 October 2026 and a GDPR page say visitor conversations aren't used to train public or shared AI models and that retention settings are the customer's. The DPA is sent only on request by email, and no retention periods for MCP audit logs or tokens were found (16 of 30). No deprecation policy. The terms let Chatway change or discontinue parts of the service at any time with a notice on the website (5 of 20). The GDPR page names Stripe, AWS, Google, Facebook, Elastic Email, Cloudflare and Profitwell as tools it uses, and the privacy policy says data may go to servers in various countries without naming regions (8 of 20). Privacy and GDPR readings are per the 17 October check, not re-read on 4 November. Total 44.); 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.)
- Schema & documentation, Drag +7: Chatway MCP 64 (The tool definitions are only served after OAuth, so the served JSON Schemas couldn't be read. The tool reference gave a typed parameter table for all 21 tools on 17 October, with required fields and ranges, and the repository README (2 November) adds get-installation-code and get-installation-status with their parameters and return fields. 15 of 25 for a documented, unverified contract. developers.chatway.app/llms.txt covered the REST API and webhooks but not MCP on 17 October. The repository's llms-install.md covers MCP setup (6 of 10). The reference says when to call several tools (list-conversations before reading messages, agent_query before list-agents, one resolve call with all IDs) and gives four common workflows (14 of 20). Enums for status, UUID identifiers, page, limit and length bounds, and no free-form objects (13 of 15). Per-tool error messages, the confirmation payload and a troubleshooting table for 401, 403 insufficient_scope, 405 and 429, but no request or response examples for tools (11 of 15). Registry versions run from 1.0.0 to 1.2.2 (26 October), but the server has no changelog, only blog posts and commit messages (5 of 15). Docs readings are per the 17 October check, not re-read on 4 November. Total 64.); 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.)