GLPI MCP Server v2
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GLPI_BASE_URL | Yes | Base URL of the GLPI server (e.g. http://localhost:8080). | |
| GLPI_PASSWORD | Yes | GLPI password used for password grant authentication. | |
| GLPI_USERNAME | Yes | GLPI username used for password grant authentication. | |
| MCP_HTTP_PORT | No | Port for the HTTP transport when MCP_TRANSPORT=http. | 3000 |
| MCP_TRANSPORT | No | Transport mode for the MCP server. Set to 'http' to enable HTTP transport. | stdio |
| GLPI_APP_TOKEN | No | Alias for GLPI_API_V1_APP_TOKEN. | |
| GLPI_CLIENT_ID | Yes | OAuth2 client ID for GLPI API v2.3. | |
| GLPI_USER_TOKEN | No | Alias for GLPI_API_V1_USER_TOKEN. | |
| GLPI_CLIENT_SECRET | Yes | OAuth2 client secret for GLPI API v2.3. | |
| GLPI_API_V1_APP_TOKEN | No | Optional app token for legacy GLPI API v1, required only for the Knowledgebase tools. | |
| GLPI_API_V1_USER_TOKEN | No | Optional user token for legacy GLPI API v1, required only for the Knowledgebase tools. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| glpi_search_ticketsB | Busca e lista tickets. Permite paginação (start, limit) e filtros (filter em RSQL). |
| glpi_get_ticketA | Retorna o contexto completo de UM ticket, incluindo timeline, sem precisar de múltiplas chamadas. |
| glpi_get_ticket_timelineA | Retorna a timeline de UM ticket (followups, tasks, etc). |
| glpi_create_ticketB | Cria um novo ticket. |
| glpi_update_ticketC | Atualiza campos de um ticket existente. |
| glpi_add_ticket_followupC | Adiciona um followup (acompanhamento) à timeline de um ticket. |
| glpi_get_ticket_statsC | Retorna as estatísticas de um ticket. |
| glpi_search_problemsA | Busca e lista problems. Permite paginação (start, limit) e filtros (filter em RSQL). |
| glpi_get_problemC | Retorna o contexto completo de UM problem, incluindo timeline, sem precisar de múltiplas chamadas. |
| glpi_get_problem_timelineA | Retorna a timeline de UM problem (followups, tasks, etc). |
| glpi_create_problemC | Cria um novo problem. |
| glpi_update_problemC | Atualiza campos de um problem existente. |
| glpi_add_problem_followupB | Adiciona um followup (acompanhamento) à timeline de um problem. |
| glpi_get_problem_statsC | Retorna as estatísticas de um problem. |
| glpi_search_changesC | Busca e lista changes. Permite paginação (start, limit) e filtros (filter em RSQL). |
| glpi_get_changeA | Retorna o contexto completo de UM change, incluindo timeline, sem precisar de múltiplas chamadas. |
| glpi_get_change_timelineB | Retorna a timeline de UM change (followups, tasks, etc). |
| glpi_create_changeC | Cria um novo change. |
| glpi_update_changeA | Atualiza campos de um change existente. |
| glpi_add_change_followupA | Adiciona um followup (acompanhamento) à timeline de um change. |
| glpi_get_change_statsC | Retorna as estatísticas de um change. |
| glpi_search_knowbaseA | Busca artigos na base de conhecimento (Knowledgebase). Permite paginação (start, limit) e filtros (filter). |
| glpi_get_knowbase_itemA | Retorna o conteúdo completo de um artigo da base de conhecimento. |
| glpi_search_faqA | Busca artigos marcados como FAQ na base de conhecimento (is_faq=true). Use para dúvidas rápidas de uso do GLPI antes de abrir ticket. |
| glpi_get_asset_statsC | Retorna estatísticas de ativos (assets) associados a chamados, mudanças ou problemas. |
| glpi_list_computersC | Busca e lista computadores (Assets). Permite paginação (start, limit) e filtros (filter em RSQL). |
| glpi_get_computerC | Retorna o contexto completo de UM computador, incluindo especificações de hardware (CPU, memória, disco, rede) e software instalado. |
| glpi_search_userA | Busca e lista usuários (Users). Permite paginação e filtros. |
| glpi_get_user_contextC | Retorna o contexto de UM usuário, incluindo itens usados e gerenciados. |
| glpi_list_groupsA | Busca e lista grupos (Groups). Permite paginação e filtros. |
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 30 tools
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.
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.
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.
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.