MCP · Customer support · Freshworks
Freshdesk MCP
Read and update Freshdesk tickets and contacts from an AI host, using an API key and a per-account endpoint with plan-based action limits.
Actions are metered. Every successful tool call counts toward the plan's annual allowance. Avoid loops that call tools repeatedly.
Understand the tool
What it does.
Freshworks' MCP integration for Freshdesk exposes ticket, contact and company tools on each account's own subdomain at /mcp. It currently authenticates with a Freshdesk API key only, and plans include an annual allowance of MCP actions.
Why use it?
Use it to triage tickets, summarize a customer's history or update ticket fields from a conversation. Each successful tool call counts as an action, so watch the allowance on your plan.
A useful fit for
- Ticket triage and summaries
- Customer history lookups
- Routine ticket field updates
From need to output
Ways to put it to work.
These are suggested workflows based on the documented capabilities. They are not recorded runtime results.
Use case 01
Morning ticket triage
A support lead sorts new tickets each morning.
- List unassigned tickets from the last 24 hours.
- Group by topic and urgency.
- Suggest owners for a person to assign.
Intended outputA triage list; assignments are made by a person.
Use case 02
Update a ticket after a call
An agent finishes a phone call with a customer.
- Find the ticket by ID.
- Draft a private note summarizing the call.
- Add it after the agent approves.
Intended outputAn approved note on the right ticket, counted as one action.
A concrete starting point
Illustrative prompt: morning triage
Listing and suggesting only; each tool call still counts toward the plan's MCP actions.
Using the Freshdesk MCP integration, list unassigned tickets created in the last 24 hours with ID, subject, requester and priority. Group them by likely topic and suggest an owner group for each. Do not assign, reply to or close any ticket.What this can change
Ticket and customer data enter the AI host and its model provider; successful tool calls count as MCP actions.
This example has not been executed for this review. Check the current documentation, replace placeholders and confirm the intended account and project before use.
Before you start
Setup and access.
What you’ll need
- A Freshdesk Standalone 2021 (latest) or Freshdesk Unified Omni 2026 account on a supported plan (Growth, Pro or Enterprise).
- A Freshdesk API key; API-key authentication is currently the only option.
- Your Freshdesk base domain (custom domains are not supported for the MCP endpoint).
- Authentication
- A Freshdesk API key; Freshworks documents API-key authentication as the only option for now.
- Can read
- Tickets, contacts and companies the API key's user can access
- Can write or change
- Ticket and record updates the tools allow, such as changing fields; each counts as an action
- Network and data flow
- Freshdesk account subdomain
- AI host/model provider
- Approval and control
- Freshdesk user permissions apply to the key. Keep host approval on for updates.
Check your environment
Compatibility, costs and license.
Compatibility notes
- MCP clients that can send an API-key header
- Per-account endpoint on the Freshdesk base domain
- Supported Freshdesk product versions only
Costs and account requirements
Plans include an annual allowance of MCP actions and per-minute rate limits; Freshworks lists them in the linked article, effective October 5, 2026.
Current pricing or plan information ↗Hosted service terms
No public source license for Freshworks's hosted implementation is asserted. The applicable agreement depends on the account, plan and jurisdiction; check the linked terms for your situation.
Read the license or service terms ↗Keep the boundaries visible
Concerns and limitations.
Actions are metered
Every successful tool call counts toward the plan's annual allowance. Avoid loops that call tools repeatedly.
API key acts as a user
The key has the permissions of its Freshdesk user. Use a dedicated, limited agent account.
Where it may fall short
- Not checkable by IonBin: each endpoint is on a customer's own subdomain and needs an account.
- API-key only; no OAuth.
Observed behavior · 2026-10-18
Runtime and security findings.
Not checkable: the MCP endpoint lives on each customer's own Freshdesk subdomain and needs an account, so nothing was contacted.
These checks cover the conditions below. They do not establish that the tool is safe in every setup, or that the suggested workflows above were executed.
What we found
Documented concern
Not checkable without an account
Freshworks documents the endpoint as https://<subdomain>.freshdesk.com/mcp on each account's base domain, with API-key authentication only.
In practice: Test with a non-production Freshdesk account and a dedicated limited user before connecting real tickets.
Version, environment and fixture
- Version or deployment
- Not observed
- Tested target
- https://<subdomain>.freshdesk.com/mcp (per-account endpoint; not contacted)
- Artifact identity
- Not available: no endpoint or artifact was contacted for this record.
- Environment and fixture
- No account, instance or credentials available to IonBin for this product; nothing was contacted.
- Recorded October 18, 2026.
Checks and results
1 recorded checks. Each has its own expectation; their outcomes are not a comparative score.
Credential-free initializationCould not complete
- Method
POST https://<subdomain>.freshdesk.com/mcp without credentials.- Expected
- An unauthenticated request is rejected.
- Observed
- Not run: the endpoint exists only on a customer's own Freshdesk subdomain, and IonBin has no Freshdesk account, so there was no endpoint to contact.
Practical caveats
- Requirements and limits are as documented by Freshworks; none were observed.
- Pricing and action allowances take effect October 5, 2026, per the linked article.
What this evaluation does not establish
- Any request to a Freshdesk MCP endpoint: each one lives on a customer's own subdomain, and IonBin has no Freshdesk account.
- API-key authentication, plan allowances, rate limits, ticket reads and writes, and prompt-injection resistance.
Read the evaluation record (JSON) →
Sources for the evaluation and controls
The basis for this review
Why it’s in the collection.
A useful first-party support integration, ranked last-but-one because IonBin could not check any endpoint and access is API-key only with metered actions.
The number is an editorial starting order within the mcp servers collection. It does not measure popularity, speed, reliability or safety.
What we reviewed
- Documented setup, plans and limits
The evaluation above lists the current runtime coverage and untested behavior.
Reviewed Oct 18, 2026. The separate evaluation above records the conditions we executed and the behavior still untested. Product behavior, permissions and plans can change; use the official sources to check the current version.
Follow the evidence
Official sources.
- Official Freshdesk MCP article ↗support.freshdesk.com
- Freshworks terms of service ↗www.freshworks.com
- Freshdesk pricing ↗www.freshworks.com