$ loading_
Let AI manage GLPI tickets, knowledge base, and statistics directly.
This tool claims to interact with a GLPI instance via the GLPI REST API, which implies network access and operations on ticket/knowledge-base data; however, the materials are sparse and do not explain authentication, endpoints, permission boundaries, or local data scope, so caution is warranted. The open-source repository is a positive signal, but low adoption and unknown maintenance reduce audit confidence.
The materials say there are no keys/environment variables, yet direct interaction with a GLPI instance via REST API would normally require some form of authentication or instance-side credential. The docs do not explain credential sourcing, storage, or scope, creating opacity around credential handling.
The description explicitly states it connects to the user's GLPI instance REST API, so user prompts and related ticket/knowledge-base content may be sent over the network to that instance. However, the materials do not specify exact endpoints, data scope, or whether any additional third-party egress exists.
The system flags that this tool executes code/spawns a process, which is a common MCP capability. The available materials do not show requests for unusual system privileges or arbitrary commands unrelated to GLPI, so this alone is not a high-risk red flag.
By description, it can manage tickets, operate on the knowledge base, and query statistics, implying access to and possible modification of GLPI business data. But it does not define whether access is limited to specific projects/entities, read-only vs. write boundaries, or any local file access, leaving the data scope unclear.
A public open-source GitHub repository is a positive factor that lowers risk because the code can be reviewed. However, the source is a third-party registry, the license is undeclared, community adoption is 0 stars, and maintenance is unknown, so supply-chain trust remains only moderate and source/dependency review is advisable.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "GLPI MCP" yet — see the docs or source repo.
Create a GLPI ticket for “printer cannot connect to the network,” set priority to high, assign it to the network support group, and return the ticket ID and link.
Returns the created ticket details, including ID, status, assignee or group, and access link.
Search the GLPI knowledge base for articles related to “VPN connection failure,” list the 3 most relevant ones, and summarize the resolution steps for each.
Returns a list of relevant knowledge base entries with a concise summary of the key resolution steps for each.
Get GLPI statistics for the last 30 days: number of new tickets, closed tickets, unresolved tickets, and break them down by priority.
Provides a 30-day ticket statistics overview, including totals, status distribution, and priority breakdown.
Manage Redmine projects, issues, time logs, wiki, and files via MCP.
Manage OpenProject projects, work packages, activities, and wiki pages through AI.
Lets AI read and manage GitLab projects, MRs, issues, and pipelines.
Manage Jira, Confluence, Git insights, and diagrams through one local MCP server.
Connect AI to any MediaWiki wiki for search, reading, and content interaction.
Turn existing APIs and databases into MCP tools for direct AI use.