Freshdesk MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STRICT_MODE | No | Set to 'True' to disable destructive tools | |
| JWT_SECRET_KEY | No | Secret key for JWT authentication (used in secure network mode) | |
| ALLOWED_CLIENTS | No | Comma-separated list of agent credentials for JWT auth (format: agent1:pass123,agent2:secure456) | |
| 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_ticketsC | List tickets in Freshdesk. Optionally filter by requester email. |
| get_ticketB | Get detailed information about a specific ticket by ID. |
| create_ticketB | Create a new Freshdesk ticket. Priority: 1=Low, 2=Medium, 3=High, 4=Urgent. Status: 2=Open, 3=Pending, 4=Resolved, 5=Closed. |
| update_ticketC | Update a ticket's status or priority. |
| delete_ticketC | Delete a specific ticket. |
| reply_ticketC | Reply to an existing ticket. |
| add_noteC | Add a note to a ticket. private=True means it is an internal note. |
| list_conversationsB | Fetch all replies and notes associated with a ticket. |
| create_outbound_emailC | Create and send an outbound email from Freshdesk. Supports cc, bcc, tags, and custom fields. |
| search_contactsB | Find a contact by email, phone, or mobile. |
| get_contactB | Retrieve contact details by ID. |
| create_contactC | Create a new customer contact. |
| update_contactC | Update an existing contact's details. |
| get_companyC | Retrieve company details by ID. |
| create_companyC | Create a new company. |
| list_agentsB | List support agents. Optionally filter by email. |
| get_agentC | Get specific agent details by ID. |
| search_solution_articlesC | Search for knowledge base articles by keyword. |
| get_solution_articleC | Retrieve the content of a specific 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 19 tools
Each tool targets a distinct resource and action. While add_note, reply_ticket, and create_outbound_email all relate to ticket communication, their purposes are clearly separated: notes, replies, and outbound emails respectively. No two tools could be easily confused.
All tool names follow a consistent verb_noun pattern in snake_case, such as create_ticket, get_contact, list_agents. The verbs are consistently chosen (create, get, list, update, delete, search, reply, add) and the nouns are singular or plural as appropriate.
With 19 tools, the server is slightly above the ideal range of 3-15, but each tool serves a distinct and necessary function within the Freshdesk domain. The count is justifiable given the variety of entities (tickets, contacts, companies, agents, knowledge base) and operations.
The tool set provides comprehensive coverage for tickets (CRUD, notes, replies, conversations, outbound emails). Contacts and companies have create, read, and update operations but lack delete and listing capabilities. Knowledge base supports search and retrieval but not curation. Overall, core workflows are well-supported with minor gaps.