Freshdesk MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FRESHDESK_DOMAIN | Yes | Your Freshdesk domain (e.g., yourcompany.freshdesk.com) | |
| FRESHDESK_API_KEY | Yes | Your Freshdesk 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_ticket_fieldsB | Get ticket fields from Freshdesk. |
| get_ticketsB | Get tickets from Freshdesk with pagination support. |
| create_ticketD | Create a ticket in Freshdesk |
| update_ticketC | Update a ticket in Freshdesk. |
| delete_ticketB | Delete a ticket in Freshdesk. |
| get_ticketC | Get a ticket in Freshdesk. |
| search_ticketsC | Search for tickets in Freshdesk. |
| get_ticket_conversationC | Get a ticket conversation in Freshdesk. |
| create_ticket_replyB | Create a reply to a ticket in Freshdesk. |
| create_ticket_noteC | Create a note for a ticket in Freshdesk. |
| update_ticket_conversationB | Update a conversation for a ticket in Freshdesk. |
| get_agentsC | Get all agents in Freshdesk with pagination support. |
| list_contactsA | List all contacts in Freshdesk with pagination support. |
| get_contactC | Get a contact in Freshdesk. |
| search_contactsC | Search for contacts in Freshdesk. |
| update_contactC | Update a contact in Freshdesk. |
| list_canned_responsesC | List all canned responses in Freshdesk. |
| list_canned_response_foldersA | List all canned response folders in Freshdesk. |
| view_canned_responseC | View a canned response in Freshdesk. |
| create_canned_responseC | Create a canned response in Freshdesk. |
| update_canned_responseC | Update a canned response in Freshdesk. |
| create_canned_response_folderB | Create a canned response folder in Freshdesk. |
| update_canned_response_folderC | Update a canned response folder in Freshdesk. |
| list_solution_articlesC | List all solution articles in Freshdesk. |
| list_solution_foldersD | – |
| list_solution_categoriesA | List all solution categories in Freshdesk. |
| view_solution_categoryC | View a solution category in Freshdesk. |
| create_solution_categoryC | Create a solution category in Freshdesk. |
| update_solution_categoryC | Update a solution category in Freshdesk. |
| create_solution_category_folderC | Create a solution category folder in Freshdesk. |
| view_solution_category_folderC | View a solution category folder in Freshdesk. |
| update_solution_category_folderC | Update a solution category folder in Freshdesk. |
| create_solution_articleC | Create a solution article in Freshdesk. |
| view_solution_articleC | View a solution article in Freshdesk. |
| update_solution_articleC | Update a solution article in Freshdesk. |
| view_agentC | View an agent in Freshdesk. |
| create_agentC | Create an agent in Freshdesk. |
| update_agentC | Update an agent in Freshdesk. |
| search_agentsC | Search for agents in Freshdesk. |
| list_groupsC | List all groups in Freshdesk. |
| create_groupC | Create a group in Freshdesk. |
| view_groupC | View a group in Freshdesk. |
| create_ticket_fieldC | Create a ticket field in Freshdesk. |
| view_ticket_fieldC | View a ticket field in Freshdesk. |
| update_ticket_fieldC | Update a ticket field in Freshdesk. |
| update_groupC | Update a group in Freshdesk. |
| list_contact_fieldsA | List all contact fields in Freshdesk. |
| view_contact_fieldB | View a contact field in Freshdesk. |
| create_contact_fieldC | Create a contact field in Freshdesk. |
| update_contact_fieldC | Update a contact field in Freshdesk. |
| get_field_propertiesC | Get properties of a specific field by name. |
| list_companiesB | List all companies in Freshdesk with pagination support. |
| view_companyC | Get a company in Freshdesk. |
| search_companiesC | Search for companies in Freshdesk. |
| find_company_by_nameA | Find a company by name in Freshdesk. |
| list_company_fieldsA | List all company fields in Freshdesk. |
| view_ticket_summaryC | Get the summary of a ticket in Freshdesk. |
| update_ticket_summaryC | Update the summary of a ticket in Freshdesk. |
| delete_ticket_summaryB | Delete the summary of a ticket in Freshdesk. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_ticket | Create a ticket in Freshdesk |
| create_reply | Create a reply in Freshdesk |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 59 tools
Most tools have distinct purposes targeting specific Freshdesk resources and actions, but there is some ambiguity between 'get_' and 'view_' tools (e.g., get_contact vs. view_agent) and between 'list_' and 'search_' tools (e.g., list_companies vs. search_companies), which could cause confusion in tool selection.
Tool names follow a highly consistent verb_noun pattern throughout, with clear verbs like create, delete, get, list, search, update, and view applied uniformly across resources. There are no deviations in naming conventions, making the set predictable and readable.
With 59 tools, the count is excessive for a typical MCP server, making it heavy and potentially overwhelming for agents. This many tools suggests over-fragmentation of operations that could have been consolidated, such as separate tools for viewing and getting similar resources.
The tool set provides comprehensive CRUD and lifecycle coverage for Freshdesk's core domain, including agents, tickets, contacts, companies, groups, canned responses, solution articles, and fields. There are no obvious gaps, with create, read, update, delete, list, and search operations available for most resources.