Skip to main content
Glama
Freshservice MCP Server
by tannertm0

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

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-mcp

Konfigurieren 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

FRESHSERVICE_DOMAIN

Ja

Ihre Freshservice-Subdomain (z. B. ihrefirma für ihrefirma.freshservice.com)

FRESHSERVICE_API_KEY

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

list_tickets

Tickets mit Filtern auflisten (Status, Priorität, Anfragender, Datum)

get_ticket

Vollständige Ticketdetails abrufen

create_ticket

Ein neues Ticket erstellen

update_ticket

Ticketfelder aktualisieren (Status, Priorität, Zuweisung usw.)

delete_ticket

Ein Ticket löschen (verschiebt es in den Papierkorb)

reply_to_ticket

Auf ein Ticket antworten

add_note_to_ticket

Eine öffentliche oder private Notiz hinzufügen

get_ticket_conversations

Alle Antworten und Notizen anzeigen

search_tickets

Tickets mit Abfragesyntax filtern

Assets

Tool

Beschreibung

list_assets

Alle Assets/CIs auflisten

get_asset

Asset-Details mit benutzerdefinierten Feldern abrufen

create_asset

Ein neues Asset registrieren

update_asset

Asset-Felder aktualisieren

delete_asset

Ein Asset entfernen

Personen & Organisation

Tool

Beschreibung

list_requesters / get_requester

Endbenutzer

list_agents / get_agent

Support-Mitarbeiter

list_groups / get_group

Agentengruppen mit Mitgliedern

list_departments / get_department

Abteilungen

Ticket-Aufgaben

Tool

Beschreibung

list_ticket_tasks

Unteraufgaben eines Tickets auflisten

get_ticket_task

Aufgabendetails abrufen

create_ticket_task

Eine Aufgabe zu einem Ticket hinzufügen

update_ticket_task

Aufgabenstatus/Zuweisung aktualisieren

delete_ticket_task

Eine Aufgabe entfernen

Zeiteinträge

Tool

Beschreibung

list_time_entries

Protokollierte Zeit für ein Ticket anzeigen

create_time_entry

Aufgewendete Zeit protokollieren

update_time_entry

Einen Zeiteintrag ändern

delete_time_entry

Einen Zeiteintrag entfernen

Änderungen

Tool

Beschreibung

list_changes

Änderungsanfragen auflisten

get_change

Änderungsdetails abrufen (Typ, Risiko, Zeitplan)

create_change

Eine Änderungsanfrage erstellen

update_change

Änderungsfelder aktualisieren

delete_change

Eine Änderung löschen

Probleme

Tool

Beschreibung

list_problems

Problem-Datensätze auflisten

get_problem

Problemdetails abrufen

create_problem

Einen Problem-Datensatz erstellen

update_problem

Problemfelder aktualisieren

delete_problem

Ein Problem löschen

Servicekatalog

Tool

Beschreibung

list_service_catalog_items

Verfügbare Services durchsuchen

get_service_catalog_item

Servicedetails und erforderliche Felder abrufen

place_service_request

Eine Serviceanfrage einreichen

Wissensdatenbank

Tool

Beschreibung

list_solution_categories / get_solution_category

KB-Kategorien durchsuchen

list_solution_folders / get_solution_folder

KB-Ordner durchsuchen

list_solution_articles / get_solution_article

Artikel lesen

create_solution_article

Einen neuen Artikel schreiben

update_solution_article

Einen Artikel bearbeiten

delete_solution_article

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 date

Entwicklung

git clone https://github.com/tannertm0/freshservice-mcp.git
cd freshservice-mcp
npm install
npm test

Lizenz

MIT

Available Tools

53 tools
add_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

    B3.2/5.0

    Scored across 53 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness5/5

    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

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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
    • F
      license
      Not graded
      quality
      D
      maintenance
      Integrates 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
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides 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
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      36
      2
      MIT