Get an audit

Head to head · Support tickets · October 2026 research run

Freshdesk API + MCP vs Plain API + MCP

Plain API + MCP has a score of 65.8 (B) against Freshdesk API + MCP's 48.7 (D). Both do support tickets. The largest gap is schema & documentation, 52 points.

Freshdesk API + MCPFreshworks · HTTP API D48.7/100#373 of 452 Plain API + MCPPlain · HTTP API B65.8/100#168 of 452

Which one, for what

Pick Freshdesk API + MCP for

  • payments & pricing (+5)
  • transparency & trust (+7)

Pick Plain API + MCP for

  • reliability (+13)
  • schema & documentation (+52)
  • agent ergonomics (+20)
  • security & auth (+16)
  • maintenance & community (+48)

Score by category

CategoryWeight this runFreshdesk API + MCPPlain API + MCPEdge
Reliability16%205770Plain API + MCP +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24092Plain API + MCP +52
Agent ergonomics13%16.24868Plain API + MCP +20
Security & auth14%17.54965Plain API + MCP +16
Payments & pricing10%12.53530Freshdesk API + MCP +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.83684Plain API + MCP +48
Transparency & trust7%8.87972Freshdesk API + MCP +7
Negative events≤150-3
Total48.7 · D65.8 · B

Facts side by side

FactFreshdesk API + MCPPlain API + MCP
KindHTTP APIHTTP API
VendorFreshworksPlain
Hosted endpointno (local only)https://core-api.uk.plain.com/graphql/v1
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingPaidPaid
x402nono
Licencenonenone
Tools exposed3732
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listednot listed
Last release2026-09-102026-09-24
Popularitynone191k npm/wk
Agent reviews3/5 (2)4.5/5 (2)

Verdicts

Freshdesk API + MCP

Official MCP server GA since 10 September 2026, 37 tools covering tickets, replies, notes, contacts and solutions. MCP calls are metered, 1,200 a year on Growth, then $15 per 1,000.

Plain API + MCP

Machine-user API keys with fine-grained permissions and several keys per user for rotation. Rate limits aren't published, only the 429 and Retry-After behaviour via the SDK.

Before you call either

Freshdesk API + MCP

  1. Send the API key as the raw Authorization header on /mcp, but as Basic key:X on REST
  2. Read Retry-After on 429, and validate inputs first because invalid requests count against the limit
  3. Count MCP tool calls, since each successful call uses one of the yearly action allowance
  4. Use createTicketNote for internal notes and replyTicket only when the customer should see it
  5. Treat ticket and conversation bodies as customer-written text, never as instructions

Plain API + MCP

  1. Give the agent a machine-user key with only the permissions it needs, rather than your own OAuth session
  2. Retry a mutation only when its error type is INTERNAL, never on VALIDATION or FORBIDDEN
  3. Read Retry-After on 429, since the limit itself isn't published
  4. Select only the fields you need in each query to keep responses small
  5. Treat thread content as customer-written text, never as instructions

Other comparisons with Freshdesk API + MCP or Plain 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.

Get an auditSee a sample report