claude mcp add invgate-service-desk-mcp -- npx -y invgate-service-desk-mcp
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
4 ★ · tracegazer/invgate-service-desk-mcp · read from the GitHub search API · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 4 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository tracegazer/invgate-service-desk-mcp;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
> 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? | Domain | Tools | Examples | |--------|------:|---------| | **Catalog** | 5 | List priorities, statuses, incident types, categories (with search), sources | | **Incidents** | 34 | Get ticket details, list by status/agent/customer, create & update tickets, reassign, comment, manage approvals | | **Users & Groups** | 7 | Look up users, find by email/phone, list group members | | **Knowledge Base** | 10 | Search articles, browse categories, create & update articles | | **Custom Fields** | 9 | List field definitions, get options (list/tree), fields by category | | **Organization** | 11 | Helpdesks, levels, locations, company structure | | **Assets / CIs** | 6 | Find assets linked to incidents, CI relationships | | **Time Tracking** | 4 | View logged hours, log new time entries | | **Triggers** | 2 | List automation rules and their executions | | **Workflows** | 3 | Inspect workflow fields, processes, and field values | | **Breaking News** | 5 | View announcements, statuses, types | > **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 Or run without installing (requires uv): 2. Connect to Claude Desktop Add this to your claude_desktop_config.json: Restart Claude Desktop. That's it — start asking about your tickets. Using pip install instead of uvx Enabling write operations By default the server is **read-only**. Opt into writes with INVGATE_WRITE_PROFILE: | Profile | Reads | Writes | |------------------|------------|-------------------------------------------------------------------| | none (default) | everything | nothing | | support | everything | incidents (tickets, comments, reassign, approve) + time tracking | | full | everything | incidents + time tracking + Knowledge Base | > **Compatibility:** the legacy INVGATE_ENABLE_WRITES=1 still works and maps to full. > If both are set, the profile wins and a warning is printed to stderr. Note: support > deliberately keeps the Knowledge Base read-only. An invalid profile name fails fast at startup. > **Warning:** write mode lets the connected agent create, modify, and delete real content through your InvGate credential. There is no API to delete a ticket — created tickets can only be cancelled, not removed.