MCP server
by effytech
Automate support with Freshdesk! Use AI customer service to manage tickets, improve workflows, and elevate your customer
Connects AI models to Freshdesk's support platform for automated ticket management and customer service operations.
Freshdesk is a community-built MCP server published by effytech that provides AI assistants with tools and capabilities via the Model Context Protocol. Automate support with Freshdesk! Use AI customer service to manage tickets, improve workflows, and elevate your customer It is categorized under developer tools.
You can install Freshdesk in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Freshdesk is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Useful MCP listing: Freshdesk is the kind of server we cite when onboarding engineers to host + tool permissions.
We wired Freshdesk into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Freshdesk is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
According to our notes, Freshdesk benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
We evaluated Freshdesk against two servers with overlapping tools; this profile had the clearer scope statement.
I recommend Freshdesk for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Freshdesk is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
We evaluated Freshdesk against two servers with overlapping tools; this profile had the clearer scope statement.
Freshdesk is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Strong directory entry: Freshdesk surfaces stars and publisher context so we could sanity-check maintenance before adopting.
showing 1-10 of 66
An MCP server implementation that integrates with Freshdesk, enabling AI models to interact with Freshdesk modules and perform various support operations.
The server offers several tools for Freshdesk operations:
create_ticket: Create new support tickets
subject (string, required): Ticket subjectdescription (string, required): Ticket descriptionsource (number, required): Ticket source codepriority (number, required): Ticket priority levelstatus (number, required): Ticket status codeemail (string, optional): Email of the requesterrequester_id (number, optional): ID of the requestercustom_fields (object, optional): Custom fields to set on the ticketadditional_fields (object, optional): Additional top-level fieldsupdate_ticket: Update existing tickets
ticket_id (number, required): ID of the ticket to updateticket_fields (object, required): Fields to updatedelete_ticket: Delete a ticket
ticket_id (number, required): ID of the ticket to deletesearch_tickets: Search for tickets based on criteria
query (string, required): Search query stringget_ticket_fields: Get all ticket fields
get_tickets: Get all tickets
page (number, optional): Page number to fetchper_page (number, optional): Number of tickets per pageget_ticket: Get a single ticket
ticket_id (number, required): ID of the ticket to getget_ticket_conversation: Get conversation for a ticket
ticket_id (number, required): ID of the ticketcreate_ticket_reply: Reply to a ticket
ticket_id (number, required): ID of the ticketbody (string, required): Content of the replycreate_ticket_note: Add a note to a ticket
ticket_id (number, required): ID of the ticketbody (string, required): Content of the noteupdate_ticket_conversation: Update a conversation
conversation_id (number, required): ID of the conversationbody (string, required): Updated contentview_ticket_summary: Get the summary of a ticket
ticket_id (number, required): ID of the ticketupdate_ticket_summary: Update the summary of a ticket
ticket_id (number, required): ID of the ticketbody (string, required): New summary contentdelete_ticket_summary: Delete the summary of a ticket
ticket_id (number, required): ID of the ticketget_agents: Get all agents
page (number, optional): Page numberper_page (number, optional): Number of agents per pageview_agent: Get a single agent
agent_id (number, required): ID of the agentcreate_agent: Create a new agent
agent_fields (object, required): Agent detailsupdate_agent: Update an agent
agent_id (number, required): ID of the agentagent_fields (object, required): Fields to updatesearch_agents: Search for agents
query (string, required): Search querylist_contacts: Get all contacts
page (number, optional): Page numberper_page (number, optional): Contacts per pageget_contact: Get a single contact
contact_id (number, required): ID of the contactsearch_contacts: Search for contacts
query (string, required): Search queryupdate_contact: Update a contact
contact_id (number, required): ID of the contactcontact_fields (object, required): Fields to updatelist_companies: Get all companies
page (number, optional): Page numberper_page (number, optional): Companies per pageview_company: Get a single company
company_id (number, required): ID of the companysearch_companies: Search for companies
query (string, required): Search queryfind_company_by_name: Find a company by name
name (string, required): Company namelist_company_fields: Get all company fields
To install freshdesk_mcp for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @effytech/freshdesk_mcp --client claude
uvx installed (pip install uv or brew install uv)claude_desktop_config.json:"mcpServers": {
"freshdesk-mcp": {
"command": "uvx",
"args": [
"freshdesk-mcp"
],
"env": {
"FRESHDESK_API_KEY": "<YOUR_FRESHDESK_API_KEY>",
"FRESHDESK_DOMAIN": "<YOUR_FRESHDESK_DOMAIN>"
}
}
}
Important Notes:
YOUR_FRESHDESK_API_KEY with your actual Freshdesk API keyYOUR_FRESHDESK_DOMAIN with your Freshdesk domain (e.g., yourcompany.freshdesk.com)Once configured, you can ask Claude to perform operations like:
For testing purposes, you can start the server manually:
uvx freshdesk-mcp --env FRESHDESK_API_KEY=<your_api_key> --env FRESHDESK_DOMAIN=<your_domain>
uvx command is available in your PATHThis MCP server is licensed under the MIT License. See the LICENSE file in the project repository for full details.
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.