Incident Management
Freshservice MCP connector
The Freshservice connector brings your tickets, replies, notes and service desk agents into Claude, ChatGPT, Cursor and the Elaichi Agent, so people can raise, update and answer tickets in plain language while every action stays inside their own Freshservice access.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Freshservice to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Freshservice once
-
Open Connections, choose Add connection, and pick Freshservice.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Freshservice API key. One person generates a token in Freshservice and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Freshservice to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Freshservice to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Freshservice to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Freshservice to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Freshservice through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
IT service desk
Catch a ticket up after a call
Tell the agent what the caller said and it updates the ticket, adds an internal note and posts a reply to the requester, so nothing has to be typed twice.
-
IT service desk
Triage the morning queue
Ask for every open ticket that is high priority, unassigned or past due, and hand them out to the right people without opening each one.
-
IT operations
Break a major incident into child tickets
When the VPN goes down, spin one parent ticket into child tickets for networking, identity and communications, and keep the whole thread linked.
-
HR
Raise a new starter request in one go
Describe the new hire, their start date and the kit they need, and the agent creates the Freshservice ticket with the details filled in and the right group picked.
-
Facilities
Log and chase a repair request
Report a broken door badge reader or a meeting room screen, then ask for a status update later and reply to the requester when it is fixed.
-
IT management
Keep the agent roster current
Deactivate a departing technician, convert a contractor to a requester when their engagement ends, and check which roles each service desk agent holds.
Try asking
- “Show open Freshservice tickets raised in the last week.”
- “Which agents have the most unresolved tickets right now?”
- “Create a ticket for the failed payroll export.”
AI tools
Freshservice tools for your AI agents
394 tools are ready to call through Elaichi's MCP endpoint the moment you connect Freshservice, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Freshservice gets you
6 screens from the product, each doing one job for your Freshservice account.
The agent
Ask about tickets, read the answer.
Plain language questions return live Freshservice tickets, agents and roles.
- tickets
- agents
- roles
- requesters
Ask Elaichi to work across your apps.
Show open Freshservice tickets raised in the last week.
Which agents have the most unresolved tickets right now?
Create a ticket for the failed payroll export.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One Freshservice endpoint for every client.
Claude, ChatGPT and Cursor connect over OAuth, no SDK, no shared key.
Copy the endpoint
Tool catalog
394 Freshservice tools, no custom code.
Tickets, agents, roles and requesters, with every resource and method listed.
- List all Freshservice agents
- Get single Freshservice agent by ID
- Delete a Freshservice agent by ID
- Create a Freshservice agent
Toolboxes
Every team gets its own toolbox.
Scope Freshservice ticket and agent tools to the team that needs them.
- Service desk
- IT operations
- Onboarding
- Change management
Shared connections
Teammates use Freshservice without a credential.
See who connected each account and how many teams and members share it.
- Service desk EMEA
- IT operations
- Onboarding
- Change management
Audit log
Every Freshservice call is on record.
When, who, what happened, type and resource, appended and never edited.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, a digest ships.
Fetch Freshservice tickets, group them, draft a digest, approve, post it back.
Freshservice digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch tickets
Freshservice
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Freshservice
Queued
Collections and dashboards
Freshservice ticket health, computed on schedule.
Four metrics, 14 days of tickets created, and a breakdown by team.
Freshservice health
Refreshed 4 minutes ago · every 15 minutes · from the tickets collection
Tickets
1,284 ↓ 12%
Agents
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Tickets created
Last 14 days
By team
Share of activity
Service desk EMEA 34%
IT operations 27%
Onboarding 21%
Change management 18%
FAQ
Frequently asked questions
How do I connect Freshservice to Claude?
Connect Freshservice in Elaichi first: you paste the API key from your own Freshservice profile, and there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi, and from then on your Freshservice tickets are available in the chat.
Does Freshservice work with ChatGPT and Cursor as well as Claude?
Yes. Once Freshservice is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Freshservice once and every client you use picks it up.
What can an AI agent actually do with my Freshservice data?
With Freshservice connected, an agent can find tickets by status, priority or group, read the full conversation on a ticket, post a reply to the requester or an internal note, and update fields like priority, assignee and status. It can also create new tickets, split an incident into child tickets, move a ticket to another workspace, restore one that was deleted, and manage service desk agents and their roles. Freshservice offers a lot of actions, so short concrete asks, such as "show my open P1 tickets", get better results than long paragraphs.
Does connecting Freshservice give the AI every ticket in the service desk?
No. The AI works inside the Freshservice access of the person who connected, so the groups, workspaces and ticket scope that apply to that agent in Freshservice apply to the AI as well. Elaichi can narrow that further by blocking particular actions, but it can never widen it beyond what the person could already see or do in Freshservice.
Can I stop an agent from deleting or changing things in Freshservice?
Yes. Restrictions in Elaichi apply to each Freshservice action separately, so you can allow reading and replying to tickets while blocking deleting tickets, removing conversations or deactivating agents. A blocked action is never shown to Claude, ChatGPT or any other client at all, so no prompt, however it is worded, can reach it.
What happens to a Freshservice connection when someone leaves?
When you offboard someone in Elaichi, their access to Freshservice through every client ends at once. A shared Freshservice connection keeps working for everyone else on the team. If you disconnect Freshservice in Elaichi, it disappears from Claude, ChatGPT, Cursor and every other client in one step.
Put Freshservice in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.