# tracegazer/invgate-service-desk-mcp [Health: Active]

**Category:** 🎧 Support & Service Management  
**Repository:** https://github.com/tracegazer/invgate-service-desk-mcp  
**GitHub Stars:** 4  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/tracegazer-invgate-service-desk-mcp

## Description
MCP server for InvGate Service Desk: 96 tools across 11 domains (incidents, users, knowledge base, assets, custom fields, workflows, time tracking), read-only by default with opt-in writes.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "invgate-service-desk-mcp": {
    "command": "uvx",
    "args": ["invgate-service-desk-mcp"],
    "env": {
      "INVGATE_BASE_URL": "",
      "INVGATE_API_TOKEN": "",
      "INVGATE_API_USERNAME": "",
      "INVGATE_WRITE_PROFILE": "",
      "INVGATE_ENABLE_WRITES": "",
      "INVGATE_TELEMETRY": "",
      "INVGATE_TELEMETRY_DETAIL": ""
    }
  }
}
```

**Requires environment variables:** `INVGATE_BASE_URL`, `INVGATE_API_TOKEN`, `INVGATE_API_USERNAME`, `INVGATE_WRITE_PROFILE`, `INVGATE_ENABLE_WRITES`, `INVGATE_TELEMETRY`, `INVGATE_TELEMETRY_DETAIL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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`.

_Full upstream README: https://allmcps.com/mcp/tracegazer-invgate-service-desk-mcp/readme_