Productivity & Project Management · Freshservice + Claude
Freshservice MCP with Claude: Faster IT Service Desk Workflows
The short answer
Claude connects to Freshservice through the Model Context Protocol (MCP), a secure standard that lets Claude read and act inside the tool with permissions you control. Once connected, Claude can create incidents, update tickets, manage service requests and automate ITSM workflows through plain-language instructions, with people approving consequential changes.
What is Freshservice?
Freshservice is a cloud-based IT service management platform. IT teams use it to log and resolve incidents, track assets such as laptops and software licences, and run a service desk for employees. It helps IT departments organise support requests, follow agreed service levels and keep a central record of what has been done. Typical users include IT service desk agents, IT operations managers and support leads in organisations of all sizes.
How Claude connects to Freshservice through MCP
The Model Context Protocol (MCP) is an open standard that lets Claude securely use other software. Think of it as a universal adapter between Claude and the tool. Freshservice's connection can be set up with an API key, so Claude uses a defined credential rather than a shared login.
Once connected, Claude can typically read tickets, look up assets and review service request details in Freshservice. It can also take actions such as creating an incident, updating ticket fields or routing a service request, based on instructions given in natural language. Staff can ask for these things in ordinary sentences instead of navigating several screens.
Permissions and approvals keep people in charge. We set access to the least privilege needed for each workflow, so Claude only touches the areas it should. Consequential actions, such as closing major incidents or changing asset ownership, can require a human sign-off, and every action is recorded in audit logs for review.
What you can automate
Logging incidents from conversation
An employee reports a problem in a chat tool. Claude gathers the key details, such as device, location and urgency, and creates a properly categorised incident in Freshservice. The agent receives a complete ticket rather than a vague message, which can shorten the time to first response.
Updating tickets in plain language
A service desk agent says, "Mark the printer ticket for the Pune office as waiting on vendor and add a note." Claude finds the ticket, updates the status and adds the note. Agents spend less time clicking through fields and more time solving problems.
Managing service requests
Common requests such as new starter laptops or software access can be raised and tracked through Claude. It can check the request against the approval rules you define and move it to the right fulfilment team, helping requests flow without manual handoffs.
Asset lookups and housekeeping
When a manager asks which laptops are assigned to a team or which licences are near expiry, Claude can search Freshservice asset records and summarise the answer. Teams can use this to plan refresh cycles and spot gaps in records more quickly.
Weekly ITSM reporting
Operations leads often need a summary of open incidents, overdue requests and repeat issues. Claude can pull the relevant ticket data and draft a short weekly report, which a manager reviews before it is shared with leadership.
An end-to-end workflow: New starter onboarding request
TriggerHR confirms a new employee start date in the HR system.
Claude reads the new starter details from the HR system and checks the role.
Claude raises a service request in Freshservice for a laptop, email account and standard software bundle.
The request is routed to the correct fulfilment group based on department and location.
Claude posts a status update to the hiring manager in Microsoft 365 Teams.
An IT agent approves the asset allocation before the device is issued.
Claude closes the onboarding checklist once the laptop is delivered and the account is active.
OutcomeNew starters are typically ready on day one, with fewer missed steps and a clear audit trail for each request.
How we set it up
Free automation audit
We review your service desk volumes, common request types and current tools to find the workflows worth automating first, at no cost.
Connect Claude to Freshservice
We set up the connection using a Freshservice API key, with least-privilege permissions scoped to the workflows you have approved.
Design the end-to-end workflow
We map the process across Freshservice and your other systems, such as Microsoft 365, your CRM or HR platform, defining where people must approve actions.
Test on real past cases
We run the workflow against historical tickets and requests to check accuracy, edge cases and approval routing before anything goes live.
Launch, monitor and train
We go live with monitoring and audit logs in place, then train your agents and managers so they know how to use Claude with confidence.
Who benefits
- IT service desk manager
- Faster ticket handling and fewer manual updates, with a clear audit trail for every change.
- IT operations lead
- Easier asset tracking and reporting, with consistent workflows across sites.
- HR and onboarding coordinators
- Smoother new starter and leaver requests, with fewer missed IT steps.
- Employees raising requests
- A simpler way to report problems and ask for services in everyday language.
Security and control
- Least-privilege API access, limited to the workflows you approve.
- Human approval for consequential actions such as closing major incidents or reassigning assets.
- Complete audit logs of every action Claude takes in Freshservice.
- Regular reviews of permissions and workflow performance after launch.
- Clear escalation paths when Claude cannot confidently complete a request.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host the Claude workflow in their chosen region to align with their data protection obligations. Indian organisations must meet the Digital Personal Data Protection Act, 2023, and we can host in India to support this. Companies in the UAE and Saudi Arabia must follow local data protection laws, and we select the hosting region to meet those requirements. Hosting location is always chosen to meet your legal and contractual needs.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Freshservice MCP server do?
The Freshservice MCP server acts as the secure bridge between Claude and your Freshservice account. It lets Claude read and act on tickets, incidents, service requests and assets using defined permissions. Instead of building a custom integration from scratch, the MCP connection gives Claude a standard way to work with your ITSM data.
Is connecting Claude to Freshservice secure?
Security depends on how the connection is configured. We use an API key with least-privilege access, so Claude only sees and changes what the workflow requires. Consequential actions can require human approval, and every action is logged for audit. We design these controls before anything goes live.
What can Claude do with Freshservice?
Typically, Claude can create incidents, update ticket fields, add notes, manage service requests, look up assets and summarise ticket data. It works from natural language instructions, so agents and managers can ask for what they need in ordinary sentences. The exact actions depend on the permissions you grant.
How long does setup take?
Timelines vary with the number of workflows and the systems involved. A focused first workflow often takes a few weeks, covering audit, connection, design, testing and training. We confirm a realistic schedule during the free automation audit, once we understand your requirements.
Which plan or permissions are needed?
Generally, you need access to your Freshservice account and an API key with permissions matching the workflows you want to automate. The specific plan and permission levels depend on your existing Freshservice setup, so we confirm this during the audit before designing the connection.