Enterprise DNA
M MCP Servers Developer low

tracegazer/invgate-service-desk-mcp

by Various

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

T

MCP

tracegazer/invgate-service-desk-mcp

Added 11 June 2026

#ai #ai-tools #claude #invgate #itsm #mcp #mcp-server #model-context-protocol

Overview

A Model Context Protocol server that wraps the InvGate Service Desk API, exposing its operations as MCP tools. It allows AI agents to interact with InvGate Service Desk through standardized tool calls.

Best for

Best for
Developers building AI assistants that need to automate InvGate Service Desk workflows

Use cases

  • Automating ticket creation and updates via AI agents
  • Querying service desk assets and incidents programmatically
  • Integrating InvGate Service Desk with MCP-compatible assistants

Notes

A Model Context Protocol server that wraps the InvGate Service Desk API, exposing its operations as MCP tools. It allows AI agents to interact with InvGate Service Desk through standardized tool calls.

1 stars on GitHub. Last updated 2026-06-09. Licensed MIT.

Use cases

  • Automating ticket creation and updates via AI agents
  • Querying service desk assets and incidents programmatically
  • Integrating InvGate Service Desk with MCP-compatible assistants

Pros

  • Enables direct AI agent access to service desk operations
  • Leverages the MCP standard for tool interoperability
  • Written in Python, easy to extend or debug

Cons

  • Very early stage with only 1 star and minimal community adoption
  • Requires an existing InvGate Service Desk instance and API access
  • Limited documentation and no clear error handling patterns

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Enables direct AI agent access to service desk operations
  • Leverages the MCP standard for tool interoperability
  • Written in Python, easy to extend or debug

Cons

  • Very early stage with only 1 star and minimal community adoption
  • Requires an existing InvGate Service Desk instance and API access
  • Limited documentation and no clear error handling patterns