How to Connect Freshservice to Claude (and What It Can't Do)
The answer changed this spring. At its Refresh conference in May 2026, Freshworks announced an MCP Gateway for Freshservice, and the inbound half is exactly what this page’s title asks for: an MCP endpoint on your own helpdesk domain — https://<your-domain>.freshservice.com/mcp — that Claude can talk to. The catch is who gets it. As of mid-2026 the integration sits in an Early Access Program restricted to the Enterprise plan.
Whichever route you take, the Claude-side rules apply: the server joins as a custom connector (paid Claude plans only), and it responds only within a conversation you start. There is no mode where Claude keeps an eye on your incidents between chats.
What the official endpoint exposes
Freshservice’s EAP documentation lists a fairly deep toolset:
- Tickets: create, update, fetch, and add notes — full lifecycle, not just reads
- Assets: create, read, and update CI records
- Service catalog: browse items and actually place requests
- Knowledge base: search and pull article details
- Requesters and agents: look up who’s who (read-only)
- Onboarding/offboarding: manage those request flows end to end
Authentication is OAuth 2.0 (recommended) or an API key header. There are also hard ceilings worth knowing before you plan anything ambitious: 100 tool calls per minute and 5,000 actions per month.
Not on Enterprise? There’s a community server
Teams on Growth or Pro aren’t locked out entirely. The open-source freshservice_mcp server by effytech wraps the standard Freshservice REST API — you run it yourself with your domain and API key, then register it with Claude the same way. You’re trusting community code with helpdesk credentials, so read the source and scope the API key as tightly as your use allows.
For Claude on the web, either route ends at Settings → Connectors, where you add the endpoint and complete auth. Claude Desktop takes the server via claude_desktop_config.json; Claude Code registers it with claude mcp add. All of them need a paid Claude plan for custom connectors.
Conversations it’s genuinely good at
Once connected, the service desk becomes queryable in plain English:
“Which open incidents are within two hours of SLA breach? Group them by assigned agent.”
“Summarize INC-4092 for the change advisory board — what happened, what was tried, current status.”
“How many laptop requests came through the service catalog this month, and how does that compare to May?”
For an IT lead prepping a Monday review, this collapses an hour of report-pulling into a few sentences.
Incidents don’t schedule themselves around your chats
Here is the awkward truth of a chat-bound connector on a service desk. A P1 lands at 2 a.m.; the endpoint could fetch it, but nobody is awake to ask. An SLA clock on a priority ticket quietly expires during lunch; Claude would have flagged it — in a chat no one opened. A change request stalls waiting on an approval the approver never saw. Freshservice’s own workflow automator covers some of this natively, but the Claude side contributes nothing between conversations: no listening, no polling, no acting.
Wiring the service desk to actual triggers
That gap — “do X the moment Y happens, without me present” — is Carly’s home turf. Carly is an AI executive assistant that runs event-driven workflows in the cloud:
- An incident is logged → Carly summarizes it, checks severity, and pings the on-call channel in Slack
- An SLA nears breach → escalate priority and notify the agent’s manager by email (sent, not drafted — Gmail or Outlook, attachments included)
- Monday, 8 a.m. → the queue digest arrives before standup, every week, untouched by human hands
You describe the workflow conversationally; Carly asks follow-up questions and builds it — no endpoints, no OAuth apps, no config files. AI agents start at $35/month, and non-AI steps in a workflow run free and unlimited. Details on the Freshservice integration page, with 200+ other tools under integrations.
The two options, side by side
| Claude + Freshservice MCP | Carly | |
|---|---|---|
| Query incidents, assets, catalog items | Yes, in chat | Yes |
| Create and update tickets | Yes, when prompted | Yes, on a trigger |
| Escalate a P1 the moment it’s logged | No | Yes |
| Warn before an SLA breach, unasked | No | Yes |
| Availability requirement | You, in a chat window | None — runs hosted 24/7 |
| Plan gates | Freshservice Enterprise (EAP) + paid Claude | AI agents from $35/mo |
| Monthly action ceiling | 5,000 MCP actions | Non-AI steps unlimited |
Frequently Asked Questions
Does Claude integrate with Freshservice?
Yes. As of mid-2026 Freshworks offers an official MCP endpoint at https://<your-domain>.freshservice.com/mcp, currently in an Early Access beta for Enterprise-plan customers. Added to Claude as a custom connector (paid plan required), it lets Claude fetch, create, and update tickets, assets, and service requests inside a chat.
What if we’re not on the Freshservice Enterprise plan?
Use a community MCP server such as effytech’s freshservice_mcp, which wraps the public REST API using your domain and API key. Same Claude-side setup, but you host and vet the code yourself.
Can Claude escalate an incident automatically when it’s logged?
No. Connectors act only inside an open conversation — there’s no event listener. Automatic escalation needs a trigger-based platform like Carly, which fires the moment the incident is created.
Are there usage limits on the official MCP integration?
Yes: 100 tool calls per minute and 5,000 actions per month, per Freshworks’ EAP documentation. Heavy automation would burn through that quickly — another sign it’s designed for interactive analysis, not background work.
Can I get SLA-breach alerts without sitting in a chat?
Not from Claude. Carly can run that as a standing workflow — watch the queue, catch tickets nearing breach, escalate and notify — around the clock. AI agents start at $35/month.
More: Claude connectors · Can Claude send emails · Claude vs Carly · Claude Cowork alternatives · Claude customer support · Claude + Zoho Desk · Claude + Canny · Claude + Productboard
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
