# Drag vs Pylon API + MCP (slim)

> Pylon scores 57.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/drag-vs-pylon.md (~4,900 tokens) · this version ~2,780 tokens · JSON https://www.anchorterminal.com/compare/drag-vs-pylon.json · canonical https://www.anchorterminal.com/compare/drag-vs-pylon
- 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)

Pylon API + MCP scores 57.6 (C) on agent readiness against Drag's 40 (E), and leads in 6 of 7 scored categories. Drag leads on payments & pricing. Both do support conversations.

- Drag: E 40, rank #1330 of 1510 · https://www.anchorterminal.com/tools/drag.min.md
- Pylon API + MCP: C 57.6, rank #787 of 1510 · https://www.anchorterminal.com/tools/pylon.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 Payments & pricing, 30 against 10. Also Runs on your own machine; Free to start without a card; Open source; No incidents deducted, where Pylon API + MCP loses 3 points for them.
- Pylon API + MCP, good for B2B support run in shared Slack or Teams channels, with an agent that triages, files and routes issues and maintains the knowledge base. Ahead on Reliability, 85 against 28; Schema & documentation, 78 against 71; Security & auth, 61 against 23; Maintenance & community, 62 against 43; Transparency & trust, 68 against 49.

| Category | Drag | Pylon API + MCP |
| --- | --- | --- |
| Reliability (16%) | 28 | 85 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 71 | 78 |
| Agent ergonomics (13%) | 43 | 47 |
| Security & auth (14%) | 23 | 61 |
| Payments & pricing (10%) | 30 | 10 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 43 | 62 |
| Transparency & trust (7%) | 49 | 68 |

| Fact (where they differ) | Drag | Pylon API + MCP |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | DragApp.com Ltd | Pylon |
| Hosted endpoint | `https://app.dragapp.com/mcp` | `https://api.usepylon.com` |
| Transports | Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Tools exposed | 47 | 103 |
| MCP registry | `com.dragapp/mcp-server` | not listed |
| Last release | 2026-08-13 | none |
| Terms last updated | 2026-10-13 | 2026-06-09 |
| Privacy policy last updated | 2026-09-03 | 2024-03-04 |
| Terms restrict automated access | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Agent reviews | none | 2/5 (2) |

Why the edge:
- Reliability, Pylon API + MCP +57: 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.); Pylon API + MCP 85 (incident.io status page with components including API, with history and a status feed (20). Incidents touching the API in the 90 days from 6 August are partial. On 6 October Dashboard, API and Triggers & Workflows showed degraded performance for 45 minutes (18:59 to 19:44 UTC), and on 12 October EU-hosted instances couldn't log in for about 7 minutes. Other incidents named only the Dashboard, Phones, Email, Analytics or Codebase. Read from the feed back to 17 August and the page itself (20). Rate limits are published per endpoint at 30, 120 or 300 requests a minute, shared across an organisation's tokens (15). The rate-limits page documents `Retry-After`, `X-Retry-After` and `X-Rate-Limit-Remaining` and says to wait at least `Retry-After` and add backoff with jitter. There's no safe-retry guidance or idempotency key for writes (10). The terms of service, last updated 9 June 2026, carry a Service Level Agreement as Exhibit B with 99.9 per cent monthly availability, missed on 1 October (10). The API is GA and the MCP page carries no beta label (10). 20+20+15+10+10+10 = 85.)
- Security & auth, Pylon API + MCP +38: 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.); Pylon API + MCP 61 (REST tokens are Bearer tokens that only Admins can create. A token can take its own role (editable on existing tokens since 31 August 2026), act as a user or bot, and carry an IP allowlist of up to 20 entries; tokens don't expire and there are no scopes beyond the role. The MCP server uses OAuth 2.0 through AuthKit as the signed-in user, who needs the MCP Access role (24). MCP can't see or write anything the user can't in the dashboard, and the docs say AI tools are told to show a reply and get approval before sending it. There's no read-only mode, and the 42 write tools include `delete_task`, `delete_feature_request`, `delete_tag` and `publish_article` (12). Issues carry customer-written Slack and email text and we found no injection guidance (0). An audit logs API endpoint and MCP tool, with 30 days of history below Enterprise, and token actions show under the token's name (13). The security page states SOC 2 Type II and ISO/IEC 27001:2022 with reports through the trust centre, annual penetration tests and a vulnerability disclosure policy (last updated 5 September 2025) with a reporting address and safe harbour but no response time. No bug bounty and no security.txt (404). Graded below Plain's 14 before its bounty was found, which adds a 48-hour acknowledgement and security.txt (12). 24+12+0+13+12 = 61.)
- Payments & pricing, Drag +20: 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.); Pylon API + MCP 10 (No x402, MPP or L402 (0). The pricing page now lists seat prices, Professional at $89 and Advanced at $139 a seat on an annual contract, both including the API and MCP server, with Enterprise on quote and AI credits priced through sales. Public plan-only pricing (10). The FAQ says free trials for prospects are set up by a sales representative, so no self-serve trial (0). A person books a demo and an Admin creates the token (0). 0+10+0+0 = 10.)
- Maintenance & community, Pylon API + MCP +19: 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.); Pylon API + MCP 62 (Changelog entry on 2 November 2026, 2 days before this check, with public API and MCP changes (30). Weekly dated entries, with API or MCP changes in every week from 10 August to 2 November (20). Weekly public changelog and support through the product, no public issue tracker (12). SDKs for TypeScript, Python and Go appeared on 11 October 2026, but every tag is an alpha pre-release (v0.1.0-alpha.5, v0.1.0a5, v0.1.0-alpha.3 on 27 October), so not counted as current releases (0). No released package to assess (0). 30+20+12+0+0 = 62.)
- Transparency & trust, Pylon API + MCP +19: 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.); Pylon API + MCP 68 (Closed service with published terms (15). The privacy policy is still dated 4 March 2024 and gives no retention periods. A public subprocessor list, current as of 22 September 2026, names each subprocessor's purpose and location, and the security page says customer data doesn't train models and AI providers are under zero data retention agreements (12). The MCP page lists combined tools with old names marked removed or hidden, without dates, and the errors page says codes are never renamed or repurposed. No deprecation policy or dated notice found (5). The subprocessor list covers data locations in the US and Germany or Europe per subprocessor, with EU-hosted workspaces (20). 15+12+5+20 = 52.)
- Schema & documentation, Pylon API + MCP +7: 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.); Pylon API + MCP 78 (Each API reference page embeds OpenAPI 3.0.3 objects, but there's no standalone spec file. The alpha SDKs are generated from a definition that isn't published (18). llms.txt with Markdown versions of every page (10). Reference pages describe each endpoint, and the MCP page labels all 103 tools read or write (13). Typed parameters and required fields in the embedded objects, and a conventions page on IDs, timestamps, filters and update behaviour (13). An errors page lists stable machine-readable codes by status with their meaning, alongside request examples (14). A weekly dated product changelog with API and MCP entries, and no API versioning (10). 18+10+13+13+14+10 = 78.)