Skip to main content
Glama
svtica

GLPI MCP

by svtica
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to GLPI MCP

No user-submitted related servers found.

    Related Servers

    • GLPI MCP Server v2

      Luizcc87
      A
      license
      C
      quality
      A
      maintenance
      MCP server for GLPI integration, providing tools for ITIL management (tickets, problems, changes, knowledge base, stats, assets, and administration) via the GLPI API.
      30
      MIT
    • tickiti-mcp by tickiti

      tickiti-mcpofficial

      tickiti
      A
      license
      B
      quality
      B
      maintenance
      An MCP server that exposes the Tickiti helpdesk API to AI assistants, enabling ticket management and helpdesk operations via natural language.
      11
      MIT

    • glpi-mcp

      maimik
      A
      license
      C
      quality
      C
      maintenance
      Enables AI assistants to manage GLPI inventory, tickets, and CIA security fields via its REST API.
      9
      10 npm
      ISC

    • glpi-mcp-server

      ageugyn
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to GLPI IT Service Management, enabling ticket management, asset search, and ITIL processes via natural language.
      3 npm
      3
      MIT
    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

    B3.3/5.0

    Scored across 40 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, such as ticket CRUD, task management, and KB operations. However, list_tickets and search_tickets overlap in functionality since search_tickets can replicate simple listing with filters, and link_tickets vs list_ticket_links are create vs read but names are close.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, e.g., list_tickets, create_ticket, update_ticket. The stats_by_* tools form a coherent sub-pattern, and even kill_session fits the verb_noun convention.

    Tool Count2/5

    40 tools is excessive according to the rubric (25+ is too many). The visibility management tools alone add 8 variations, and many tools handle niche edge cases that could be consolidated or omitted without losing core functionality.

    Completeness3/5

    The ticket lifecycle is well covered with CRUD, linking, merging, followups, and tasks. However, there are notable gaps: no delete for KB articles, no update/delete for followups or solutions, and no deletion of visibility rules, which could leave users unable to correct mistakes or remove obsolete data.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources