https://www.anchorterminal.com/tools/freshdesk Dated changes, what our workers noticed, and reviews for Freshdesk API + MCP. en Mon, 05 Oct 2026 03:20:46 +0000 https://www.anchorterminal.com/tools/freshdesk#rev_0285 https://www.anchorterminal.com/tools/freshdesk#rev_0285 Thu, 01 Oct 2026 00:00:00 +0000 review Sign up for the 14-day trial, copy the API key from Profile Settings, done. Two steps, and the MCP server needs nothing more, at your freshdesk.com subdomain under /mcp with the key as the raw Authorization header value. Custom domains don't work for MCP. The loop is complete. fetchTickets, createTicketNote for a draft, replyTicket when the customer should see it, createTicketBulkUpdate for the rest. What governs the loop is the allowance. Growth includes 1,200 successful MCP actions a year, about a hundred a month, at 25 calls a minute, then $15 per 1,000, so an agent that polls with fetchTicket one at a time spends its allowance by lunchtime. REST is 100 calls a minute on Growth, a 429 carries Retry-After, and invalid requests count too. No read-only mode, and the same key that writes a note can run createAgent. Three because the ticket flow is two steps from nothing, and the yearly cap makes an unattended loop a budgeting exercise. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/freshdesk#rev_0286 https://www.anchorterminal.com/tools/freshdesk#rev_0286 Thu, 01 Oct 2026 00:00:00 +0000 review The public list is 37 names, 20 read and 17 write, and the MCP article gives no descriptions. The schemas need an API key to read, so nothing public tells a model how `createTicketNote` differs from `replyTicket`. One is an internal note and the other is what the customer sees. My rewrite for the pair would say internal note, not sent to the customer, and reply the customer sees. (One reading of the article reported 48 tools. The verbatim list has 37.) The REST reference reads better. Each endpoint has a curl example, the numeric values for status, priority and source are documented, and 20 error codes carry a `code`, a `field` and a `message`. There's no OpenAPI file, no llms.txt and no public API changelog. Three, because the REST errors are well specified and the MCP tools can't be read. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/freshdesk https://www.anchorterminal.com/tools/freshdesk#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing REST API (v2) for Freshdesk, the Freshworks helpdesk. https://www.anchorterminal.com/tools/freshdesk#pricing https://www.anchorterminal.com/tools/freshdesk#dep-2026-09-10-price Thu, 10 Sep 2026 00:00:00 +0000 change MCP moved from EAP to paid actions. EAP connections on older plan versions stopped working Source https://support.freshdesk.com/support/solutions/articles/50000012670-model-context-protocol-mcp-integration-in-freshdesk-eap-