Skip to main content
Glama
tracegazer

InvGate Service Desk

by tracegazer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to InvGate Service Desk

No user-submitted related servers found.

    Related Servers

    • servicedesk-plus

      kaattaalan
      A
      license
      A
      quality
      C
      maintenance
      MCP server for ManageEngine ServiceDesk Plus that lets AI agents list, search, create, update, and manage help desk tickets and technical notes in real-time.
      6
      MIT

    • soporte-ti-mcp

      raulperez0798
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides IT support tools to search known incidents, check ticket status, and create ticket drafts, enabling an AI assistant to help users with IT support queries.
      -

    • invgate-mcp

      wdelcant
      A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server for InvGate Asset Management, enabling natural language queries for assets, people, computers, servers, software, and API health.
      12
      6 npm
      1
      MIT

    • freshservice-mcp

      mchluba
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to interact with Freshservice service desk, supporting ticket search, retrieval, and creation via a configurable, Docker-first deployment.
      MIT

    • kaseya-bms-mcp

      WYRE-AI
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Kaseya BMS PSA — tickets, accounts, time entries, and contracts. Enables AI assistants to manage service desk operations via the Kaseya BMS API.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.7/5.0

    Scored across 63 tools

    Disambiguation4/5

    Most tools target distinct entities or filtered views, but the multiple list_incidents_by_* functions could cause confusion without careful reading. Descriptions clarify the filter, so ambiguity is low.

    Naming Consistency4/5

    Naming follows a consistent verb_noun pattern (get_, list_, find_, search_) with minor exceptions like get_breaking_news_status mixing list-like behavior. Overall, predictable.

    Tool Count3/5

    63 tools is high, but the service desk domain has many entities. The count is justifiable though slightly excessive; some tools could be merged (e.g., list_incidents_by_*).

    Completeness1/5

    The entire tool set is read-only (no create, update, or delete operations). Missing basic CRUD for incidents, users, and other entities makes it severely incomplete for typical automation workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources