create_ticketLABSCO SUMMARY
The service desk becomes something you can ask.
get_ticket_fields is the tool that makes the rest usable: Freshservice instances are heavily customised, and reading the field definitions first means a ticket gets written in the shape your instance expects rather than rejected. The change tools go all the way to close_change, so this is not a read-only view of the queue.
What it is
A server over the Freshservice API covering the ticket and change queues. Both sides carry read and write tools, and both accept a query string, so finding the records a question is about is a filter rather than a list-and-scan.
What you get
- Tickets created, updated and deleted, with subject, description, source, priority, status and requester email
- Tickets listed with pagination, fetched one at a time by id, or filtered by a query
- The ticket field definitions your instance actually uses
- Change requests created with requester, impact, risk and change type, then updated, closed or deleted
- Changes listed, filtered by query, and fetched by id
- The tasks attached to a change, and notes added to a change record
Requirements
A Freshservice instance and API access to it — every tool is a call against your own Freshservice endpoints, so what it can reach is what that access allows.
Setup effort
Add the configuration to your client
USE CASES
01
Raising a ticket from wherever the problem surfaced
Read the field definitions your instance uses, then file the ticket with priority, status, source and requester already correct instead of leaving them to be fixed later.
02
Finding the tickets a question is about
Ask in the terms the question arrived in — this requester, this priority, still open — and pull the full record for whichever one turns out to matter.
03
Moving a ticket along
Change status, priority or assignment on an existing ticket from the conversation where the decision was made, rather than switching to the desk to record it.
04
Putting a change through
Raise the change with its impact, risk and type, update it as approvals land, and close it when the work is done.
05
Reviewing what changed
List or filter the change queue, open the one in question, and read the tasks hanging off it — the sequence a post-incident review walks.
06
Recording a decision on a change record
Attach a note to the change so the reasoning sits with the record instead of in a chat thread nobody will find again.
16 tools
Listed in project docs. Your client may show a different list.
update_ticketdelete_ticketfilter_ticketsget_ticket_fieldsget_ticketsget_ticket_by_idget_changesfilter_changesget_change_by_idcreate_changeupdate_changeclose_changedelete_changeget_change_taskscreate_change_noteBEFORE YOU INSTALL
What to know first
Tools you get
16 tools named in the project's documentation.
Requires
- uvx on PATH
- FRESHSERVICE_APIKEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"freshservice-mcp": {
"command": "uvx",
"args": [
"freshservice-mcp"
],
"env": {
"FRESHSERVICE_APIKEY": "<YOUR_FRESHSERVICE_APIKEY>",
"FRESHSERVICE_DOMAIN": "<YOUR_FRESHSERVICE_DOMAIN>"
}
}
}
}
