GLPI MCP Server
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
GLPI MCP Server
Connect AI assistants (Claude, ChatGPT, Copilot…) to GLPI through the Model Context Protocol (MCP): tickets, ITIL, projects, any itemtype, documents, massive actions, sessions and configuration — with safe defaults.
Português · Security · Changelog
Continues ageugyn/glpi-mcp-server by Ageu Bonfim (MIT), keeping its full history, with the goal of covering the whole GLPI legacy REST API.
Highlights
47 tools: tickets and ITIL, generic CRUD for any itemtype, project management (projects, subprojects, task trees, teams, states), session/profiles/entities, documents, massive actions.
Safe by default: delete and massive actions are off; read-only mode; allow/deny tool patterns; secrets masked in every output; tokens sent in headers (not URLs); local files confined to one directory.
Works with GLPI 10 and 11 (legacy REST API
apirest.php, also shipped with GLPI 11).
Related MCP server: glpi-mcp-server
Supported versions
GLPI | API | Status |
10.0.x | Legacy REST API ( | ✅ All tools |
11.0.x | Legacy REST API ( | ✅ All tools (tested on 11.0.7) |
11.0.x | High-Level API ( | ⚠️ Original ticket/ITIL/forms tools only |
The generic, project, session, document and massive-action tools use the legacy API: keep
GLPI_API_VERSION=10 (the default), which also works with GLPI 11.
Quick start
1. Enable the GLPI API
In GLPI: Setup → General → API → enable the REST API and "login with external token". Then get your API token: user preferences (or Administration → Users → your user) → Passwords and access keys → API token → regenerate. An App-Token is only needed if your API client requires one.
2. Install
Requires Node.js 20+.
git clone https://github.com/Alan-Gois/glpi-mcp.git
cd glpi-mcp
npm ci
npm run buildOr run straight from GitHub: npx -y github:Alan-Gois/glpi-mcp (builds on install).
3. Configure your MCP client
Claude Code — .mcp.json in your project (values come from your environment, not from the file):
{
"mcpServers": {
"glpi": {
"command": "node",
"args": ["/absolute/path/to/glpi-mcp/dist/index.js"],
"env": {
"GLPI_URL": "https://glpi.example.com",
"GLPI_USER_TOKEN": "${GLPI_USER_TOKEN}",
"GLPI_APP_TOKEN": "${GLPI_APP_TOKEN:-}"
}
}
}
}Claude Desktop — claude_desktop_config.json
(macOS ~/Library/Application Support/Claude/, Windows %APPDATA%\Claude\, Linux ~/.config/Claude/):
{
"mcpServers": {
"glpi": {
"command": "node",
"args": ["/absolute/path/to/glpi-mcp/dist/index.js"],
"env": {
"GLPI_URL": "https://glpi.example.com",
"GLPI_USER_TOKEN": "your_user_token",
"GLPI_MCP_READ_ONLY": "true"
}
}
}
}Restart the client and the glpi_* tools appear. Start with GLPI_MCP_READ_ONLY=true and open up writes
when you are comfortable.
Configuration
Variable | Required | Description |
| Yes | Base URL of GLPI (without |
| Yes* | User API token (legacy API). |
| * | Alternative to the user token (legacy API); required for the v2 API. |
| No | App token, if your API client requires one. |
| No |
|
| v2 only | OAuth2 client for |
| No |
|
| No | Regex: only register tools whose name matches (e.g. |
| No | Regex: never register tools whose name matches (e.g. |
| No |
|
| No |
|
| No | Directory where document tools may read/write local files. Default: none (base64 only). |
| No | Max document size in MB. Default: 10. |
| No |
|
* Legacy API: GLPI_USER_TOKEN or GLPI_USERNAME + GLPI_PASSWORD.
Tools
Tickets and ITIL
glpi_list_tickets, glpi_get_ticket, glpi_create_ticket, glpi_update_ticket, glpi_add_followup,
glpi_add_solution, glpi_add_task, glpi_get_ticket_tasks, glpi_request_validation,
glpi_answer_validation, glpi_get_ticket_validations, glpi_create_change, glpi_create_problem,
glpi_search (multi-criteria search on any itemtype), glpi_list_search_options, and GLPI 11 native forms:
glpi_list_forms, glpi_get_form_details, glpi_submit_form.
Generic CRUD (any itemtype)
Tool | Endpoint |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Projects
Tool | What it does |
| Projects with state, parent, manager, progress; filters by name, state, parent |
| Project + subprojects + team + task tree (with task teams) |
| Projects and subprojects ( |
| Tasks of a project as a tree (or flat) |
| Tasks and subtasks ( |
| Add a User, Group, Supplier or Contact to a project or task team |
| Project states (and project/task types) |
Dropdown fields come with the id and the name (projectstates_id + projectstates_id_name).
Session, profiles, entities and configuration
glpi_get_my_profiles, glpi_get_active_profile, glpi_change_active_profile, glpi_get_my_entities,
glpi_get_active_entities, glpi_change_active_entities, glpi_get_full_session, glpi_get_glpi_config
(use keys to limit large outputs). GLPI refusals are reported as errors. lostPassword is not exposed.
Documents
Tool | What it does |
| Upload base64 content or a local file, optionally linked to an item |
| Download to a local file (never overwrites) or as base64; SHA-1 checked against GLPI |
Massive actions
Tool | Endpoint |
|
|
|
|
|
|
Example prompts
"List the projects in progress and show the task tree of the biggest one."
"Create project Office move with subprojects Network and Furniture, and a task Cabling of 16 hours."
"Show open tickets of the last week and add a followup to #42."
"Which computers in the Finance location run Windows 10?"
"Attach
report.pdfto ticket 120."
Security
See docs/security.md. In short: give the API user only the GLPI profile it needs, start in read-only mode, keep delete and massive actions off unless needed, and keep tokens in environment variables or a secret manager — never in files under version control.
Development
npm ci
npm run build
npm test
npx @modelcontextprotocol/inspector node dist/index.jsCI runs build, tests and npm audit on Node 20, 22 and 24.
Credits and license
MIT — see LICENSE. Original work by Ageu Bonfim (ageugyn/glpi-mcp-server); continued by Alan Gois.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for GLPI: tickets, ITIL, assets, knowledge base. GLPI 10/11. Not affiliated with Teclib'.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Helpdesk tickets from your AI: find, reply, take, hold, complete — within your own role. OAuth.
Related MCP Servers
- AlicenseBqualityCmaintenanceMCP server allowing an AI assistant to interact directly with your GLPI instance via its REST API, enabling ticket management, knowledge base operations, and statistics.404-
- AlicenseNot gradedqualityDmaintenanceConnects AI assistants to GLPI IT Service Management, enabling ticket management, asset search, and ITIL processes via natural language.11 npm3MIT
- AlicenseCqualityDmaintenanceEnables AI assistants to manage GLPI inventory, tickets, and CIA security fields via its REST API.925 npm1ISC
- AlicenseBqualityCmaintenanceEnables AI assistants to interact with a GLPI instance through its REST API, allowing natural-language consultation, creation, and updating of tickets, followups, tasks, solutions, knowledge base articles, suppliers, contacts, contracts, and statistics.52-