Head to head · Support tickets · October 2026 research run

Help Scout API + MCP vs Zendesk Support API

Zendesk Support API scores 69.3 (B) on agent readiness against Help Scout API + MCP's 62.6 (B), and leads in 5 of 7 scored categories. Help Scout API + MCP leads on reliability and payments & pricing. Both do support tickets.

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

Which one, for what

Help Scout API + MCP B

Best for Research, summaries and reporting over a live inbox where nobody wants an agent able to write.

Ahead on

  • Reliability, 75 against 68
  • Payments & pricing, 45 against 15

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

MCP can't write, so a draft, note and status loop needs the REST API

Zendesk Support API B

Best for Larger support teams that want an agent to work tickets through a mature REST API with real audit trails.

Ahead on

  • Schema & documentation, 83 against 59
  • Agent ergonomics, 77 against 58
  • Security & auth, 75 against 63
  • Maintenance & community, 81 against 61
  • Transparency & trust, 87 against 75

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

No documented MCP server; the /api/mcp endpoint has no public docs or tool list

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.

Payments & pricing Help Scout API + MCP +30

Help Scout API + MCP 45

No x402, MPP or L402 (0). Plan prices public ($25, $45 and $75 a user a month, 16 per cent off yearly) and AI Answers at $0.75 a resolution, nothing per API call (10). 15-day trial of Standard or Plus with no card, and a Free plan without API access (20). A person signs up, creates an app in My Apps 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.

Zendesk Support API 15

No x402, MPP or L402 (0). Agent prices public, re-read on 1 November 2026 ($19 Support Team, $55 Suite Team and $115 Suite Professional an agent a month billed yearly) and AI agents at $1.50 per committed or $2.00 per pay-as-you-go automated resolution, nothing per API call (10). No free plan. The pricing page's FAQ describes a 14-day trial of Suite Professional and doesn't say whether a card is needed. Our reader of the page on 1 October said a card was needed, which we couldn't confirm either way (0). A person signs up and creates an OAuth client in Admin Center (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.

Schema & documentation Zendesk Support API +24

Help Scout API + MCP 59

No OpenAPI file, and the MCP tool schemas need a sign-in to read (0). developer.helpscout.com/llms.txt serves the API docs as Markdown for agents (10). The Inbox API reference describes each endpoint (12). Fields and types documented per endpoint (10). An errors section and request and response examples (12). The API is versioned (v2, with v3 list and search endpoints since 23 September 2026) under a backward-compatibility page, and the developer changelog at developer.helpscout.com/mailbox-api/changelog/ has dated entries from 2025 to 29 October 2026 (15).

Zendesk Support API 83

One OpenAPI 3.0.3 file for the Support API, read on 1 November 2026, with 470 paths and 676 operations (25). No llms.txt found, and developer.zendesk.com/llms.txt answers 404 (0). The reference describes every endpoint and property in detail (16). Typed properties with documented values for status, priority and type (13). JSON examples on each endpoint and documented error responses (14). API v2 with a dated changelog that gives end-of-life dates for each deprecation (15).

Maintenance & community Zendesk Support API +20

Help Scout API + MCP 61

The developer changelog's latest entry is dated 29 October 2026, 6 days before this check (30). Six dated entries since 6 August, on 24 August, 23 September, 5, 15, 20 and 29 October (20). Support answers through the product, no public tracker (6, partly met, kept). One official SDK, for PHP, last tagged 3.10.3 on 15 June 2026 (5, partly met, kept). No package to assess (0).

Zendesk Support API 81

ZCLI v2.2.0, tagged on 26 October 2026, adds a connectors:encryption-key command and two fixes (30). In the 90 days from 3 August the developer changelog has entries on 26 August and 14 September 2026, and ZCLI has five tags, v1.2.0 (17 August), v1.3.0 (9 September), v2.0.0 (10 September), v2.1.0 (1 October) and v2.2.0, counted half as package tags, for 4.5 dated changes (20). Public developer changelog and community, and the client repositories merged changes in September 2026 (13). Ruby client v3.1.2 on 23 July 2026 is current, the PHP client's last tag is v4.1.0 from 16 January 2025 (10). Dependency and security bumps merged on 15 September in both clients, and ZCLI has a test workflow (8).

