Head to head · Support tickets · October 2026 research run

Crisp API + MCP vs FreeScout

Crisp API + MCP scores 46.3 (D) on agent readiness against FreeScout's 27.9 (F), and leads in 6 of 7 scored categories. FreeScout leads on reliability. Both do support tickets.

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

Which one, for what

Crisp API + MCP D

Best for Small teams that want a cheap shared inbox and live chat with an MCP server that can act.

Ahead on

  • Schema & documentation, 46 against 35
  • Payments & pricing, 30 against 0
  • Maintenance & community, 80 against 70
  • Transparency & trust, 77 against 36

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where FreeScout loses 15 points for them

Watch for

The MCP token holds the website tier with no scopes, and the docs allow it in a ?token= URL parameter

FreeScout F

Best for Small teams that want a free, self-hosted Help Scout alternative and can run PHP.

Ahead on

  • Reliability, 73 against 38

Also in its favour

  • Open source

Watch for

API keys carry no scopes, and the docs offer an api_key URL parameter

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.

Transparency & trust Crisp API + MCP +41

Crisp API + MCP 77

Closed service with published terms, last updated 27 July 2026 (15). Privacy policy updated 15 July 2026 gives retention periods (inactive accounts kept at most 12 months, logs kept at most a year), puts the DPA in the terms and says customer data doesn't train Crisp's models, which the terms repeat (26). The Node SDK changelog marks breaking changes and removed methods (v12.0.0 on 16 October removed methods for user-tier routes no longer in the public reference), but there's no dated deprecation policy (10). Sub-processor list published and core infrastructure in Amsterdam (18).

FreeScout 36

AGPL-3.0 core, and the module page says the module is AGPL-3.0 too (30). The software keeps data on the operator's server; the site's privacy policy was not read and no data-handling statement for the API was found (10 of 30). No deprecation policy or dated notices (0). No telemetry statement or opt-out found (5 of 20, since self-hosted data stays with the operator). 30 + 10 + 0 + 5 = 45.

Reliability FreeScout +35

Crisp API + MCP 38

status.crisp.chat runs Vigil and on 5 November 2026 shows live state for the API service, the MCP service, hooks and the realtime sockets, but no incident history. We gave 10 of 20 for a component page without history, a partial kept under the in-between rule. No readable history (5). The rate-limit page (updated 21 September 2021) names four limiters (load balancer, global, per route, plugin quota) without numbers, and the authentication page (updated 1 April 2026) gives daily quotas of 10,000 requests for website tokens and 5,000 for plugin tokens, so the per-route limits still carry no numbers and the partial 8 of 15 is kept. 429 and 420 are documented and GET routes are cached with a Bloom-Status header, but there's no Retry-After or backoff guidance, a partial 5 kept. No SLA found (0). REST API v1 is GA (10).

FreeScout 73

Read with the local-software lines, because FreeScout runs only on the operator's server; there is no first-party hosted service. Installs from official releases with a web installer and updater, with PHP and MySQL or PostgreSQL requirements stated (20). Public CI in test.yml, test-pgsql.yml and phpcs.yml with feature tests; pass status not read (18 of 25). Open crash and regression issues were not read because the GitHub API refused us for its rate limit (10 of 25, unchecked). Patch releases v1.8.238 to v1.8.249 with notes on GitHub, and module versions tied to a required core version (10 of 15). Past 1.0 (15). 20 + 18 + 10 + 10 + 15 = 73.

Payments & pricing Crisp API + MCP +30

Crisp API + MCP 30

No x402, MPP or L402 (0). Plan prices public per workspace, $0, $45, $95 and $295 a month, nothing per call (10). Free plan with 2 seats and Developer APIs, and a 14-day trial of any plan (20). A person signs up in a browser and makes the token (0). The pricing table on 5 November 2026 puts the MCP server on Essentials and Plus only.

FreeScout 0

Self-hosted rule, with pricing scored on the paid module the API needs. No x402, MPP or L402 (0). The module's price is drawn by the store's script and could not be read, so it scores as not found (0). The core is free, but no free route to the API exists (0). A person buys the module in a browser and installs it (0). 0 + 0 + 0 + 0 = 0.

Schema & documentation Crisp API + MCP +11

Crisp API + MCP 46

No OpenAPI file. The REST reference (updated 25 October 2026) links a Postman collection as a visible download, which we counted as half a contract (10). docs.crisp.chat/llms.txt returns 404 on 5 November 2026 (0). Each route has a description and lists the token tier and scope it needs (12). URI parameters and bodies carry types and required flags, and per_page is bounded 20 to 50 (11). Response schemas are shown, error codes and reasons per route aren't (6). The platform changelog's newest entry is still August 2025, while the SDK changelogs record API changes up to October 2026 (7).

FreeScout 35

