MCP.Market

InvGate Service Desk MCP server

by tracegazer·io.github.tracegazer/invgate-service-desk-mcp·v0.2.0·3 stars
No reviews yet

InvGate Service Desk MCP: 96 tools/11 domains, 3-tier access (none/support/full), OTel.

B75/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B75/100

full report

Adoption
New

3 stars

Reviews

Write one

Nobody has reviewed InvGate Service Desk yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

InvGate Service Desk tools (96, 10 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • accept_incident_approval

    Accept an approval.

  • accept_incident_solution

    Accept the solution of a request, with a rating.

  • add_incident_approval_voter

    Add a voter to an approval.

  • add_incident_collaborator

    Request collaboration from one or more users on a request.

  • add_incident_comment

    Add a reply/comment to a request.

  • add_incident_observer

    Add one or more users as observers of a request.

  • cancel_incidentwrite action

    Cancel a request.

  • cancel_incident_approvalwrite action

    Cancel an approval.

  • create_incidentwrite action

    Create a new request (ticket).

  • create_incident_spontaneous_approvalwrite action

    Create a spontaneous approval on a request.

  • create_kb_articlewrite action

    Create a Knowledge Base article.

  • delete_incident_custom_fieldwrite action

    Delete the value of a custom field on a request.

  • delete_kb_articlewrite action

    Delete a Knowledge Base article by ID.

  • delete_time_entrywrite action

    Delete a time tracking entry from a request.

  • find_users

    Search users by username, email, phone number or employee number.

  • get_breaking_news

    Get a single Breaking News announcement by ID.

  • get_breaking_news_status

    Get the updates of a Breaking News announcement.

  • get_cis_by_id

    Get CIs by their internal IDs and inventory source ID.

  • get_custom_field_config

    Get the configuration of a custom field by UID.

  • get_custom_field_list_config

    Get the configuration of a list-type custom field.

  • get_custom_field_list_options

    Get the options of a list-type custom field.

  • get_custom_field_tree_options

    Get the options structure of a tree-type custom field.

  • get_incident

    Get a single incident (request) by its ID.

  • get_incident_comments

    Get the replies/comments of a given incident.

  • get_kb_article_attachments

    List the attachments of a Knowledge Base article.

  • get_kb_articles_by_ids

    Get Knowledge Base articles by their IDs.

  • get_kb_categories_by_ids

    Get Knowledge Base categories by their IDs.

  • get_linked_assets_counters

    Get counters of linked assets from a given starting point.

  • get_linked_cis_counters

    Get counters of incidents per status for CIs from a given starting point.

  • get_starting_fields_by_category

    List the custom fields applicable to a category at request creation.

  • get_user

    Get a single user by ID.

  • get_user_groups

    Get the groups, companies, helpdesks and locations for the given users.

  • get_workflow_field_list_values

    Get current values of a list-type field in a workflow instance.

  • get_workflow_initial_fields

    List the initial fields needed to create a request from a workflow.

  • get_workflow_process

    Get workflow process info with version history (or one by ID).

  • link_incident

    Link a request to one or more other requests.

  • link_incident_to_external_entity

    Link a request to an external entity.

  • list_breaking_news

    List all Breaking News announcements.

  • list_breaking_news_statuses

    List the possible statuses of Breaking News (or one by ID).

  • list_breaking_news_types

    List the importance types of Breaking News (or one by ID).

  • list_categories

    List incident categories. Hierarchical via parent_category_id. Supports search.

  • list_companies

    List active companies, optionally filtered by ID, name or external ID.

  • list_company_groups

    List the user groups related to a company.

  • list_company_members

    List the members of a company (optionally check one user).

  • list_company_observers

    List companies and their observers (optionally filtered by IDs).

  • list_custom_field_types

    List supported custom field types (type code -> description).

  • list_custom_fields

    List all active custom field definitions.

  • list_custom_fields_by_category

    List the custom fields related to a category.

  • list_group_members

    List the members of a group (optionally check one user's membership).

  • list_groups

    List active groups, or one in particular by ID or name.

  • list_helpdesk_levels

    List active help desk levels, or one in particular by ID.

  • list_helpdesk_observers

    List help desks and their observers (optionally filtered by IDs).

  • list_helpdesks

    List active help desks, or one in particular by ID or name.

  • list_helpdesks_and_levels

    List help desks together with their levels, or one by ID.

  • list_incident_types

    List incident types (e.g. Incident, Service Request, Problem, Change).

  • list_incidents_by_agent

    List incidents assigned to an agent (by id, email or username).

  • list_incidents_by_asset

    List the requests related to an asset.

  • list_incidents_by_cis

    List the requests linked to CIs (by source ID and CI IDs).

  • list_incidents_by_customer

    List open incidents from a customer (by id, email or username).

  • list_incidents_by_helpdesk

    List open incidents in a help desk (or several help desk IDs).

  • list_incidents_by_status

    List open incidents matching a status (or several status IDs).

  • list_kb_articles

    List Knowledge Base articles with their properties.

  • list_kb_articles_by_category

    List articles in a category (visibility: 1=public).

  • list_kb_categories

    List all Knowledge Base categories.

  • list_level_observers

    List help desk levels and their observers (optionally filtered by IDs).

  • list_location_members

    List the members of a location (optionally check one user).

  • list_location_observers

    List locations and their observers (optionally filtered by IDs).

  • list_locations

    List active locations, or one in particular by ID.

  • list_priorities

    List incident priorities (e.g. Low, Medium, High, Urgent, Critical).

  • list_requests_related_to_assets

    List the requests related to assets (by source ID and asset IDs).

  • list_shared_custom_fields

    List all active shared custom field definitions.

  • list_sources

    List incident sources (e.g. Portal, Email, Phone, API).

  • list_statuses

    List incident statuses.

  • list_time_tracking

    List time tracking entries for a request or within a date interval (provide request_id or from_date; dates are ISO-8601).

  • list_time_tracking_categories

    List time tracking categories (or one by ID), including cost_per_hour.

  • list_trigger_executions

    List each time a specific trigger was executed.

  • list_triggers

    List the automation triggers, or one in particular by ID.

  • list_users

    List users, optionally filtered to specific IDs.

  • log_time

    Log time on a request (from/to are epoch timestamps; from defaults to now). For category_id, first call list_time_tracking_categories and use the matching numeric id rather than guessing.

  • promote_incident_to_major

    Promote a request to a major incident.

  • reassign_incident

    Reassign a request to a help desk and/or agent.

  • reject_incident

    Reject a request.

  • reject_incident_approval

    Reject an approval.

  • reject_incident_solution

    Reject the solution of a request, with a comment.

  • relate_incident_to_cis_by_keyword

    Relate a request to every CI that matches a keyword.

  • reopen_incident

    Reopen a request.

  • request_incident_custom_approval

    Request a custom approval (by template) on a request.

  • search_kb_articles

    Search Knowledge Base articles by keywords (relevance-ranked).

  • set_incident_custom_field

    Set the value(s) of a custom field on a request.

  • set_incident_waiting_for_agent

    Set a request to waiting for agent.

  • set_incident_waiting_for_customer

    Set a request to waiting for customer.

  • set_incident_waiting_for_date

    Set a request to waiting until a date (epoch timestamp).

  • set_incident_waiting_for_external_entity

    Set a request to waiting for an external entity.

  • set_incident_waiting_for_incident

    Set a request to waiting for another request.

  • update_incidentwrite action

    Change attributes of a request.

  • update_kb_articlewrite action

    Update a Knowledge Base article (author_id required by the API).

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan24 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 75 days ago12/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 75/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How InvGate Service Desk compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
75/100
higher than 45% of 48,255 servers
Tools
96
the typical server has 7
Tools that change things
10%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
3
more than 80% of 28,688 servers

What its tools let an agent do: 76 read · 7 create · 8 change · 5 delete

Install InvGate Service Desk in Claude Code, Cursor or VS Code

claude mcp add invgate-service-desk-mcp -- uvx invgate-service-desk-mcp
Add to Cursor

What the publisher says

From the InvGate Service Desk repository's README, as published. We do not edit it. Read it on GitHub

invgate-service-desk-mcp

<!-- mcp-name: io.github.tracegazer/invgate-service-desk-mcp -->

A Model Context Protocol server for InvGate Service Desk / Service Management.

Give your AI assistant full access to your InvGate Service Desk — query incidents, look up users, search the knowledge base, check assets, and manage tickets — all through natural language.

96 tools across 11 domains. Read-only by default, with optional write operations behind explicit opt-in.

Install in one click

The easiest way to use this server with Claude Desktop (and other MCPB-compatible clients) is the prebuilt bundle:

➡️ Download invgate-service-desk.mcpb — then double-click it. Claude Desktop opens the installer, prompts for your InvGate base URL and API token, and you're done. No Python, no npx/uvx, no config files.

The .mcpb is attached to every GitHub Release and mirrored on Smithery. Prefer a package manager or container? See Quick start below.

What can it do?

63 read-only tools work out of the box. 33 write tools (incidents, KB, time tracking) activate only when you explicitly opt in.

Quick start

1. Install

pip install invgate-service-desk-mcp

Or run without installing (requires uv):

uvx invgate-service-desk-mcp

2. Connect to Claude Desktop

Add this to your claudedesktopconfig.json:

{
  "mcpServers": {
    "invgate": {
      "command": "uvx",
      "args": ["invgate-service-desk-mcp"],
      "env": {
        "INVGATE_BASE_URL": "https://acme.sd.cloud.invgate.net",
        "INVGATE_API_TOKEN": "your-api-token"
      }
    }
  }
}

Restart Claude Desktop. That's it — start asking about your tickets.

Using pip install instead of uvx

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

InvGate Service Desk: common questions

Is InvGate Service Desk MCP server safe?
Mostly: it is graded B (75/100). Read the InvGate Service Desk safety report
How do I install InvGate Service Desk?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does InvGate Service Desk need an API key?
Yes. The registry entry asks for INVGATE_API_TOKEN.
Is InvGate Service Desk maintained?
The last commit was 113 days ago (2026-07-14). The latest release is v0.2.0.
How does InvGate Service Desk compare with other MCP servers?
safety score 75/100 (higher than 45% of 48,255 servers); tools 96 (the typical server has 7); tools that change things 10% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.