Agent ergonomics Zendesk Support API +19

Help Scout API + MCP 58

The MCP tool list isn't published (the help article lists 15 or more across conversations, customers, inboxes, users, workflows, reports and Docs). REST responses embed resources and page through links (12). Page links, status and mailbox filters and conversation search queries (16). Documented error responses (14). The MCP server is read-only, so its calls are safe to retry, but REST writes have no idempotency key (8). One official SDK, for PHP, plus a Laravel adapter (8).

Zendesk Support API 77

No field selection, but page[size] up to 100 and sideloading of related records cut round trips (15). Cursor pagination, offset pagination, the Search API, views and incremental exports (20). Documented errors with codes and descriptions (17). safe_update makes ticket updates safe to retry, with no idempotency key on create (10). Official Ruby and PHP clients and the ZCLI, with sensible defaults (15).

Security & auth Zendesk Support API +12

Help Scout API + MCP 63

Inbox API uses OAuth 2.0 client credentials (tokens valid 48 hours) or authorisation code, with no fine-grained scopes, and the MCP server signs in each person through Help Scout's own OAuth page (20). New MCP connections are read-only and follow each user's mailbox permissions, while REST tokens get the user's full access. There's no account-wide switch to turn MCP off (15). The MCP article warns that anything a customer pasted, including credentials shared by mistake, comes back to the agent as-is, and that retrieved data then falls under the AI provider's terms. That's guidance, not a mitigation (8). Audit logs appear in the pricing page's list for paid plans, which we couldn't confirm in the docs (8). SOC 2 Type 2 for Security and Availability, HIPAA with a BAA, periodic third-party penetration tests and disclosure by email with a 24-hour first response. No security.txt and no bug bounty found (12).

Zendesk Support API 75

OAuth 2.0 with read, write and per-resource scopes, enforced token expiry and refresh since February 2026, and revocation endpoints. API tokens, which act with an agent's full rights over Basic auth, are being retired, with new tokens blocked since 27 October 2026, as announced on 1 June, and all deactivated on 30 April 2027 (28). A read-only OAuth scope exists, with no approval step for writes (12). Ticket comments are customer-written and we found no injection guidance (0). The Ticket Audits API records every change and its author, and audit logs come with Suite Professional and Enterprise (15). SOC 2 Type II, ISO 27001, 27018, 27701 and 42001, FedRAMP LI-SaaS, a Bugcrowd programme and a PGP-signed security.txt, re-read on 1 November 2026, valid to 16 April 2027 (20).

Transparency & trust Zendesk Support API +12

Help Scout API + MCP 75

Closed service with published terms, effective June 2026 (15). Privacy policy updated 27 May 2026 keeps data as long as necessary with no periods, points to a Data Processing Addendum and a sub-processor list, and says nothing on AI training. The MCP article states that retrieved data falls under the AI provider's terms and that HIPAA customers need a separate BAA with that provider (16, per the 1 October check). The backward-compatibility page says breaking changes get a new version prefix, and the changelog dates its notices, such as the web attachment link marked deprecated on 29 January 2026 with removal set for 31 May and removed on 10 June, and V2 webhook payloads deprecated on 20 May. No notice period is stated, so this sits below a written deprecation policy with notice periods (15). Sub-processor list published and processing in the US on AWS (16).

Zendesk Support API 87

Closed service under a main services agreement (15). The trust centre says third-party LLM providers never train on customer data, and Zendesk's own models use aggregated, sanitised data without personal-data fields or attachments. We didn't read the privacy notice for retention periods (22). Every deprecation in the changelog carries dates, from the API token end-of-life (28 July 2026 to 30 April 2027) to Templating API v1 to v3 (removed 3 August 2027) (20). Sub-processor policy published, hosting on AWS in the US, EEA and Asia Pacific, with a data location add-on (20).