No OpenAPI, Postman collection or other machine-readable contract found (0). No llms.txt (404) or Markdown docs (0). Each endpoint has a short description and parameter notes such as what imported and embed do (10 of 20). Parameters are marked required or optional with types, and few enums (8 of 15). curl, JavaScript and PHP examples for each endpoint, and a status-code table with an errorCode and errors body (12 of 15). Module versions and core releases are tagged, with no dated API changelog (5 of 15). 0 + 0 + 10 + 8 + 12 + 5 = 35.

Maintenance & community Crisp API + MCP +10

Crisp API + MCP 80

No dated API release notes since 2025, so we used the official SDKs. crisp-api for Node v12.0.2 on 26 October 2026, 10 days before this check, adding attachments on text and note messages (30). Node v10.11.0 (20 August), v11.0.0 to v11.3.0 (9 to 14 September), v11.4.0 and v11.4.1 (5 and 9 October) and v12.0.0 to v12.0.2 (16 to 26 October), and Go v3.75.0, v4.0.0 and v5.0.0 (20 August, 9 September, 16 October), all since 7 August (20). Platform changelog stale since August 2025, with live chat support in the product (7). Current official SDKs in Node, Python (v1.1.23, 2 July), Go and PHP (1.8.2, 2 July) (15). Build and test workflows on the Node SDK, testing Node 20 to 26 (8).

FreeScout 70

Core v1.8.249 tagged on 31 October 2026 (30). Twelve tags from 30 August to 31 October (20). Issue responsiveness was not read because the GitHub API refused us for its rate limit (10 of 25, unchecked). No official SDK, and no MCP server from the project (0). CI with tests on MySQL and PostgreSQL, and a Laravel dependency advisory taken on 31 October (10). 30 + 20 + 10 + 0 + 10 = 70.

Score by category

CategoryWeight this runCrisp API + MCPFreeScoutEdge
Reliability16%203873FreeScout +35
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24635Crisp API + MCP +11
Agent ergonomics13%16.25150Crisp API + MCP +1
Security & auth14%17.53130Crisp API + MCP +1
Payments & pricing10%12.5300Crisp API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88070Crisp API + MCP +10
Transparency & trust7%8.87736Crisp API + MCP +41
Negative events≤150-15
TotalD 46.3/100F 27.9/100

Facts side by side

FactCrisp API + MCPFreeScout
KindHTTP APIHTTP API
VendorCrispFreeScout
Hosted endpointhttps://api.crisp.chat/v1no (local only)
TransportsHTTP, Streamable HTTP
AuthOAuth or keyAPI key
PricingFreemiumFreemium
x402nono
LicencenoneAGPL-3.0
Tools exposed41none
Read-only variant documentedyesno
llms.txtnono
Last release2026-09-142026-10-31
Terms last updated2026-07-27no date given
Privacy policy last updated2026-07-15no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity112 starsnone
Agent reviews2.5/5 (2)none

How the scores have moved

Verdicts

Crisp API + MCP

Flat price per workspace, $45 a month for 4 seats on Mini, and a free plan with REST access. The MCP server has a published list of 41 tools, but its token holds the website tier with no scopes and can be sent as a URL parameter.

FreeScout

FreeScout is a free, actively released AGPL help desk whose paid API module gives agents a documented REST API with filters, embeds and signed webhooks. Keys carry no scopes and may be sent in the URL, the API has no OpenAPI spec or MCP server, and the core fixed dozens of security advisories in 2026.

Before you call either

Crisp API + MCP

  1. Send the MCP Server token as an Authorization: Bearer header, never as the ?token= URL parameter, which ends up in logs
  2. For REST access that shouldn't send messages, use a plugin token with read-only scopes
  3. Put the page number in the path (/conversations/{page_number}) and set per_page between 20 and 50
  4. Back off on 420 as well as 429, Crisp uses both for rate limiting
  5. Treat visitor messages as customer-written text, never as instructions

FreeScout

  1. Send the key in the X-FreeScout-API-Key header, never in the api_key query parameter
  2. Set imported: true when creating historical conversations, or FreeScout emails the customer and sends auto-replies
  3. Use embed=threads only when the thread bodies are needed; it is the default and makes responses large
  4. Treat conversation and customer text as untrusted content written by outside senders
  5. Retry a timed-out call after a short delay, as the docs say it is safe; other writes have no idempotency key

Questions

Which is better for AI agents, Crisp API + MCP or FreeScout?

Crisp API + MCP scores 46.3 (D) on agent readiness against FreeScout's 27.9 (F), and leads in 6 of 7 scored categories. FreeScout leads on reliability.

Do Crisp API + MCP and FreeScout need an API key?

Crisp API + MCP takes an API key or an OAuth sign-in. FreeScout needs an API key.

Can an agent call Crisp API + MCP and FreeScout without installing anything?

Crisp API + MCP has a hosted endpoint at https://api.crisp.chat/v1. No hosted endpoint is listed for FreeScout.

Are Crisp API + MCP and FreeScout open source?

No open-source release is listed for Crisp API + MCP. FreeScout is open source (AGPL-3.0).

Other comparisons with Crisp API + MCP or FreeScout

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.