Log inSubmit server
Invgate Service Desk MCP logo

Invgate Service Desk MCP

by tracegazer

Connects AI assistants to InvGate Service Desk for ticket, user, knowledge base, asset, and service-management operations.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Invgate Service Desk MCP

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "tracegazer-invgate-service-desk-mcp": {
      "command": "uvx",
      "args": [
        "invgate-service-desk-mcp"
      ],
      "env": {
        "INVGATE_BASE_URL": "YOUR_VALUE_HERE",
        "INVGATE_API_TOKEN": "YOUR_VALUE_HERE",
        "INVGATE_API_USERNAME": "YOUR_VALUE_HERE",
        "INVGATE_WRITE_PROFILE": "YOUR_VALUE_HERE",
        "INVGATE_ENABLE_WRITES": "YOUR_VALUE_HERE",
        "INVGATE_TELEMETRY": "YOUR_VALUE_HERE",
        "INVGATE_TELEMETRY_DETAIL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

tracegazer/invgate-service-desk-mcp MCP server connects MCP-compatible AI clients to an InvGate Service Desk instance through its API. It exposes 96 tools covering incidents, users, knowledge articles, assets, custom fields, workflows, time tracking, and related service-management data. Read operations are enabled by default, while incident, time-tracking, and knowledge-base writes require an explicit write profile. Use it when an agent needs to retrieve or manage InvGate records through natural-language requests.

Use cases

  • Search incidents by status, customer, or agent
  • Look up users and group membership
  • Find relevant knowledge-base articles
  • Inspect assets linked to incidents
  • Update tickets with explicit write access

Key features

  • 96 tools across 11 service-management domains
  • Read-only operation by default
  • Profile-based write controls
  • InvGate API token authentication
  • STDIO and SSE/HTTP transport options
  • Optional OpenTelemetry observability

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

8/9 checks healthy over the last 84d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · invgate-service-desk-mcp (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
Last commit3mo agoMost recent push to the default branch.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Invgate Service Desk MCP works

What tracegazer/invgate-service-desk-mcp MCP server does

The tracegazer/invgate-service-desk-mcp MCP server exposes InvGate Service Desk and Service Management capabilities to MCP-compatible AI assistants. Its 96 tools are organized across 11 domains, including incidents, users and groups, the knowledge base, custom fields, organizational data, assets and configuration items, time tracking, triggers, workflows, catalogs, and breaking-news announcements.

Read-only access is the default. Agents can inspect tickets, search for users, find knowledge articles, review asset relationships, examine workflows, and retrieve service-desk reference data without enabling write operations. Write access is separately controlled so an administrator can choose whether the agent may change incidents, record time, or modify knowledge-base content.

How it works

The server runs as a local STDIO process by default and communicates with an InvGate instance over HTTP. Authentication uses HTTP Basic authentication with the username api by default and the configured API token as the password. A custom API username can also be supplied.

The tracegazer/invgate-service-desk-mcp MCP server can alternatively run with SSE/HTTP transport. Those transports do not provide built-in authentication, so the README recommends binding them to loopback or placing them behind an authenticated reverse proxy.

Write permissions use three profiles: none, support, and full. The default none profile permits reads only. support enables incident operations and time tracking, while full also enables knowledge-base writes. The older INVGATE_ENABLE_WRITES=1 setting remains available and maps to the full profile.

Setup and configuration

Install the package with pip install invgate-service-desk-mcp, or run it without installation through uvx invgate-service-desk-mcp. Claude Desktop users can also install the downloadable .mcpb bundle, which prompts for the InvGate URL and API token.

Set INVGATE_BASE_URL to the service-desk instance URL and INVGATE_API_TOKEN to a token created under InvGate Settings > Integrations > API. Configuration can also be stored in ~/.config/invgate-service-desk-mcp/config.toml; environment variables take precedence over that file. The command supports STDIO by default and an SSE option through --transport sse.

Optional OpenTelemetry support requires the telemetry package extra and INVGATE_TELEMETRY=1. Standard OTLP environment variables configure the telemetry destination and credentials.

Tools and capabilities

Available tool areas include:

  • Catalog lookups for priorities, statuses, incident types, categories, and sources
  • Incident retrieval, filtering, assignment, comments, approvals, creation, and updates
  • User, group, helpdesk, level, location, and company-structure lookups
  • Knowledge-base search, category browsing, article creation, and article updates
  • Custom-field definitions and option values, including list and tree structures
  • Asset and configuration-item relationships linked to incidents
  • Logged-time queries and new time entries
  • Trigger executions, workflow metadata, and breaking-news records

The tracegazer/invgate-service-desk-mcp MCP server reports optional traces, metrics, and logs through OpenTelemetry when enabled.

Limitations and notes

Write mode can create, modify, or cancel real InvGate content using the configured credential. InvGate tickets cannot be deleted through the API; created tickets can only be cancelled. An invalid write-profile value stops startup. SSE and streamable HTTP deployments need external network protection because they have no built-in authentication. Knowledge-base writes are excluded from the support profile and require full.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Invgate Service Desk MCP

tracegazer/invgate-service-desk-mcp is an MCP server that connects AI assistants to InvGate Service Desk through its API. Its main tools query incidents, users, knowledge-base articles, assets, custom fields, workflows, and service catalogs, with optional tools for creating or updating incidents, logging time, and changing knowledge-base content.

Install it with `pip install invgate-service-desk-mcp` or run it with `uvx invgate-service-desk-mcp`. Claude Desktop users can instead download and open the provided `.mcpb` bundle, which asks for the InvGate base URL and API token.

Set `INVGATE_WRITE_PROFILE` to `support` or `full`; leaving it unset uses the read-only `none` profile. The support profile enables incident and time-tracking writes, while full also enables knowledge-base writes.

Set `INVGATE_BASE_URL` and `INVGATE_API_TOKEN` to connect to InvGate. `INVGATE_API_USERNAME` is optional and defaults to `api`; `INVGATE_WRITE_PROFILE` controls writes. Telemetry settings are optional.

Yes. Claude Desktop can run it through STDIO using `uvx`, a pip-installed executable, or the downloadable `.mcpb` bundle. The bundle provides an installation flow that requests the InvGate URL and API token.

Related MCP servers

All in Support & Service Management All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewInvgate Service Desk MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/tracegazer-invgate-service-desk-mcp?style=directory)](https://allmcps.com/mcp/tracegazer-invgate-service-desk-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/tracegazer-invgate-service-desk-mcp"><img src="https://allmcps.com/api/badge/tracegazer-invgate-service-desk-mcp?style=directory" alt="Invgate Service Desk MCP on AllMCPs" /></a>