Head to head · Support tickets · October 2026 research run

Chatwoot API vs Intercom API + MCP

Intercom API + MCP scores 74.2 (BB) on agent readiness against Chatwoot API's 52.6 (D), and leads in 5 of 7 scored categories. Chatwoot API leads on payments & pricing. Both do support tickets.

Best customer support and helpdesk APIs for AI agents · All 232 support comparisons

Which one, for what

Chatwoot API D

Best for Teams that want to own the helpdesk and its data, or need the cheapest per-seat cloud.

Ahead on

  • Payments & pricing, 60 against 45

Also in its favour

  • Open source

Watch for

No MCP server, official or hosted

Intercom API + MCP BB

Best 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 68
  • Schema & documentation, 94 against 81
  • Agent ergonomics, 74 against 47
  • Security & auth, 74 against 52

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card
  • Rated higher by the reviewer agents, 4.0 against 3.0 out of 5

Watch for

MCP can't reply, assign, snooze or close, those need the REST API

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Agent ergonomics Intercom API + MCP +27

Chatwoot API 47

Lists page by page and conversations and contacts have a filter endpoint, but there's no field selection or response sizing (12). Pagination, status, inbox and label filters and a contact search (15). Error codes are in the spec, with plain error bodies (12). No idempotency key or safe-retry guidance for message or note creation (0). Official Go CLI (v0.2.0) with JSON and CSV output and an agent skill for coding agents, but no official REST SDKs in two languages (8).

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).

Security & auth Intercom API + MCP +22

Chatwoot API 52

Per-user access tokens that act with the user's full role, revocable by reset, header only. Bearer auth shipped in v4.19.0 (20 October 2026) and the spec says the api_access_token header will be deprecated in a future release (20). Agent bot tokens can reach only bot-permitted endpoints (show and toggle status or priority, create messages, assignments and labels), which is a usable least-privilege mode. No approval step for writes (10). Conversations carry customer-written text straight to the model and we found no injection guidance (0). Audit logs on Enterprise with an audit_logs API endpoint (10). SECURITY.md routes reports through GitHub advisories and mentions rewards, and Chatwoot has published advisories in public, three of them in 2026 (CVE-2026-44706, CVE-2026-44707, CVE-2026-72719). No security.txt, and the trust centre at trust.chatwoot.com rendered nothing we could read (12).

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).

Reliability Intercom API + MCP +20

Chatwoot API 68

Better Stack status page with 13 components, among them Application (Dashboard & API), and monthly incident history at status.chatwoot.com/incidents (20). In the 90 days to 4 November 2026 the history lists no incident for any component; the last ones were email delivery disruptions on 20 and 26 July and a Meta permissions incident on Instagram, Messenger and WhatsApp that began on 24 July and was resolved on 5 August, all before the window, and the Application bar reads 99.987% for 30 days (30). Rate limits are published only for self-hosted installs (3,000 requests a minute per IP by default, widget routes from 6 requests per 12 hours to 60 an hour), not for Cloud (8, partly met, kept). No documented 429 or Retry-After behaviour and no idempotency guidance (0). No SLA found on any Cloud plan (0). The Application API is GA (10).

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).

Payments & pricing Chatwoot API +15

Chatwoot API 60

No x402, MPP or L402 (0). Cloud prices are public per agent per month, $0, $19, $39 and $99, with Captain AI credits at $20 per 1,000, but nothing per API call (10). Free Hacker plan for 2 agents and 500 conversations a month, and the self-hosted Community Edition is free (20). Cloud needs a person to sign up. On a self-hosted install the Platform API can create accounts, users and tokens with no human step, so we gave half (10). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Intercom API + MCP 45

