Chatwoot alternatives
The highest-scoring alternative to Chatwoot is Intercom at 57/100 on the AgentReady, against 48/100 for Chatwoot.
All scored in Customer Support APIs.
| Score | Alternative | Compare |
|---|---|---|
| 57 | Intercom | Chatwoot vs Intercom |
| 55 | Gorgias | Chatwoot vs Gorgias |
| 48 | Zendesk | Chatwoot vs Zendesk |
| 47 | Help Scout | Chatwoot vs Help Scout |
| 43 | Stream | Chatwoot vs Stream |
What Intercom does that Chatwoot does not
Intercom passes mcp discoverable, fast time to first request, copyable quickstart, mcp integration available, and Chatwoot fails them. That is the whole of the gap between the two scores, so if none of those matter to your agent the ranking above overstates the difference.
Why people look for an alternative
Chatwoot fails llms-full.txt / full agent docs, mcp discoverable, structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, no mandatory sales call, programmatic credential creation, fast time to first request, copyable quickstart, mcp integration available, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified. Each one is a place an unattended run stops, which is usually what sends someone looking in the first place.
Where Chatwoot loses the points
| Pillar | Chatwoot | What it measures |
|---|---|---|
| Discover | 80 | Can an agent find it at all: sitemap, robots, structured data. |
| Understand | 23 | Is there a spec, an llms.txt, a machine-readable description. |
| Adopt | 55 | Signup, keys, SDKs, and whether a human has to be involved. |
| Operate | 35 | Rate-limit headers, errors, status, and behaviour under load. |
Chatwoot is weakest on understand at 23/100. Without a spec an agent has to guess at endpoints, and it guesses wrong. If that is the part your agent depends on, take the ranking above seriously; if it is not, Chatwoot may still be the right pick.
What an agent runs into with Chatwoot
These are the findings from the last audit on 2026-08-23. Each one is a place unattended software stops, which is the practical reason to look at the list above.
- Ship an MCP server so agents can call you as a tool.
- Publish MCP install instructions so agents can discover the server.
- Publish an OpenAPI spec so agents can generate a client.
- Flesh out the OpenAPI: paths, schemas, and descriptions.
- Document error responses as an enum in your OpenAPI.
- Let agents create API keys programmatically.
- Return X-RateLimit / Retry-After headers so agents pace themselves.
- Publish an AGENTS.md or llms-full.txt with full agent context.
What this category actually supports
Across the 6 products scored in Customer Support APIs, manage support tickets is offered by 83%, live chat is offered by 50%.
An agent can get this list directly: resolve("alternative to Chatwoot") over the MCP server, or GET /v1/categories/customer-support.