Skip to main content
Glama
USONDIG

GLPI MCP

by USONDIG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to GLPI MCP

No user-submitted related servers found.

    Related Servers

    • glpi-mcp

      maimik
      A
      license
      C
      quality
      D
      maintenance
      Enables AI assistants to manage GLPI inventory, tickets, and CIA security fields via its REST API.
      9
      8 npm
      1
      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.
      5 npm
      4
      MIT

    • NexTool MCP for GLPI

      NexTools-Solutions
      A
      license
      B
      quality
      A
      maintenance
      Connects AI assistants to GLPI service desks so they can manage tickets, ITIL objects (problems and changes), assets, knowledge base articles, users, rules and webhooks through natural language. Works with GLPI 10 and 11 via REST API v1 and the GLPI 11 API v2, with read-only and delete guards, idempotent creates, and support for both local (stdio/HTTP) and hosted OAuth deployments.
      111
      1
      MIT

    • GLPI MCP Server

      Alan-Gois
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects AI assistants to GLPI through the Model Context Protocol, enabling management of tickets, ITIL objects, assets, projects, tasks, documents, sessions, entities and massive actions via the legacy REST API. It supports GLPI 10 and 11 with safe defaults such as read-only mode, disabled destructive operations and masked secrets.
      MIT

    • GLPI MCP

      svtica
      A
      license
      B
      quality
      C
      maintenance
      MCP server allowing an AI assistant to interact directly with your GLPI instance via its REST API, enabling ticket management, knowledge base operations, and statistics.
      40
      4
      -
    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 52 tools

    Disambiguation4/5

    Each tool has a clearly distinct purpose, with resource+action naming that separates e.g. list_tickets vs search_tickets and profile vs group visibility tools. A few tools (stats_by_*) follow similar patterns but target different metrics, so confusion is unlikely.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (list_tickets, add_followup, update_supplier), with only minor deviations like stats_resolution_time and kill_session. No mixed conventions are present.

    Tool Count2/5

    52 tools is far above the typical 3–15 range; while GLPI is a broad domain, the granular CRUD for each entity could be consolidated. The count is excessive and likely burdens tool selection.

    Completeness3/5

    Core ticketing, followups, tasks, and KB articles have near-complete lifecycles, but there are notable gaps: no list/get for contacts and contracts, no update/delete for solutions, no asset/problem/change management, and KB category CRUD is missing. These gaps limit the server's coverage of GLPI.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources