glpi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GLPI_API_URL | Yes | The full URL to your GLPI API endpoint. | |
| GLPI_APP_TOKEN | Yes | The unique App Token generated in GLPI (Setup > General > API). | |
| GLPI_USER_TOKEN | No | The User Token from your personal settings. | |
| GLPI_OAUTH_TOKEN | No | OAuth Access Token (if using OAuth). Takes precedence if both GLPI_USER_TOKEN and GLPI_OAUTH_TOKEN are provided. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| glpi_list_itemsD | – |
| glpi_get_itemD | – |
| glpi_create_itemD | – |
| glpi_update_itemD | – |
| glpi_delete_itemD | – |
| glpi_searchD | – |
| glpi_get_cia_fieldsD | – |
| glpi_update_cia_fieldsD | – |
| glpi_update_cia_fields_batchD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
The CRUD operations (list, create, get, update, delete) are clearly distinct, and the CIA fields tools are separate from item tools. However, glpi_search may overlap with glpi_list_items in function, and the generic 'item' term could cause confusion without descriptions.
Most tools follow a consistent verb_noun pattern (e.g., glpi_list_items, glpi_create_item), but glpi_search breaks the pattern by omitting the object. Overall, naming is clear and predictable.
With 9 tools, the server is well-scoped for basic GLPI item management and CIA field handling. The count is appropriate, neither too sparse nor overwhelming.
The tool set covers full CRUD for items, search, and specialized CIA field operations. Minor gaps exist, such as batch create/delete or listing item types, but the core functionality is complete.