Skip to main content
Glama
Luizcc87

GLPI MCP Server v2

by Luizcc87
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to GLPI MCP Server v2

No user-submitted related servers found.

    Related Servers

    • 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
      -

    • mcp-ticketing-server

      ShaiviBansal
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for ticketing automation that exposes tools to create, search, and update IT helpdesk tickets, with metrics tracking.
      -

    • mcp-itop

      gest0r1
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for iTop ITSM that provides 19 tools for analytics, ticket management, comments, knowledge base, and CI impact analysis, enabling AI assistants to interact with iTop.
      1
      -

    • mcp-server-snipe-it

      borgels
      A
      license
      A
      quality
      B
      maintenance
      MCP server for the Snipe-IT asset management REST API, enabling read and write operations on assets, licenses, accessories, and more.
      13
      Apache 2.0

    • gitlab-mcp

      EllGree
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for interacting with GitLab API, supporting both self-hosted instances and gitlab.com. Provides tools for managing issues, merge requests, code review, pipelines, milestones, releases, search, and file access.
      745 npm
      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

    C2.9/5.0

    Scored across 30 tools

    Disambiguation4/5

    Tools mostly target distinct resources and actions: tickets, problems, changes, knowledgebase, computers, users, and groups are clearly named. Some overlap exists between full-context getters and standalone timeline getters, and between knowledgebase search and FAQ search, but the descriptions help disambiguate them.

    Naming Consistency4/5

    Nearly all tools follow glpi_verb_entity snake_case with consistent create/update/search/get/add patterns for the main ITSM entities. Minor deviations include list_computers/list_groups versus search_* for the other collections, and get_knowbase_item versus get_computer/get_ticket.

    Tool Count2/5

    At 30 tools, this is above the 25-tool heavy threshold and the set includes redundant timeline endpoints that duplicate the full-context getters. A leaner set around 20-22 tools could cover the same GLPI modules without extra selection burden.

    Completeness3/5

    The core ticket/problem/change lifecycle is well covered with search, get, create, update, and followup, and there is read access to knowledgebase, computers, users, and groups. However, there are no create/update/delete operations for computers, users, or groups, no knowledgebase write tools, and no task/solution-specific endpoints for tickets, problems, or changes.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources