InvGate Service Desk MCP — 96 tools across 11 domains (incidents, users, knowledge base, assets, time tracking), read-only by default with a 3-tier
InvGate Service Desk MCP — 96 tools across 11 domains (incidents, users, knowledge base, assets, time tracking), read-only by default with a 3-tier write access model (none/support/full), and built-in OpenTelemetry observability. That is what the invgate mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
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.
Installation goes through your MCP client rather than a global install: point it at invgate-service-desk-mcp on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Configuration is passed through the environment: INVGATE_BASE_URL, INVGATE_API_TOKEN, INVGATE_WRITE_PROFILE, INVGATE_TELEMETRY, OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_EXPORTER_OTLP_HEADERS, OTEL_SERVICE_NAME, YOUR_DT_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by Alan (tracegazer); worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
{
"mcpServers": {
"invgate-service-desk": {
"command": "uvx",
"args": ["invgate-service-desk-mcp"],
"env": {
"INVGATE_BASE_URL": "your-value",
"INVGATE_API_TOKEN": "your-value",
"INVGATE_WRITE_PROFILE": "your-value",
"INVGATE_TELEMETRY": "your-value",
"OTEL_EXPORTER_OTLP_ENDPOINT": "your-value",
"OTEL_EXPORTER_OTLP_HEADERS": "your-value",
"OTEL_SERVICE_NAME": "your-value",
"YOUR_DT_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| INVGATE_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| INVGATE_API_TOKEN | Credential the server authenticates with. | Yes |
| INVGATE_WRITE_PROFILE | Configuration value read at startup. | Optional |
| INVGATE_TELEMETRY | Configuration value read at startup. | Optional |
| OTEL_EXPORTER_OTLP_ENDPOINT | Configuration value read at startup. | Optional |
| OTEL_EXPORTER_OTLP_HEADERS | Configuration value read at startup. | Optional |
| OTEL_SERVICE_NAME | Configuration value read at startup. | Optional |
| YOUR_DT_TOKEN | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.