MCP server created for Freshdesk, allowing AI models to interact with Freshdesk modules
{
"mcpServers": {
"freshdesk-mcp": {
"args": [
"-y",
"@effytech/freshdesk_mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An MCP server implementation that integrates with Freshdesk, enabling AI models to interact with Freshdesk modules and perform various support operations.
Is it safe?
No known CVEs for @effytech/freshdesk_mcp. 3 previously resolved.
No authentication — any process on your machine can connect.
MIT. View license →
Is it maintained?
Last commit 184 days ago. 53 stars.
Will it work with my client?
Transport: stdio, http. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@effytech/freshdesk_mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
No open vulnerabilities. 3 fixed CVEs.
CVE-2025-13327Fixeduv allows ZIP payload obfuscation through parsing differentials
### Impact In versions 0.9.5 and earlier of uv, ZIP archives were handled in a manner that enabled two parsing differentials against other components of the Python packaging ecosystem: 1. Central directory entries in a ZIP archive can contain comment fields. However, uv would assume that these fields were not present, since they aren't widely used. Consequently, a ZIP archive could be constructed where uv would interpret the contents of a central directory comment field as ZIP control structur
GHSA-w476-p2h3-79g9Fixeduv has differential in tar extraction with PAX headers
### Impact In versions 0.9.4 and earlier of uv, tar archives containing PAX headers with file size overrides were not handled properly. As a result, an attacker could contrive a source distribution (as a tar archive) that would extract differently when installed via uv versus other Python package installers. The underlying parsing differential here originates with astral-tokio-tar, which disclosed this vulnerability as CVE-2025-62518. In practice, the impact of this vulnerability is **low**:
CVE-2025-54368Fixeduv allows ZIP payload obfuscation through parsing differentials
## Impact In versions 0.8.5 and earlier of uv, remote ZIP archives were handled in a streamwise fashion, and file entries were not reconciled against the archive's central directory. This enabled two parser differentials against other Python package installers: 1. An attacker could contrive a ZIP archive that would extract with legitimate contents on some package installers, and malicious contents on others due to multiple local file entries. The attacker could choose which installer to target
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Manage Supabase projects — databases, auth, storage, and edge functions
Dynamic problem-solving through sequential thought chains
A Model Context Protocol server for searching and analyzing arXiv papers
Query and manage PostgreSQL databases directly from AI assistants
MCP Security Weekly
Get CVE alerts and security updates for Freshdesk_mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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