by effytech
Automate IT support with AI assistants in Freshservice. Streamline workflows using it helpdesk software and it helpdesk
Connects AI assistants directly to Freshservice to automate IT service ticket management and operations. Handles ticket creation, updates, asset management, and other ITSM tasks through AI interactions.
Freshservice is a community-built MCP server published by effytech that provides AI assistants with tools and capabilities via the Model Context Protocol. Automate IT support with AI assistants in Freshservice. Streamline workflows using it helpdesk software and it helpdesk It is categorized under productivity, developer tools.
You can install Freshservice 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
Freshservice 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
We evaluated Freshservice against two servers with overlapping tools; this profile had the clearer scope statement.
We wired Freshservice into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
I recommend Freshservice for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Freshservice is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Freshservice reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We wired Freshservice into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Useful MCP listing: Freshservice is the kind of server we cite when onboarding engineers to host + tool permissions.
I recommend Freshservice for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Freshservice is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Strong directory entry: Freshservice surfaces stars and publisher context so we could sanity-check maintenance before adopting.
showing 1-10 of 63
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)Generate your Freshservice API key from the admin panel:
Set up your domain and authentication details as shown below
claude_desktop_config.json:"mcpServers": {
"freshservice-mcp": {
"command": "uvx",
"args": [
"freshservice-mcp"
],
"env": {
"FRESHSERVICE_APIKEY": "<YOUR_FRESHSERVICE_APIKEY>",
"FRESHSERVICE_DOMAIN": "<YOUR_FRESHSERVICE_DOMAIN>"
}
}
}
Important: Replace <YOUR_FRESHSERVICE_APIKEY> with your actual API key and <YOUR_FRESHSERVICE_DOMAIN> with your domain (e.g., yourcompany.freshservice.com)
Once configured, you can ask Claude to perform operations like:
Tickets:
Changes:
Other Operations:
For testing purposes, you can start the server manually:
uvx freshservice-mcp --env FRESHSERVICE_APIKEY=<your_api_key> --env FRESHSERVICE_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.