Freshservice MCP Server
freshservice-mcp
Ein MCP-Server (Model Context Protocol), der KI-Assistenten mit Ihrer Freshservice ITSM-Instanz verbindet. Verwalten Sie Tickets, Assets, Änderungen, Probleme, den Servicekatalog, die Wissensdatenbank und mehr mittels natürlicher Sprache.
Funktionen
53 Tools in 9 Kategorien:
Kategorie | Tools | Beschreibung |
Tickets | 9 | Auflisten, abrufen, erstellen, aktualisieren, löschen, antworten, Notizen hinzufügen, Konversationen, suchen |
Assets | 5 | Auflisten, abrufen, erstellen, aktualisieren, löschen |
Personen | 8 | Anfragende, Agenten, Gruppen, Abteilungen (auflisten + abrufen) |
Ticket-Aufgaben | 5 | Unteraufgaben für Tickets auflisten, abrufen, erstellen, aktualisieren, löschen |
Zeiteinträge | 4 | Zeitprotokolle auflisten, erstellen, aktualisieren, löschen |
Änderungen | 5 | Änderungsanfragen auflisten, abrufen, erstellen, aktualisieren, löschen |
Probleme | 5 | Problem-Datensätze auflisten, abrufen, erstellen, aktualisieren, löschen |
Servicekatalog | 3 | Katalogelemente durchsuchen, Details abrufen, Serviceanfragen stellen |
Wissensdatenbank | 9 | Kategorien, Ordner, Artikel (vollständiges CRUD) |
Related MCP server: Service Desk Plus MCP Server
Schnellstart
Voraussetzungen
Node.js 18+
Ein Freshservice-Konto mit API-Zugriff
Ihr Freshservice-API-Schlüssel (Profilsymbol > Profileinstellungen > API-Schlüssel im rechten Bereich)
Installation via npx (empfohlen)
Keine Installation erforderlich. Konfigurieren Sie Ihren MCP-Client für die Ausführung von:
{
"mcpServers": {
"freshservice": {
"command": "npx",
"args": ["-y", "freshservice-mcp"],
"env": {
"FRESHSERVICE_DOMAIN": "yourcompany",
"FRESHSERVICE_API_KEY": "your-api-key"
}
}
}
}Global installieren
npm install -g freshservice-mcpKonfigurieren Sie dann Ihren MCP-Client:
{
"mcpServers": {
"freshservice": {
"command": "freshservice-mcp",
"env": {
"FRESHSERVICE_DOMAIN": "yourcompany",
"FRESHSERVICE_API_KEY": "your-api-key"
}
}
}
}Aus dem Quellcode installieren
git clone https://github.com/tannertm0/freshservice-mcp.git
cd freshservice-mcp
npm install{
"mcpServers": {
"freshservice": {
"command": "node",
"args": ["/path/to/freshservice-mcp/src/index.js"],
"env": {
"FRESHSERVICE_DOMAIN": "yourcompany",
"FRESHSERVICE_API_KEY": "your-api-key"
}
}
}
}Konfiguration
Variable | Erforderlich | Beschreibung |
| Ja | Ihre Freshservice-Subdomain (z. B. |
| Ja | Ihr Freshservice-API-Schlüssel |
MCP-Client-Einrichtung
Claude Desktop - Hinzufügen zu ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) oder %APPDATA%\Claude\claude_desktop_config.json (Windows)
Claude Code - Führen Sie claude mcp add freshservice -- npx -y freshservice-mcp aus und setzen Sie dann die Umgebungsvariablen
Cursor / VS Code - Fügen Sie es gemäß der Dokumentation Ihres Editors zu Ihren MCP-Einstellungen hinzu
Verfügbare Tools
Tickets
Tool | Beschreibung |
| Tickets mit Filtern auflisten (Status, Priorität, Anfragender, Datum) |
| Vollständige Ticketdetails abrufen |
| Ein neues Ticket erstellen |
| Ticketfelder aktualisieren (Status, Priorität, Zuweisung usw.) |
| Ein Ticket löschen (verschiebt es in den Papierkorb) |
| Auf ein Ticket antworten |
| Eine öffentliche oder private Notiz hinzufügen |
| Alle Antworten und Notizen anzeigen |
| Tickets mit Abfragesyntax filtern |
Assets
Tool | Beschreibung |
| Alle Assets/CIs auflisten |
| Asset-Details mit benutzerdefinierten Feldern abrufen |
| Ein neues Asset registrieren |
| Asset-Felder aktualisieren |
| Ein Asset entfernen |
Personen & Organisation
Tool | Beschreibung |
| Endbenutzer |
| Support-Mitarbeiter |
| Agentengruppen mit Mitgliedern |
| Abteilungen |
Ticket-Aufgaben
Tool | Beschreibung |
| Unteraufgaben eines Tickets auflisten |
| Aufgabendetails abrufen |
| Eine Aufgabe zu einem Ticket hinzufügen |
| Aufgabenstatus/Zuweisung aktualisieren |
| Eine Aufgabe entfernen |
Zeiteinträge
Tool | Beschreibung |
| Protokollierte Zeit für ein Ticket anzeigen |
| Aufgewendete Zeit protokollieren |
| Einen Zeiteintrag ändern |
| Einen Zeiteintrag entfernen |
Änderungen
Tool | Beschreibung |
| Änderungsanfragen auflisten |
| Änderungsdetails abrufen (Typ, Risiko, Zeitplan) |
| Eine Änderungsanfrage erstellen |
| Änderungsfelder aktualisieren |
| Eine Änderung löschen |
Probleme
Tool | Beschreibung |
| Problem-Datensätze auflisten |
| Problemdetails abrufen |
| Einen Problem-Datensatz erstellen |
| Problemfelder aktualisieren |
| Ein Problem löschen |
Servicekatalog
Tool | Beschreibung |
| Verfügbare Services durchsuchen |
| Servicedetails und erforderliche Felder abrufen |
| Eine Serviceanfrage einreichen |
Wissensdatenbank
Tool | Beschreibung |
| KB-Kategorien durchsuchen |
| KB-Ordner durchsuchen |
| Artikel lesen |
| Einen neuen Artikel schreiben |
| Einen Artikel bearbeiten |
| Einen Artikel entfernen |
Beispiel-Prompts
Sobald die Konfiguration abgeschlossen ist, können Sie Ihren KI-Assistenten Dinge fragen wie:
"Zeige mir alle offenen P1-Tickets"
"Erstelle ein Ticket für den Drucker im 3. Stock, der offline ist"
"Welche Assets sind John Smith zugewiesen?"
"Füge eine private Notiz zu Ticket #5678 hinzu, dass wir auf den Anbieter warten"
"Erstelle eine Änderungsanfrage für das Firewall-Upgrade, das für nächsten Dienstag geplant ist"
"Durchsuche die Wissensdatenbank nach Anweisungen zur VPN-Einrichtung"
"Protokolliere 2 Stunden für Ticket #1234 zur Behebung des Netzwerkproblems"
"Zeige mir alle offenen Probleme und deren Auswirkungsstufen"
"Stelle eine neue Laptop-Anfrage aus dem Servicekatalog"
Suchabfrage-Syntax
Das Tool search_tickets verwendet die Filter-Abfragesyntax von Freshservice:
"priority:4 AND status:2" - Urgent + Open tickets
"group_id:12345" - Tickets assigned to a specific group
"agent_id:67890" - Tickets assigned to a specific agent
"created_at:>'2024-01-01'" - Tickets created after a dateEntwicklung
git clone https://github.com/tannertm0/freshservice-mcp.git
cd freshservice-mcp
npm install
npm testLizenz
MIT
Available Tools
53 toolsadd_note_to_ticketC
Add a note to a Freshservice ticket
Inputs: ticket_id (required), body (required), private.
create_assetC
Create a new Freshservice asset
Inputs: name (required), asset_type_id (required), description, user_id, +3 more.
create_changeC
Create a new Freshservice change request
Inputs: subject (required), description (required), requester_id (required), priority, +9 more.
create_problemC
Create a new Freshservice problem
Inputs: subject (required), description (required), requester_id (required), priority, +7 more.
create_solution_articleC
Create a new knowledge base article
Inputs: title (required), description (required), folder_id (required), status, +1 more.
create_ticketC
Create a new Freshservice ticket
Inputs: subject (required), description (required), email, requester_id, +10 more.
create_ticket_taskC
Create a new task on a Freshservice ticket
Inputs: ticket_id (required), title (required), description, status, +3 more.
create_time_entryB
Log time spent on a Freshservice ticket
Inputs: ticket_id (required), agent_id (required), time_spent (required), note, +2 more.
delete_assetC
Delete a Freshservice asset
Inputs: display_id (required).
delete_changeC
Delete a Freshservice change request
Inputs: change_id (required).
delete_problemB
Delete a Freshservice problem
Inputs: problem_id (required).
delete_solution_articleC
Delete a knowledge base article
Inputs: article_id (required).
delete_ticketC
Delete a Freshservice ticket (moves to trash)
Inputs: ticket_id (required).
delete_ticket_taskC
Delete a task from a Freshservice ticket
Inputs: ticket_id (required), task_id (required).
delete_time_entryC
Delete a time entry from a Freshservice ticket
Inputs: ticket_id (required), entry_id (required).
get_agentC
Get details of a specific agent
Inputs: agent_id (required).
get_assetC
Get details of a specific asset
Inputs: display_id (required).
get_changeC
Get details of a specific change request
Inputs: change_id (required).
get_departmentB
Get details of a specific department
Inputs: department_id (required).
get_groupB
Get details of a specific agent group
Inputs: group_id (required).
get_problemB
Get details of a specific Freshservice problem
Inputs: problem_id (required).
get_requesterC
Get details of a specific requester
Inputs: requester_id (required).
get_service_catalog_itemC
Get details of a specific service catalog item
Inputs: item_id (required).
get_solution_articleC
Get a knowledge base article with full content
Inputs: article_id (required).
get_solution_categoryC
Get details of a knowledge base category
Inputs: category_id (required).
get_solution_folderC
Get details of a knowledge base folder
Inputs: folder_id (required).
get_ticketB
Get details of a specific Freshservice ticket
Inputs: ticket_id (required).
get_ticket_conversationsB
Get all conversations (replies and notes) for a ticket
Inputs: ticket_id (required).
get_ticket_taskB
Get details of a specific task on a ticket
Inputs: ticket_id (required), task_id (required).
list_agentsC
List Freshservice agents (support staff)
Inputs: page, per_page, email, active.
list_assetsC
List Freshservice assets/configuration items
Inputs: page, per_page.
list_changesC
List Freshservice change requests
Inputs: page, per_page, filter, order_by, +1 more.
list_departmentsC
List Freshservice departments
Inputs: page, per_page.
list_groupsC
List Freshservice agent groups
Inputs: page, per_page.
list_problemsC
List Freshservice problems
Inputs: page, per_page, order_by, order_type.
list_requestersC
List Freshservice requesters (end users)
Inputs: page, per_page, email.
list_service_catalog_itemsC
List items in the Freshservice service catalog
Inputs: page, per_page.
list_solution_articlesC
List articles in a knowledge base folder
Inputs: folder_id (required), page, per_page.
list_solution_categoriesC
List knowledge base categories in Freshservice
Inputs: page, per_page.
list_solution_foldersC
List folders in a knowledge base category
Inputs: category_id (required), page, per_page.
list_ticketsC
List Freshservice tickets with optional filters
Inputs: page, per_page, filter, requester_id, +4 more.
list_ticket_tasksC
List all tasks for a Freshservice ticket
Inputs: ticket_id (required).
list_time_entriesC
List time entries for a Freshservice ticket
Inputs: ticket_id (required).
place_service_requestC
Place a service request from the Freshservice catalog
Inputs: item_id (required), quantity, email, custom_fields.
reply_to_ticketC
Reply to a Freshservice ticket
Inputs: ticket_id (required), body (required), cc_emails, bcc_emails.
search_ticketsC
Search/filter Freshservice tickets using a query string
Inputs: query (required).
update_assetC
Update an existing Freshservice asset
Inputs: display_id (required), name, description, user_id, +3 more.
update_changeC
Update an existing Freshservice change request
Inputs: change_id (required), subject, description, priority, +8 more.
update_problemC
Update an existing Freshservice problem
Inputs: problem_id (required), subject, description, priority, +6 more.
update_solution_articleC
Update an existing knowledge base article
Inputs: article_id (required), title, description, status, +1 more.
update_ticketC
Update an existing Freshservice ticket
Inputs: ticket_id (required), subject, description, priority, +7 more.
update_ticket_taskC
Update a task on a Freshservice ticket
Inputs: ticket_id (required), task_id (required), title, description, +4 more.
update_time_entryC
Update a time entry on a Freshservice ticket
Inputs: ticket_id (required), entry_id (required), time_spent, note, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 53 tools
Most tools have clearly distinct purposes targeting specific resources and actions (e.g., create_ticket vs. update_ticket vs. delete_ticket). However, some potential overlap exists between list_tickets and search_tickets, and between get_ticket and get_ticket_conversations, which could cause minor confusion for agents about which to use in certain scenarios.
Tool names follow a highly consistent verb_noun pattern throughout (e.g., create_ticket, list_agents, get_asset, update_problem, delete_change). All tools use snake_case with clear, predictable naming conventions, making them easily readable and systematic.
With 53 tools, the count is excessively high for a single server, likely overwhelming for agents to navigate efficiently. While Freshservice is a comprehensive ITSM platform, this many tools suggests over-fragmentation of operations that could be consolidated or scoped more narrowly.
The tool set provides complete CRUD/lifecycle coverage across all key Freshservice domains (tickets, assets, changes, problems, solutions, agents, requesters, etc.). It includes all essential operations from listing and getting to creating, updating, and deleting, with no obvious gaps for core workflows.
Maintenance
Related MCP Connectors
Manage tickets, run agents and workflows, query tables, and search workspace knowledge.
AI-native ITSM and ESM platform. resolve IT and HR requests inside Slack and Teams.
Search, reply, tag, assign and report on ThriveDesk help desk conversations from your AI assistant.
Read tickets, contacts, companies, agents and groups; create, update and reply to tickets.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI models to interact with Freshservice IT service management platform, allowing automated ticket management, change requests, asset tracking, and solution article operations through natural language commands.MIT
- FlicenseNot gradedqualityDmaintenanceIntegrates with Service Desk Plus Cloud API to enable AI assistants perform CRUD operations on service desk entities, including request management, technician management, and email communication.4-
- AlicenseNot gradedqualityBmaintenanceProvides AI assistants with structured access to the Freshdesk customer support platform, including tickets, contacts, companies, agents, groups, knowledge base, and SLA configuration. Features decision-tree navigation and destructive-action guardrails.Apache 2.0
- AlicenseAqualityCmaintenanceEnables AI models to perform IT service management operations on Freshservice, including managing tickets, changes, problems, releases, assets, projects, and more through a set of MCP tools.362MIT