Freshdesk MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FRESHDESK_DOMAIN | Yes | Your Freshdesk subdomain (e.g., mycompany for mycompany.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
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 |
|---|---|
| get_ticketA | Fetch complete ticket details from Freshdesk including conversations, attachments, time entries, and satisfaction ratings. Accepts a ticket URL or ID. |
| search_ticketsB | Search Freshdesk tickets by text query. Can filter by status and priority. |
| get_agent_ticketsB | Get tickets assigned to a specific Freshdesk agent by name. Supports partial name matching. |
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 3 tools
Each tool targets a distinct operation: fetching by agent, fetching by ID/URL, and searching by text query. There is no overlap in purpose.
All tool names follow a consistent verb_noun pattern using snake_case (get_agent_tickets, get_ticket, search_tickets).
Three tools is on the low side but still within the typical 3-15 range and each tool serves a clear read-focused purpose for the domain.
Only read operations are covered; missing create, update, and delete functionalities that are essential for managing tickets in a CRM system.