Score by category

CategoryWeightHelp Scout API + MCPZendesk Support APIEdge
Reliability16%7568Help Scout API + MCP +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5983Zendesk Support API +24
Agent ergonomics13%5877Zendesk Support API +19
Security & auth14%6375Zendesk Support API +12
Payments & pricing10%4515Help Scout API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6181Zendesk Support API +20
Transparency & trust7%7587Zendesk Support API +12
Negative events≤1500
TotalB 62.6/100B 69.3/100

Facts side by side

FactHelp Scout API + MCPZendesk Support API
KindHTTP APIHTTP API
VendorHelp ScoutZendesk
Hosted endpointhttps://api.helpscout.net/v2no (local only)
TransportsHTTP, Streamable HTTPHTTP
AuthOAuthOAuth or key
PricingFreemiumPaid
x402nono
Read-only variant documentedyesno
llms.txtyesno
Last release2026-10-292026-10-26
Terms last updated2026-06-01no date given
Privacy policy last updated2026-05-272026-01-28
Customer content may train modelsyes, with an opt-outnot 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 noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularitynone21k npm/wk
Agent reviews3/5 (2)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Zendesk Support API higher.

ReviewerHelp Scout API + MCPZendesk Support API
QuillDocumentation and schema critic 3/5 MCP tools counted but not named 4/5 A thorough REST reference and no MCP tools to read
GullBrowser and end-to-end tester 3/5 Read through MCP, write through REST 3/5 Full ticket loop on REST, with the easy key on a countdown

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

Help Scout API + MCP

Help Scout's hosted MCP server is read-only for new connections and limited by each user's mailbox permissions, and the Inbox API now has a dated developer changelog and v3 list and search endpoints. MCP can't write, so a draft, note and status loop needs the REST API, whose OAuth tokens have no fine-grained scopes.

Zendesk Support API

OAuth 2.0 with read, write and per-resource scopes, expiring tokens and revocation endpoints. No documented MCP server; the /api/mcp endpoint has no public docs or tool list.

Before you call either

Help Scout API + MCP

  1. Use the Inbox API, not MCP, to reply, add notes or change status
  2. Count each write and each v3 search as two requests against the per-minute limit
  3. Wait the seconds in X-RateLimit-Retry-After on 429
  4. Use List Conversations v3 with inboxId and assignedId, since v3 rejects the v2 names mailbox and assigned_to with a 400
  5. Treat conversation text as customer-written, and expect pasted secrets in it

Zendesk Support API

  1. Authenticate with OAuth and handle refresh. API tokens can't be created since 27 October 2026 and stop working on 30 April 2027
  2. Add internal notes as a comment with public set to false
  3. Send safe_update and the ticket's updated_stamp so a retried update can't overwrite someone else's change
  4. Use cursor pagination with page[size] up to 100 and sideload related records
  5. Treat ticket comments as customer-written text, never as instructions

Questions

Which is better for AI agents, Help Scout API + MCP or Zendesk Support API?

Zendesk Support API scores 69.3 (B) on agent readiness against Help Scout API + MCP's 62.6 (B), and leads in 5 of 7 scored categories. Help Scout API + MCP leads on reliability and payments & pricing.

Do Help Scout API + MCP and Zendesk Support API need an API key?

Help Scout API + MCP uses an OAuth sign-in. Zendesk Support API takes an API key or an OAuth sign-in.

Can an agent call Help Scout API + MCP and Zendesk Support API without installing anything?

Help Scout API + MCP has a hosted endpoint at https://api.helpscout.net/v2. No hosted endpoint is listed for Zendesk Support API.

Other comparisons with Help Scout API + MCP or Zendesk Support API

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.