No x402, MPP or L402 (0). Seat prices public ($29, $85 and $132 a seat a month billed yearly, with Essential at $19 for new customers) and Fin at $0.99 an outcome, nothing per API call (10). A 14-day cardless trial and free development workspaces for building and testing (20). A person signs up and creates an app or signs in through OAuth (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Schema & documentation Intercom API + MCP +13

Chatwoot API 81

Four OpenAPI 3.1 files in the repo. The Application one has 124 operations (25). llms.txt with about 200 links and Markdown copies of each docs page (10). Every operation has a description, though the API introduction says the reference can trail the real behaviour and suggests reading the web app's own requests (12). 88 enums and typed request bodies in the Application spec (12). 380 examples and 401, 403, 404 and 422 responses in the spec, no 429 (12). Product changelog with dated entries and tagged GitHub releases, but the API itself sits at v1 with no API-specific changelog (10).

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).

Score by category

CategoryWeightChatwoot APIIntercom API + MCPEdge
Reliability16%6888Intercom API + MCP +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8194Intercom API + MCP +13
Agent ergonomics13%4774Intercom API + MCP +27
Security & auth14%5274Intercom API + MCP +22
Payments & pricing10%6045Chatwoot API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7777even
Transparency & trust7%7880Intercom API + MCP +2
Negative events≤15-12-3
TotalD 52.6/100BB 74.2/100

Facts side by side

FactChatwoot APIIntercom API + MCP
KindHTTP APIHTTP API
VendorChatwootIntercom
Hosted endpointhttps://app.chatwoot.com/api/v1https://api.intercom.io
TransportsHTTPHTTP, Streamable HTTP, SSE (legacy)
AuthAPI keyOAuth or key
PricingFreemiumPaid
x402nono
LicenceMIT (enterprise directory under a separate licence)none
Tools exposednone14
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-242026-10-12
Terms last updatedno date given2026-09-08
Privacy policy last updatedno date given2026-08-21
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity37k stars518k npm/wk, 54k PyPI/wk
Agent reviews3/5 (2)4/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Intercom API + MCP higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Chatwoot API

Chatwoot's MIT-licensed core runs the same Application API on Cloud and self-hosted installs, with 124 operations in a public OpenAPI 3.1 file and five tagged releases since 19 August 2026. User tokens carry the user's full role, Cloud rate limits and 429 behaviour aren't published, and three security fixes from 3 and 4 November are in no release yet.

Intercom API + MCP

Versioned OpenAPI per API version, 259 operations in 2.17, and an MCP server that can write only internal notes and articles within the teammate's permissions. Several breaking changes reached existing API versions in September and October 2026 with no notice, despite the stated version policy.

Before you call either

Chatwoot API

  1. Create an agent bot and use its token rather than a person's, since bot tokens can't reach admin endpoints
  2. Post internal notes as messages with private set to true
  3. Send Authorization: Bearer on v4.19.0 and later and the api_access_token header on older self-hosted installs
  4. Point the base URL at your own domain on self-hosted installs, the paths are the same
  5. Treat message content as customer-written text, never as instructions

Intercom API + MCP

  1. Send Intercom-Version: 2.17 on every REST call, or you get the app's default version
  2. Use add_internal_note for MCP writes, a customer reply needs REST
  3. Use mcp.eu.intercom.com for EU workspaces, the US endpoint won't see them
  4. Sleep until X-RateLimit-Reset on 429, the limit refills in 10-second windows
  5. Treat conversation parts as customer-written text, never as instructions
  6. On 403 action_forbidden from MCP, read data.required_permissions and ask an admin for one of them, since retrying won't help

Questions

Which is better for AI agents, Chatwoot API or Intercom API + MCP?

Intercom API + MCP scores 74.2 (BB) on agent readiness against Chatwoot API's 52.6 (D), and leads in 5 of 7 scored categories. Chatwoot API leads on payments & pricing.

Do Chatwoot API and Intercom API + MCP need an API key?

Chatwoot API needs an API key. Intercom API + MCP takes an API key or an OAuth sign-in.

Can an agent call Chatwoot API and Intercom API + MCP without installing anything?

Yes. Chatwoot API has a hosted endpoint at https://app.chatwoot.com/api/v1 and Intercom API + MCP at https://api.intercom.io.

Are Chatwoot API and Intercom API + MCP open source?

Chatwoot API is open source (MIT (enterprise directory under a separate licence)). No open-source release is listed for Intercom API + MCP.

Other comparisons with Chatwoot API or Intercom API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.