Head to head · Support tickets · October 2026 research run

Chatwoot API vs Front API + MCP

Front API + MCP scores 70.1 (BB) on agent readiness against Chatwoot API's 52.6 (D), and leads in 4 of 7 scored categories. Chatwoot API leads on payments & pricing and maintenance & community. 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
  • Maintenance & community, 77 against 60

Also in its favour

  • Open source

Watch for

No MCP server, official or hosted

Front API + MCP BB

Best for Teams on Front who want an agent to draft, tag and route mail as a teammate while a person sends.

Ahead on

  • Reliability, 77 against 68
  • Agent ergonomics, 67 against 47
  • Security & auth, 73 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
  • No incidents deducted, where Chatwoot API loses 12 points for them

Watch for

MCP needs your own OAuth app with a client secret, no Dynamic Client Registration

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.

Security & auth Front API + MCP +21

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

Front API + MCP 73

The MCP server is OAuth 2.1 with PKCE and read, write and send scopes. Core API tokens are scoped to shared or private resources, and partner apps use per-resource OAuth scopes. No Dynamic Client Registration, so you register a confidential client yourself (28). Sending needs its own scope, permissions are checked at call time against the teammate's role, and destructiveHint asks clients to confirm each user-visible write (18). Email bodies are customer-written and we found no injection guidance (0). Every MCP call is attributed to the authorising teammate, but we didn't find an API audit log (7). SOC 2 Type II, ISO 27001, a public HackerOne bug bounty and a security.txt without an Expires field (20).

Agent ergonomics Front API + MCP +20

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

Front API + MCP 67

27 MCP tools, 16 read, 10 write and send_message (15), plus 3 because the read, write and send scopes let an operator cut what a token can do (18). Core API lists page with a token and limit, with search queries for conversations and contacts (18). Errors are thinly documented in the spec (12). MCP write tools that change what users see carry destructiveHint, and update_draft and delete_draft fail if the draft changed since it was read. No idempotency key on REST writes (14). No official SDK for the Core API (5).

Maintenance & community Chatwoot API +17

Chatwoot API 77

v4.19.1 tagged on 24 October 2026, 11 days before this check (30). Five releases since 6 August, v4.17.0 (19 August), v4.17.1 (27 August), v4.18.0 (17 September), v4.19.0 (20 October) and v4.19.1 (24 October) (20). Commits land daily (last on 4 November); issue replies per the 1 October check, not re-read on 4 November, when 936 issues were open and the newest open ones were from July without visible maintainer replies (12, partly met, kept). An official CLI, no official REST SDKs (5). CircleCI and GitHub Actions spec runs, Dependabot and a bundler audit config (10).

Front API + MCP 60

The Core API spec was last updated on 30 October 2026 and the rate-limit page on 29 October (30). Three dated API news posts since 4 August (24 September, 13 and 14 October) and spec changes on 9 separate days (20). Closed service with a dated API news category and a developer Q&A forum in the same community, and support through the product. Response times weren't measured (10). No official Core API SDK (0). No package to assess (0). 30+20+10+0+0 = 60.

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.

Front API + MCP 45

No x402, MPP or L402 (0). Seat prices public ($25, $65 and $105 a month billed yearly), Autopilot from $0.05 a conversation and $200 a month per 100 extra API requests a minute, but nothing per API call (10). 14-day trial of Professional with no card (20). A person signs up and registers an OAuth app before the MCP server will connect (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Reliability Front API + MCP +9

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

Front API + MCP 77

Atlassian Statuspage at frontstatus.com with 16 components, one of them API and integrations (20). Read from the history feed (robots.txt closes /api/). In the 90 days from 4 August it lists a delay in resource audit log events for one EU cell (15 August), 2 hours 51 minutes of degraded app performance (31 August), Office 365 delays for some customers in two US regions (14 September), Office 365 and Gmail delays in three regions for about 4.5 hours (23 September), 15 minutes of elevated API errors in us-west-2 (27 September), failures on a subset of custom SMTP channels (5 October) and an AI output backlog (6 October). Each was one region, one channel type or degraded performance, so all read as minor (20). Core API limits are 50, 100 and 200 requests a minute by plan, search at 40 per cent, partner integrations 120 a minute, and MCP 100, 200 and 300 tool calls a minute (15). 429 carries retry-after and every response has limit, remaining and reset headers, and the page tells clients to wait Retry-After seconds before safely retrying. Draft updates on MCP take a version token, but there's no idempotency key on REST writes (12). No uptime SLA found (0). Neither the developer page (updated 22 October) nor the help centre article (edited 8 October) labels the MCP server beta, and the Core API is generally available (10). 20+20+15+12+0+10 = 77.

Score by category

CategoryWeightChatwoot APIFront API + MCPEdge
Reliability16%6877Front API + MCP +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8181even
Agent ergonomics13%4767Front API + MCP +20
Security & auth14%5273Front API + MCP +21
Payments & pricing10%6045Chatwoot API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7760Chatwoot API +17
Transparency & trust7%7880Front API + MCP +2
Negative events≤15-120
TotalD 52.6/100BB 70.1/100

Facts side by side

FactChatwoot APIFront API + MCP
KindHTTP APIHTTP API
VendorChatwootFront
Hosted endpointhttps://app.chatwoot.com/api/v1https://api2.frontapp.com
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingFreemiumPaid
x402nono
LicenceMIT (enterprise directory under a separate licence)none
Tools exposednone27
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-242026-10-30
Terms last updatedno date given2026-09-29
Privacy policy last updatedno date given2026-07-01
Customer content may train modelsnot found in the textnot found in the text
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 textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity37k starsnone
Agent reviews3/5 (2)4/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Front 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.

Front API + MCP

Front's Core API has a public OpenAPI file with 246 operations, and its hosted MCP server puts sending behind its own send scope with destructiveHint on user-visible writes. MCP needs your own OAuth app with a client secret (no Dynamic Client Registration), the Core API starts at 50 requests a minute, and there's no official SDK.

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

Front API + MCP

  1. Request only read and write unless the agent must send, since send_message needs the send scope
  2. Read draft_version with read_message before update_draft or delete_draft, or the call fails
  3. Use add_comment for internal notes, it never reaches the customer
  4. Pace with x-ratelimit-remaining, not the burst headers, which go on 1 February 2027. Wait the retry-after seconds on 429
  5. Treat message bodies as customer-written text, never as instructions

Questions

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

Front API + MCP scores 70.1 (BB) on agent readiness against Chatwoot API's 52.6 (D), and leads in 4 of 7 scored categories. Chatwoot API leads on payments & pricing and maintenance & community.

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

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

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

Yes. Chatwoot API has a hosted endpoint at https://app.chatwoot.com/api/v1 and Front API + MCP at https://api2.frontapp.com.

Are Chatwoot API and Front API + MCP open source?

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

Other comparisons with Chatwoot API or Front 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.