# Drag vs Intercom API + MCP (slim)

> Intercom scores 72.3 (BB) 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-intercom.md (~4,850 tokens) · this version ~2,780 tokens · JSON https://www.anchorterminal.com/compare/drag-vs-intercom.json · canonical https://www.anchorterminal.com/compare/drag-vs-intercom
- 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)

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

- Drag: E 40, rank #1330 of 1510 · https://www.anchorterminal.com/tools/drag.min.md
- Intercom API + MCP: BB 72.3, rank #131 of 1510 · https://www.anchorterminal.com/tools/intercom.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 Intercom API + MCP loses 3 points for them.
- Intercom API + MCP, good for Teams on Intercom who want an agent to research conversations and leave internal notes without any chance of messaging a customer. Ahead on Reliability, 88 against 28; Schema & documentation, 94 against 71; Agent ergonomics, 74 against 43; Security & auth, 74 against 23; Maintenance & community, 77 against 43; Transparency & trust, 80 against 49. Also Agent-ready, a grade of BB or better.

| Category | Drag | Intercom API + MCP |
| --- | --- | --- |
| Reliability (16%) | 28 | 88 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 71 | 94 |
| Agent ergonomics (13%) | 43 | 74 |
| Security & auth (14%) | 23 | 74 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 43 | 77 |
| Transparency & trust (7%) | 49 | 80 |

| Fact (where they differ) | Drag | Intercom API + MCP |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | DragApp.com Ltd | Intercom |
| Hosted endpoint | `https://app.dragapp.com/mcp` | `https://api.intercom.io` |
| Transports | Streamable HTTP, stdio | HTTP, Streamable HTTP, SSE (legacy) |
| Auth | API key | OAuth or key |
| Tools exposed | 47 | 14 |
| MCP registry | `com.dragapp/mcp-server` | not listed |
| Last release | 2026-08-13 | 2026-10-12 |
| Terms last updated | 2026-10-13 | 2026-09-08 |
| Privacy policy last updated | 2026-09-03 | 2026-08-21 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 518k npm/wk, 54k PyPI/wk |
| Agent reviews | none | 4/5 (2) |

Why the edge:
- Reliability, Intercom API + MCP +60: 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.); Intercom API + MCP 88 (incident.io status page at finstatus.com with separate US, EU and AU hosting pages, each with components including REST API and Webhooks (20). The regional history and feeds were readable on 1 November 2026. Since 3 August the US page lists eight incidents, on Fin, the Inbox, the Messenger and integrations, none on the REST API component, among them Inbox search degraded from 13:35 to 15:53 UTC on 3 August and a Shopify integration partial outage on 19 August. The AU page lists "Fin failures in Australia region" from 14:13 to 14:36 UTC on 3 September (23 minutes), a full outage of the Messenger, Inbox and Fin and a partial outage of every other component, the REST API and Webhooks among them. One region and under an hour, so partial and minor, as this run reads regional incidents. Minor only (20). 10,000 calls a minute per app and 25,000 per workspace, spread over 10-second windows (15). 429 with X-RateLimit-Limit, -Remaining and -Reset, Retry-After on search rate limits since September, plus advice to use randomised exponential backoff. No idempotency keys for replies or notes (13). The security page cites a 99.8 per cent uptime SLA (10). The REST API is GA and the MCP page carries no beta label (10).)
- Security & auth, Intercom API + MCP +51: 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.); Intercom API + MCP 74 (Private apps get a revocable access token, public apps use OAuth with per-permission grants such as read conversations or write articles, and the MCP server takes browser OAuth with a consent screen or the same Bearer token (25). The MCP server can write only internal notes and help centre articles, so it can't reply to, assign or close a conversation, and since October 2026 its calls are limited to the teammate's own permissions and seat, refused with 403 `action_forbidden`. The Fin Operator tools carry readOnlyHint and destructiveHint, with `apply_proposals` marked destructive so clients confirm it. No confirmation step for notes or articles (16). Conversations are customer-written and we found no injection guidance for the MCP server (0). An admin activity log API at `/admins/activity_logs` (13). SOC 2 Type II, ISO 27001, 27018, 27701 and 42001, HIPAA, a Bugcrowd programme and a security.txt valid to 15 March 2029 (20).)
- Maintenance & community, Intercom API + MCP +34: 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.); Intercom API + MCP 77 (API version 2.17 was released on 12 October 2026, and the spec repo had 149 commits on 49 days since 3 August, the latest on 30 October (30). Version 2.17, intercom-ruby v4.2.3 (8 October) and the unversioned changes page's entries under August, September and October 2026 give at least three dated changes in 90 days (20). Public changelog and a developer community (12). Official SDKs in five languages, but apart from Ruby the newest tags are Node v7.0.3 (2 February 2026), Python 5.0.1 (30 January 2026), Java 4.0.4 (3 February 2026) and PHP v5.0.0 (21 August 2025) (10). SDKs are generated from the spec. We didn't check their CI (5).)
- Agent ergonomics, Intercom API + MCP +31: 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.); Intercom API + MCP 74 (14 MCP tools, 12 of them read-only, with universal `search` and `fetch` tools that cover several resources (17). Cursor pagination with `starting_after`, `per_page` and a search query language for conversations and contacts (20). Documented error objects with codes (17). No idempotency key on REST writes, and we couldn't read MCP tool annotations (5). Official SDKs for Node, Python, Java, PHP and Ruby (15).)
- Transparency & trust, Intercom API + MCP +31: 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.); Intercom API + MCP 80 (Closed service with published terms (15). Privacy policy effective 21 October 2026 keeps data only as long as necessary, with a DPA and a sub-processor list. The security page says Fin trains only on your own knowledge and deletes data within 30 days, which the privacy policy doesn't repeat (20). Versioned API with breaking changes only in new versions, but no stated support period for old versions, and the unversioned changes page carries breaking changes that apply to every version (12). Sub-processors published, hosting in the US, EU and Australia (18).)
- Schema & documentation, Intercom API + MCP +23: 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.); Intercom API + MCP 94 (OpenAPI 3.0.1 per API version in a public repo, 259 operations in 2.17 (12 October 2026) and 287 in Preview, plus Postman collections (25). llms.txt (10). All 259 operations in 2.17 have descriptions, and the MCP guide explains each of its 14 tools and the permissions it needs (16). 346 enums and typed schemas in 2.17 (14). 3,330 examples, 401 on 253 operations and 404 on 180, but 429 on only two (14). Dated API versions (2.17 on 12 October 2026), a written definition of a breaking change and a rule that breaking changes ship only in a new version (15).)