MCP server created for Freshservice, allowing AI models to interact with Freshservice modules
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"freshservice-mcp": {
"args": [
"-y",
"@effytech/freshservice_mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A powerful MCP (Model Context Protocol) server implementation that seamlessly integrates with Freshservice, enabling AI models to interact with Freshservice modules and perform various IT service management operations. This integration bridge empowers your AI assistants to manage and resolve IT service tickets, streamlining your support workflow.
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/freshservice_mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
uv vulnerable to arbitrary file deletion through RECORD entries
## Impact Wheel RECORD entries can contain relative paths that traverse outside of the wheel’s installation prefix. In versions 0.11.5 and earlier of uv, these wheels were not rejected on installation and the RECORD was respected without validation on uninstall. uv uses the RECORD to determine files to remove on uninstall. Consequently, a malicious or malformed wheel could induce deletion of arbitrary files outside of the wheel’s installation prefix on uninstall. uv does not use the RECORD fi
uv 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
uv 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**:
uv 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
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in productivity
Persistent memory using a knowledge graph
Dynamic problem-solving through sequential thought chains
mini cli search engine for your docs, knowledge bases, meeting notes, whatever. Tracking current sota approaches while being all local
Official Miro MCP server - Supports context to code and creating diagrams, docs, and data tables.
MCP Security Weekly
Get CVE alerts and security updates for Freshservice_mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A powerful MCP (Model Context Protocol) server implementation that seamlessly integrates with Freshservice, enabling AI models to interact with Freshservice modules and perform various IT service management operations. This integration bridge empowers your AI assistants to manage and resolve IT service tickets, streamlining your support workflow.
This MCP server currently supports operations across a wide range of Freshservice modules:
The server provides a comprehensive toolkit for Freshservice operations:
| Tool | Description | Key Parameters |
|---|---|---|
create_ticket | Create new service tickets | subject, description, source, priority, status, email |
update_ticket | Update existing tickets | ticket_id, updates |
delete_ticket | Remove tickets | ticket_id |
filter_tickets | Find tickets matching criteria | query |
get_ticket_fields | Retrieve ticket field definitions | None |
get_tickets | List all tickets with pagination | page, per_page |
get_ticket_by_id | Retrieve single ticket details | ticket_id |
| Tool | Description | Key Parameters |
|---|---|---|
get_changes | List all changes with pagination | page, per_page, query |
filter_changes | Filter changes with advanced queries | query, page, per_page |
get_change_by_id | Retrieve single change details | change_id |
create_change | Create new change request | requester_id, subject, description, priority, impact, status, risk, change_type |
update_change | Update existing change | change_id, change_fields |
close_change | Close change with result explanation | change_id, change_result_explanation |
delete_change | Remove change | change_id |
get_change_tasks | Get tasks for a change | change_id |
create_change_note | Add note to change | change_id, body |
When using get_changes or filter_changes with the query parameter, the query string must be wrapped in double quotes for the Freshservice API to work correctly:
✅ CORRECT: "status:3", "approval_status:1 AND status:<6"
❌ WRONG: status:3 (will cause 500 Internal Server Error)
Common Query Examples:
"status:3" - Changes awaiting approval"approval_status:1" - Approved changes"approval_status:1 AND status:<6" - Approved changes that are not closed"planned_start_date:>'2025-07-14'" - Changes starting after specific date"status:3 AND priority:1" - High priority changes awaiting approvalTo install freshservice_mcp automatically via Smithery:
npx -y @smithery/cli install @effytech/freshservice_mcp --client claude
uvx installed (pip install uv or brew install uv)