Freshservice MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FRESHSERVICE_DOMAIN | Yes | Your Freshservice subdomain (the part before .freshservice.com) | |
| FRESHSERVICE_API_KEY | Yes | Your Freshservice API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_ticketsC | List Freshservice tickets with optional filters |
| get_ticketB | Get details of a specific Freshservice ticket |
| create_ticketC | Create a new Freshservice ticket |
| update_ticketC | Update an existing Freshservice ticket |
| delete_ticketC | Delete a Freshservice ticket (moves to trash) |
| reply_to_ticketC | Reply to a Freshservice ticket |
| add_note_to_ticketC | Add a note to a Freshservice ticket |
| get_ticket_conversationsB | Get all conversations (replies and notes) for a ticket |
| search_ticketsC | Search/filter Freshservice tickets using a query string |
| list_assetsC | List Freshservice assets/configuration items |
| get_assetC | Get details of a specific asset |
| create_assetC | Create a new Freshservice asset |
| update_assetC | Update an existing Freshservice asset |
| delete_assetC | Delete a Freshservice asset |
| list_requestersC | List Freshservice requesters (end users) |
| get_requesterC | Get details of a specific requester |
| list_agentsC | List Freshservice agents (support staff) |
| get_agentC | Get details of a specific agent |
| list_groupsC | List Freshservice agent groups |
| get_groupB | Get details of a specific agent group |
| list_departmentsC | List Freshservice departments |
| get_departmentB | Get details of a specific department |
| list_ticket_tasksC | List all tasks for a Freshservice ticket |
| get_ticket_taskB | Get details of a specific task on a ticket |
| create_ticket_taskC | Create a new task on a Freshservice ticket |
| update_ticket_taskC | Update a task on a Freshservice ticket |
| delete_ticket_taskC | Delete a task from a Freshservice ticket |
| list_time_entriesC | List time entries for a Freshservice ticket |
| create_time_entryB | Log time spent on a Freshservice ticket |
| update_time_entryC | Update a time entry on a Freshservice ticket |
| delete_time_entryC | Delete a time entry from a Freshservice ticket |
| list_changesC | List Freshservice change requests |
| get_changeC | Get details of a specific change request |
| create_changeC | Create a new Freshservice change request |
| update_changeC | Update an existing Freshservice change request |
| delete_changeC | Delete a Freshservice change request |
| list_problemsC | List Freshservice problems |
| get_problemB | Get details of a specific Freshservice problem |
| create_problemC | Create a new Freshservice problem |
| update_problemC | Update an existing Freshservice problem |
| delete_problemB | Delete a Freshservice problem |
| list_service_catalog_itemsC | List items in the Freshservice service catalog |
| get_service_catalog_itemC | Get details of a specific service catalog item |
| place_service_requestC | Place a service request from the Freshservice catalog |
| list_solution_categoriesC | List knowledge base categories in Freshservice |
| get_solution_categoryC | Get details of a knowledge base category |
| list_solution_foldersC | List folders in a knowledge base category |
| get_solution_folderC | Get details of a knowledge base folder |
| list_solution_articlesC | List articles in a knowledge base folder |
| get_solution_articleC | Get a knowledge base article with full content |
| create_solution_articleC | Create a new knowledge base article |
| update_solution_articleC | Update an existing knowledge base article |
| delete_solution_articleC | Delete a knowledge base article |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 53 tools
Most tools have clearly distinct purposes targeting specific resources and actions (e.g., create_ticket vs. update_ticket vs. delete_ticket). However, some potential overlap exists between list_tickets and search_tickets, and between get_ticket and get_ticket_conversations, which could cause minor confusion for agents about which to use in certain scenarios.
Tool names follow a highly consistent verb_noun pattern throughout (e.g., create_ticket, list_agents, get_asset, update_problem, delete_change). All tools use snake_case with clear, predictable naming conventions, making them easily readable and systematic.
With 53 tools, the count is excessively high for a single server, likely overwhelming for agents to navigate efficiently. While Freshservice is a comprehensive ITSM platform, this many tools suggests over-fragmentation of operations that could be consolidated or scoped more narrowly.
The tool set provides complete CRUD/lifecycle coverage across all key Freshservice domains (tickets, assets, changes, problems, solutions, agents, requesters, etc.). It includes all essential operations from listing and getting to creating, updating, and deleting, with no obvious gaps for core workflows.