Invgate Service Desk

Name: Invgate Service Desk
Author: tracegazer

@tracegazer

代码仓库主页

关于 Invgate Service Desk

MCP server for the InvGate Service Desk API — exposes InvGate Service Desk operations as Model Context Protocol tools.

#invgate #service-desk #itsm #ticketing #knowledge-base #incident-management #helpdesk #stdio #python #pypi

基本信息

分类

其他

许可证

MIT

运行时

python

传输方式

stdio

发布者

tracegazer

提交者

Alan

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

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

工具

未检测到工具

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Invgate Service Desk?

A Model Context Protocol (MCP) server that gives AI assistants full access to an InvGate Service Desk or Service Management instance. It provides 96 tools across 11 domains for querying incidents, looking up users, searching the knowledge base, checking assets, and managing tickets through natural language. It is read‑only by default, with optional write operations behind explicit opt‑in.

How to use Invgate Service Desk?

Install via pip install invgate-service-desk-mcp or run with uvx invgate-service-desk-mcp. Configure with environment variables INVGATE_BASE_URL and INVGATE_API_TOKEN (and optionally INVGATE_WRITE_PROFILE), then add the server to claude_desktop_config.json. Alternatively, download the prebuilt .mcpb bundle and double‑click it for a one‑click installation.

Key features of Invgate Service Desk

96 tools across 11 domains (catalog, incidents, users, KB, etc.)
Read‑only by default; write operations opt‑in via INVGATE_WRITE_PROFILE
Supports STDIO and SSE/HTTP transports
Optional OpenTelemetry observability for traces, metrics, and logs
Prebuilt .mcpb bundle for zero‑install setup
TOML configuration file for persistent settings

Use cases of Invgate Service Desk

Query incidents and retrieve ticket details via natural language
Look up users, groups, and asset information
Search and browse the knowledge base
Create, update, and reassign tickets (with write opt‑in)
Log time entries and inspect automation triggers

FAQ from Invgate Service Desk

How do I obtain an API token for InvGate?

In your InvGate Service Desk instance, go to Settings > Integrations > API (or ask your admin). The server authenticates via HTTP Basic with username api and the token as the password.

Can I enable write operations? How?

Yes. Set the environment variable INVGATE_WRITE_PROFILE to support (incidents + time tracking) or full (adds knowledge base writes). The legacy INVGATE_ENABLE_WRITES=1 still works and maps to full. The default is none (read‑only).

What transports does the server support?

The default is STDIO, which keeps everything local. The --transport sse flag enables SSE/HTTP, but that transport has no built‑in authentication and should only be used bound to loopback or behind an authenticated reverse proxy.

Can I run the server without installing Python?

Yes. Download the prebuilt .mcpb bundle from the GitHub releases page or Smithery. Double‑click it to install in Claude Desktop – no Python, npx, or uvx required.

Is there a risk of data loss with write mode?

Write mode lets the connected agent create, modify, and delete real content. However, there is no API to delete a ticket – created tickets can only be cancelled, not removed.