Connect AI clients to GLPI to manage tickets, ITIL processes, assets, and the knowledge base via REST and OAuth2 APIs.
Also known as NexTools-Solutions/nextool-mcp-glpi, glpi, @nextoolsolutions/mcp-glpi
- Stars
- 1
- Tools
- 111
- Downloads, 30 days
- —
- Latest version
- 3.5.7
- Last commit
- Nov 4, 2026
- License
- MIT
What is NexTool for GLPI MCP?
NexTool for GLPI connects AI clients to GLPI to manage tickets, ITIL processes, assets, and the knowledge base via REST and OAuth2 APIs. It exposes 111 tools, such as glpi_list_tickets, glpi_list_my_tickets, glpi_get_ticket.
Summary generated from the project's README
About NexTool for GLPI MCP server
NexTool MCP for GLPI provides a bridge between AI clients and GLPI instances to manage ITIL processes, assets, and knowledge bases. It supports two distinct tool families: a classic REST API family for GLPI versions 9.5 through 11, and a high-level API v2 family specifically for GLPI 11 using OAuth2. Developers can run this as a local process via stdio or as a multi-tenant HTTP server that manages multiple instances through a single binary.
Users can control the level of context provided to the AI by selecting specific toolsets like tickets, assets, or kb. This prevents overwhelming the session with unnecessary tools. Authentication for the classic API requires a user token and app token, while the v2 family uses client IDs, secrets, and user credentials. The server also includes built-in prompts for tasks such as triage and requester history investigation, provided the required tools are enabled.
What you can do with it
- 1Manage IT service ticketsAn AI agent can list, search, and update the lifecycle of support tickets within GLPI.
- 2Inventory and asset trackingA developer can use the server to query asset details, locations, and reservations.
- 3System administration tasksAuthorized users can manage users, groups, and business rules through the admin toolset.
Written from the project's README. Every use case is checked against a quote from it.
How to install NexTool for GLPI MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall NexTool for GLPI MCP in Claude Code
$ claude mcp add --env 'GLPI_APP_TOKEN=<YOUR_GLPI_APP_TOKEN>' --env 'GLPI_USER_TOKEN=<YOUR_GLPI_USER_TOKEN>' --env 'GLPI_V2_CLIENT_SECRET=<YOUR_GLPI_V2_CLIENT_SECRET>' --env 'GLPI_V2_PASSWORD=<YOUR_GLPI_V2_PASSWORD>' glpi -- npx -y @nextoolsolutions/mcp-glpiInstall NexTool for GLPI MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"glpi": {
"command": "npx",
"args": [
"-y",
"@nextoolsolutions/mcp-glpi"
],
"env": {
"GLPI_APP_TOKEN": "<YOUR_GLPI_APP_TOKEN>",
"GLPI_USER_TOKEN": "<YOUR_GLPI_USER_TOKEN>",
"GLPI_V2_CLIENT_SECRET": "<YOUR_GLPI_V2_CLIENT_SECRET>",
"GLPI_V2_PASSWORD": "<YOUR_GLPI_V2_PASSWORD>"
}
}
}
}Install NexTool for GLPI MCP in VS Code
.vscode/mcp.json
{
"servers": {
"glpi": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@nextoolsolutions/mcp-glpi"
],
"env": {
"GLPI_APP_TOKEN": "<YOUR_GLPI_APP_TOKEN>",
"GLPI_USER_TOKEN": "<YOUR_GLPI_USER_TOKEN>",
"GLPI_V2_CLIENT_SECRET": "<YOUR_GLPI_V2_CLIENT_SECRET>",
"GLPI_V2_PASSWORD": "<YOUR_GLPI_V2_PASSWORD>"
}
}
}
}Install NexTool for GLPI MCP in VS Code CLI
$ code --add-mcp '{"name":"glpi","type":"stdio","command":"npx","args":["-y","@nextoolsolutions/mcp-glpi"],"env":{"GLPI_APP_TOKEN":"<YOUR_GLPI_APP_TOKEN>","GLPI_USER_TOKEN":"<YOUR_GLPI_USER_TOKEN>","GLPI_V2_CLIENT_SECRET":"<YOUR_GLPI_V2_CLIENT_SECRET>","GLPI_V2_PASSWORD":"<YOUR_GLPI_V2_PASSWORD>"}}'Install NexTool for GLPI MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"glpi": {
"command": "npx",
"args": [
"-y",
"@nextoolsolutions/mcp-glpi"
],
"env": {
"GLPI_APP_TOKEN": "<YOUR_GLPI_APP_TOKEN>",
"GLPI_USER_TOKEN": "<YOUR_GLPI_USER_TOKEN>",
"GLPI_V2_CLIENT_SECRET": "<YOUR_GLPI_V2_CLIENT_SECRET>",
"GLPI_V2_PASSWORD": "<YOUR_GLPI_V2_PASSWORD>"
}
}
}
}Install NexTool for GLPI MCP in Codex
$ codex mcp add glpi --env 'GLPI_APP_TOKEN=<YOUR_GLPI_APP_TOKEN>' --env 'GLPI_USER_TOKEN=<YOUR_GLPI_USER_TOKEN>' --env 'GLPI_V2_CLIENT_SECRET=<YOUR_GLPI_V2_CLIENT_SECRET>' --env 'GLPI_V2_PASSWORD=<YOUR_GLPI_V2_PASSWORD>' -- npx -y @nextoolsolutions/mcp-glpiInstall NexTool for GLPI MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.glpi] command = "npx" args = ["-y", "@nextoolsolutions/mcp-glpi"] [mcp_servers.glpi.env] GLPI_APP_TOKEN = "<YOUR_GLPI_APP_TOKEN>" GLPI_USER_TOKEN = "<YOUR_GLPI_USER_TOKEN>" GLPI_V2_CLIENT_SECRET = "<YOUR_GLPI_V2_CLIENT_SECRET>" GLPI_V2_PASSWORD = "<YOUR_GLPI_V2_PASSWORD>"
Install NexTool for GLPI MCP in Gemini CLI
$ gemini mcp add -s user -e 'GLPI_APP_TOKEN=<YOUR_GLPI_APP_TOKEN>' -e 'GLPI_USER_TOKEN=<YOUR_GLPI_USER_TOKEN>' -e 'GLPI_V2_CLIENT_SECRET=<YOUR_GLPI_V2_CLIENT_SECRET>' -e 'GLPI_V2_PASSWORD=<YOUR_GLPI_V2_PASSWORD>' glpi npx -- -y @nextoolsolutions/mcp-glpiInstall NexTool for GLPI MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"glpi": {
"command": "npx",
"args": [
"-y",
"@nextoolsolutions/mcp-glpi"
],
"env": {
"GLPI_APP_TOKEN": "<YOUR_GLPI_APP_TOKEN>",
"GLPI_USER_TOKEN": "<YOUR_GLPI_USER_TOKEN>",
"GLPI_V2_CLIENT_SECRET": "<YOUR_GLPI_V2_CLIENT_SECRET>",
"GLPI_V2_PASSWORD": "<YOUR_GLPI_V2_PASSWORD>"
}
}
}
}Started by HostedMCP on 16 Nov 2026
We ran this command for @nextoolsolutions/mcp-glpi 3.5.7 in an isolated container with no network and no keys. It answered and listed 111 tools.
NexTool for GLPI MCP tools 111
Read from the server with tools/listglpi_list_ticketsRead-onlyList GLPI tickets of the whole instance (every ticket the connected user may see), most recently updated first by default. Filter by status (e.g. status: 'open' = not solved nor closed) and choose the sort column and direction. Each row carries status_name, type_name, priority_name (in the GLPI user's language), category_name, and requesters and assigned technicians as {id, name}. For the connected user's OWN tickets ("my tickets") use glpi_list_my_tickets instead.
glpi_list_my_ticketsRead-only"My tickets": tickets of the connected GLPI user (or of users_id) where they are requester, assigned technician or observer. Defaults: open tickets only (not solved nor closed), most recently updated first. Each row names the people: requesters, assigned and observers as {id, name}, plus status_name and my_roles. Use this for "meus chamados", "my open tickets", "tickets assigned to me".
glpi_get_ticketRead-onlyRetrieve a single ticket by ID. IDs come with names beside them (recipient_name, category_name, entity_name; status_name, type_name, priority_name in the GLPI user's language). Requesters, technicians and observers are not ticket fields: list them with glpi_list_ticket_users (and groups with glpi_list_ticket_groups).
glpi_create_ticketActionCreate a new ticket. Common fields: name (title), content (description), entities_id, users_id_requester, itilcategories_id, type (1=Incident, 2=Request), urgency, impact, priority.
glpi_update_ticketActionUpdate an existing ticket by ID.
glpi_list_changesRead-onlyList change management items, most recently updated first by default, with status_name and priority_name (in the GLPI user's language) and category_name.
glpi_get_changeRead-onlyRetrieve a change by ID, with names beside the IDs and status/priority labels in the GLPI user's language.
glpi_create_changeActionCreate a new change. Common fields: name, content, entities_id, users_id_requester.
glpi_update_changeActionUpdate an existing change by ID.
glpi_list_change_followupsRead-onlyList followups (comments) of a change, with the author's name (user_name).
glpi_list_problemsRead-onlyList problem management items, most recently updated first by default, with status_name and priority_name (in the GLPI user's language) and category_name.
glpi_get_problemRead-onlyRetrieve a problem by ID, with names beside the IDs and status/priority labels in the GLPI user's language.
Show all 111 toolsShow fewer tools
glpi_create_problemActionCreate a new problem. Common fields: name, content, entities_id, users_id_requester.
glpi_update_problemActionUpdate an existing problem by ID.
glpi_list_problem_followupsRead-onlyList followups (comments) of a problem, with the author's name (user_name).
glpi_searchRead-onlySearch GLPI items with criteria. itemtype: Ticket, User, Change, Problem, Computer, etc. Each criterion is {field, searchtype, value, link}: field = search option ID, searchtype = contains | equals | notequals | lessthan | morethan | under, link = AND | OR (omit on the first). Rows come keyed by the search option names in the GLPI user's language ('Título', 'ID', 'Status'...); coded columns (status, priority, urgency, impact, type, approval) hold the GLPI label and the code sits beside it as '<name> (id)' (e.g. 'Status': 'Solucionado', 'Status (id)': 5). named_columns=false returns the raw search keyed by option ID ('1', '2'...). Use glpi_list_search_options to discover the option IDs for criteria, forcedisplay and sort.
glpi_add_followupActionAdd a comment/followup to a ticket.
glpi_list_followupsRead-onlyList followups (comments) of a ticket, oldest first, with the author's name (user_name).
glpi_add_solutionActionAdd a solution to a ticket (status changes to Solved).
glpi_list_ticket_validationsRead-onlyList approval/validation requests for a ticket, with requester and approver names (user_name, validator_name) and status_name in the GLPI user's language (status: 1 = not subject to approval, 2 = waiting, 3 = granted, 4 = refused).
glpi_create_ticket_validationActionCreate an approval request assigning a validator (users_id_validate).
glpi_update_ticket_validationActionApprove/refuse a validation (status: accepted/refused) or change the approver.
glpi_delete_ticket_validationActionRemove a validation request by ID.
glpi_get_userRead-onlyRetrieve a user by ID.
glpi_search_user_by_emailRead-onlyFind users by exact email address (returns the user items: id, login, real name, first name...).
glpi_list_usersRead-onlyList all users with optional pagination and dropdown expansion.
glpi_create_userActionCreate a new GLPI user. Required: name (login). Common: realname, firstname, password, email (via _useremails array).
glpi_update_userActionUpdate an existing user by ID.
glpi_list_documentsRead-onlyList documents with optional pagination.
glpi_get_documentRead-onlyRetrieve a document by ID.
glpi_create_documentActionCreate a document (metadata). Fields: name, entities_id, comment, etc.
glpi_delete_documentActionPermanently delete a document by ID.
glpi_list_document_itemsRead-onlyList links between documents and other items.
glpi_get_document_itemRead-onlyRetrieve a Document_Item link by ID.
glpi_create_document_itemActionCreate a link between a document and an item (Ticket, KnowbaseItem, etc.).
glpi_delete_document_itemActionRemove a Document_Item link by ID.
glpi_list_knowbase_itemsRead-onlyList knowledge base articles with optional pagination.
glpi_get_knowbase_itemRead-onlyRetrieve a knowledge base article by ID.
glpi_create_knowbase_itemActionCreate a new knowledge base article. Fields: name, answer (HTML content), knowbaseitemcategories_id, etc.
glpi_update_knowbase_itemActionUpdate a knowledge base article by ID.
glpi_delete_knowbase_itemActionPermanently delete a knowledge base article.
glpi_list_knowbase_categoriesRead-onlyList knowledge base categories with optional pagination.
glpi_get_knowbase_categoryRead-onlyRetrieve a knowledge base category by ID.
glpi_create_knowbase_categoryActionCreate a new knowledge base category.
glpi_update_knowbase_categoryActionUpdate a knowledge base category by ID.
glpi_delete_knowbase_categoryActionPermanently delete a knowledge base category.
glpi_list_entitiesRead-onlyList GLPI entities (organizational units) with optional pagination.
glpi_get_entityRead-onlyRetrieve an entity by ID.
glpi_create_entityActionCreate a new entity. Fields: name (required), entities_id (parent, 0=Root), comment, address, etc.
glpi_update_entityActionUpdate an existing entity by ID.
glpi_delete_entityActionPermanently delete an entity by ID. WARNING: irreversible action.
glpi_get_rule_ticketRead-onlyRetrieve a ticket business rule (RuleTicket) by ID.
glpi_list_rule_ticket_criteriaRead-onlyList criteria (conditions) of a specific ticket rule (sub-items of RuleTicket).
glpi_list_rule_ticket_actionsRead-onlyList actions of a specific ticket rule (sub-items of RuleTicket).
glpi_list_rule_criteriaRead-onlyList rule criteria via GET /RuleCriteria. Optionally filter by rules_id (works for any rule type: RuleTicket, RuleChange, RuleMailCollector).
glpi_list_rule_actionsRead-onlyList rule actions via GET /RuleAction. Optionally filter by rules_id (works for any rule type: RuleTicket, RuleChange, RuleMailCollector).
glpi_update_rule_actionActionUpdate a rule action by ID. Fields: action_type, field, value.
glpi_list_rulesRead-onlyList all ticket business rules (RuleTicket) with optional pagination.
glpi_create_rule_ticketActionCreate a new ticket business rule. Fields: name, match (AND/OR), is_active, sub_type, ranking, etc.
glpi_create_rule_criteriaActionCreate a new criteria for a rule. Fields: rules_id, criteria (field name), condition, pattern.
glpi_create_rule_actionActionCreate a new action for a rule. Fields: rules_id, action_type (assign/regex_result/append_regex_result), field, value.
glpi_list_itil_followup_templatesRead-onlyList ITIL followup templates (predefined followup texts).
glpi_get_itil_followup_templateRead-onlyRetrieve a followup template by ID.
glpi_create_itil_followup_templateActionCreate a new followup template. Fields: name, content, comment, itemtype (Ticket/Change/Problem).
glpi_update_itil_followup_templateActionUpdate a followup template by ID.
glpi_list_search_optionsRead-onlyList available search fields for an itemtype. Critical for building search criteria with glpi_search. Returns field IDs, names, and types.
glpi_change_active_entitiesActionChange the active entity for the current session. Essential for multi-entity GLPI instances. Use is_recursive=true to include sub-entities.
glpi_get_full_sessionRead-onlyGet the full session info including active entity, profile, and user details. Useful for debugging and verifying the current session context.
glpi_list_ticket_usersRead-onlyList all users linked to a ticket (requesters, observers, assigned), with each person's name (user_name) beside users_id and type_name (in the GLPI user's language). type: 1=Requester, 2=Assigned, 3=Observer.
glpi_add_ticket_userActionAdd a user to a ticket as requester, observer, or assigned. type: 1=Requester, 2=Assigned, 3=Observer.
glpi_delete_ticket_userActionRemove a user-ticket link by Ticket_User ID (get the ID from glpi_list_ticket_users).
glpi_list_ticket_groupsRead-onlyList all groups linked to a ticket (requester, observer, assigned), with each group's name (group_name) beside groups_id and type_name (in the GLPI user's language). type: 1=Requester, 2=Assigned, 3=Observer.
glpi_add_ticket_groupActionAdd a group to a ticket as requester, observer, or assigned. type: 1=Requester, 2=Assigned, 3=Observer.
glpi_delete_ticket_groupActionRemove a group-ticket link by Group_Ticket ID (get the ID from glpi_list_ticket_groups).
glpi_list_ticket_tasksRead-onlyList tasks (to-do items) for a ticket, with author, technician and group names (user_name, tech_name, tech_group_name).
glpi_add_ticket_taskActionAdd a task to a ticket. Fields: tickets_id, content (required). Optional: is_private (0/1), state (0=Info, 1=To do, 2=Done), actiontime (seconds), users_id_tech (assigned technician).
glpi_list_change_tasksRead-onlyList tasks for a change, with author, technician and group names.
glpi_list_problem_tasksRead-onlyList tasks for a problem, with author, technician and group names.
glpi_list_itil_categoriesRead-onlyList ITIL categories (ticket/change/problem classification).
glpi_get_itil_categoryRead-onlyRetrieve an ITIL category by ID.
glpi_list_groupsRead-onlyList GLPI groups with optional pagination.
glpi_get_groupRead-onlyRetrieve a group by ID.
glpi_add_change_followupActionAdd a comment/followup to a change.
glpi_add_problem_followupActionAdd a comment/followup to a problem.
glpi_add_change_solutionActionAdd a solution to a change (status changes to Solved).
glpi_add_problem_solutionActionAdd a solution to a problem (status changes to Solved).
glpi_get_my_entitiesRead-onlyGet the list of entities available to the current user.
glpi_get_my_profilesRead-onlyGet the list of profiles available to the current user.
glpi_list_locationsRead-onlyList GLPI locations with optional pagination.
glpi_get_locationRead-onlyRetrieve a location by ID.
glpi_list_assetsRead-onlyList assets of a given type (Computer, Monitor, Printer, NetworkEquipment, Peripheral, Phone, Software, Rack, Enclosure), with location_name, state_name and user_name beside the IDs. Use glpi_search for filtered queries.
glpi_get_assetRead-onlyRetrieve a single asset by type and ID. For hardware detail use glpi_get_asset_details.
glpi_get_asset_detailsRead-onlyUse this read-only tool to inspect one known GLPI hardware asset by type and ID. It returns the base asset record plus the devices and disks sections by default; when GLPI has inventoried them, these sections include the operating system, processors, memory and storage. Request the softwares or networkports section only when the user asks for installed software or network interfaces because those lists can be large. Use glpi_get_asset when only the base asset record is needed. This tool does not modify the asset.
glpi_create_assetActionCreate an asset. Common fields: name, entities_id, serial, otherserial, locations_id, states_id, manufacturers_id, users_id, comment.
glpi_update_assetActionUpdate an existing asset by type and ID.
glpi_list_reservation_itemsRead-onlyList items flagged as reservable (the catalogue reservations point at).
glpi_list_reservationsRead-onlyList reservations (bookings) of reservable items.
glpi_get_reservationRead-onlyRetrieve a reservation by ID.
glpi_create_reservationActionBook a reservable item. begin/end use 'YYYY-MM-DD HH:MM:SS'. reservationitems_id comes from glpi_list_reservation_items (not the asset ID).
glpi_update_reservationActionUpdate an existing reservation by ID.
glpi_count_itemsRead-onlyCount matching items without transferring them — answers 'how many' in one cheap call. Use glpi_list_search_options to discover criteria field IDs.
glpi_get_ticket_statsRead-onlyTicket counts per built-in status (New, Processing assigned/planned, Pending, Solved, Closed), other_status_count for codes outside 1–6, and the total, without listing the tickets. Report other statuses separately and check counts_consistent before reporting an exact breakdown. For open tickets only, filter status (field 12) equals 'notold'; unfiltered counts include solved and closed tickets. Optional criteria narrow the scope, e.g. one entity: [{field: 80, searchtype: 'equals', value: <entity id>}] (Ticket search option IDs: 80 = entity, 4 = requester, 5 = technician, 7 = category; same criteria shape as glpi_search).
glpi_list_timelineRead-onlyFollowups, tasks, solutions and validations of a ticket, change or problem, merged into one chronological list (oldest first; order 'desc' for the latest first), with the people's names (user_name, tech_name, validator_name) and the solution type name. Replaces calling the four list tools separately and interleaving them by hand.
glpi_list_webhooksRead-onlyList configured webhooks (event, itemtype, target URL, active flag). Requires GLPI 10.0.7 or newer.
glpi_get_webhookRead-onlyRetrieve a webhook definition by ID, including its payload template.
glpi_create_webhookActionCreate a webhook. Common fields: name, url, itemtype (e.g. Ticket), event (new, update, delete), is_active, payload, http_method, use_cra_challenge.
glpi_update_webhookActionUpdate a webhook definition by ID.
glpi_set_webhook_activeActionTurn a webhook on or off without touching the rest of its definition.
glpi_delete_webhookActionDelete a webhook. Set purge to remove it permanently instead of trashing it.
glpi_list_webhook_deliveriesRead-onlyDelivery queue (QueuedWebhook): what was sent, when, and what is still pending, newest first. Filter by webhook name, or only_failed to see what has been retried.
glpi_retry_webhook_deliveryActionQueue a failed delivery for another attempt by resetting its send time and retry counter. The GLPI cron does the actual sending — there is no immediate-send endpoint.
Configuration
GLPI_APP_TOKENSecretGLPI API Application Token
GLPI_USER_TOKENSecretGLPI API User Token (API v1 tools)
GLPI_V2_CLIENT_SECRETSecretOAuth2 client secret (API v2)
GLPI_V2_PASSWORDSecretPassword of that user (API v2)
GLPI_ALLOW_DELETEEnable destructive tools (default false)
GLPI_DEFAULT_PAGE_SIZEItems returned when no range is given (default 25)
GLPI_IDEMPOTENCY_WINDOWSeconds an identical create is replayed instead of repeated (default 120, 0 disables)
GLPI_MAX_PAGE_SIZEHard ceiling of items per call (default 200)
GLPI_MAX_RETRIESMax retry attempts on 429/5xx (default 3)
GLPI_READ_ONLYBlock every write and destructive tool (default false)
GLPI_REQUIRE_DELETE_REASONRequire a reason on destructive tools (default true)
GLPI_RESOURCE_CACHE_TTLResource cache TTL in ms (default 300000)
GLPI_TIMEOUTRequest timeout in ms (default 30000)
GLPI_TOOLSETSNamed tool presets, comma-separated: core, tickets, itil, assets, kb, documents, users, search, admin, v2
GLPI_TOOLS_EXCLUDEComma-separated globs: drop matching tools
GLPI_TOOLS_INCLUDEComma-separated globs: register matching tools (adds to GLPI_TOOLSETS; with neither set, every tool registers)
GLPI_URLGLPI instance URL for the API v1 tools (apirest.php or api.php/v1)
GLPI_V2_API_VERSIONAPI version path, e.g. v2.2 (default v2)
GLPI_V2_CLIENT_IDOAuth2 client ID (API v2)
GLPI_V2_SCOPEOAuth2 scope (default api)
GLPI_V2_URLGLPI 11 URL for the API v2 tools (glpi_v2_*)
GLPI_V2_USERNAMEGLPI user for the OAuth2 password grant (API v2)
MCP_INSTANCES_FILE
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSPass
- Destructive tools are labelledNot checked
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHubNexTool MCP for GLPI
Connect Claude and other MCP clients to your GLPI. One MCP server for both GLPI APIs; each tool family turns on with its own credentials:
| Family | API | Tools | Enabled by |
|---|---|---|---|
glpi_* |
classic REST (apirest.php) or api.php/v1 — GLPI 9.5, 10 and 11 |
111 | GLPI_URL + GLPI_USER_TOKEN (+ GLPI_APP_TOKEN) |
glpi_v2_* |
High-level API v2 over OAuth2 — GLPI 11 | 55 | GLPI_V2_URL + GLPI_V2_CLIENT_ID/SECRET + GLPI_V2_USERNAME/PASSWORD |
Until 2.x the v2 family was a separate package (mcp-glpi-v2); since 3.0.0 it lives here, with
the same tool names and schemas. Both families share the write policy, payload formatting and
create idempotency below.
Not affiliated with Teclib'. GLPI is a registered trademark of Teclib'.
Tool selection. GLPI_TOOLSETS picks named presets (tickets,kb; see
Toolsets); GLPI_TOOLS_INCLUDE / GLPI_TOOLS_EXCLUDE take comma-separated globs
on tool names (glpi_*ticket*,glpi_search, *webhook*). Toolsets and include globs add up;
exclude always wins; with neither toolsets nor include globs every tool registers. An unknown
toolset name fails at startup. Fewer tools, less context per session.
Several instances can share this one binary with different env files.
Two ways to run
| Entry | Transport | Instances | Authentication |
|---|---|---|---|
dist/index.js (mcp-glpi) |
stdio | one, from the environment | none (local process) |
dist/http.js (mcp-glpi-http) |
Streamable HTTP, /mcp/<instance> |
many, from MCP_INSTANCES_FILE |
Authorization: Bearer <key>, required |
The HTTP entry is the one meant to serve every NexTool environment from one place. A key
opens only the instances it was granted, a session stays bound to the key and instance that
opened it, GLPI sessions, OAuth tokens and catalogue caches are kept per credential, and
create idempotency is shared per instance across sessions. One JSON audit line per request
goes to stdout (key, instance, methods, tools; never arguments or credentials).
GET /healthz answers without authentication.
Keys live in the instances file as SHA-256 hashes only (mode 600; it is re-read when it changes):
{
"instances": {
"acme": { "env": { "GLPI_URL": "https://glpi.acme.example", "GLPI_USER_TOKEN": "…", "GLPI_APP_TOKEN": "…" } }
},
"keys": [{ "name": "laptop", "sha256": "<sha256 hex of the key>", "instances": ["acme"] }]
}
KEY=$(openssl rand -hex 32) # give it to the client once
printf %s "$KEY" | sha256sum | cut -d' ' -f1 # goes into "sha256"
MCP_INSTANCES_FILE=instances.json MCP_HTTP_PORT=8787 npx mcp-glpi-http
A hosted, multi-tenant version with sign-in through the NexTool portal is available at https://mcp.nextoolsolutions.com/mcp.
Other variables: MCP_HTTP_HOST (default 127.0.0.1), MCP_ALLOWED_HOSTS (Host header
allowlist), MCP_SESSION_IDLE_MIN (default 30). The file is re-read when it changes.
What it exposes
-
111 API v1 tools (60 read / 42 write / 9 destructive) over tickets, changes, problems, the unified timeline, validations, assets and reservations, webhooks, users, groups, entities, documents, the knowledge base, rules and search.
-
4 resources (
glpi://entities,glpi://itil-categories,glpi://request-types,glpi://code-maps) so catalogue lookups do not cost a tool call. -
4 prompts for triage, recurrence investigation, requester history and asset context. A prompt is offered only when every tool it names is registered (with
GLPI_TOOLSETS=kbthere is none). -
55 API v2 tools (
glpi_v2_*): entities, ITIL with team members and timeline, users, groups, knowledge base, dropdowns, documents, rules, session and health check.
Listing tickets
| Need | Tool | Defaults |
|---|---|---|
| "My tickets" (the connected user's) | glpi_list_my_tickets |
open only, latest update first, any role |
| Tickets of the whole instance | glpi_list_tickets |
every status, latest update first |
| Arbitrary criteria | glpi_search |
GLPI search order |
glpi_list_my_tickets:role(any|requester|assigned|observer),status,sort,order,range,users_id(another user; default the session user fromgetFullSession). Rows carryrequesters/assigned/observersas{id, name},requester_groups,assigned_groups,status_name,type_nameandmy_roles; the result also hastotalanduser.glpi_list_tickets: newstatus,sortandorder(the oldrangeandexpand_dropdownskeep working). With a status filter the result also hastotal. Rows carrystatus_name,type_name,priority_name,category_name, andrequesters/assignedas{id, name}(one search per 50 tickets, not one call per ticket).statustakes one name or a list:new,assigned(=processing),planned,pending,solved,closed, andopen(= new + assigned + planned + pending, GLPI's "not old").sort:date_mod(default),date,id,priority,status,name,solvedate,closedate;order:desc(default) orasc.glpi_v2_list_ticketstakes the samestatusnames and sorts bydate_mod:descby default. The v2 API cannot filter on the team (GLPI 11.0.7 ignores or rejects ateamfilter), so "my tickets" is a v1 tool.glpi_list_changes/glpi_list_problems(and the v2 ones) also default to latest update first.
Names next to IDs
Sub-items keep their IDs and gain names: glpi_list_ticket_users (user_name, type_name),
glpi_list_ticket_groups (group_name, type_name), followups (user_name), tasks
(user_name, tech_name, tech_group_name), validations (user_name, validator_name,
status_name), glpi_list_timeline (all of these, plus solutiontype_name and
user_name_approval on solutions), glpi_get_ticket (recipient_name, category_name,
entity_name, requesttype_name, location_name, status_name, type_name, priority_name,
urgency_name, impact_name), problems and changes (category_name, status_name,
priority_name; the single item also the people and entity) and glpi_list_assets
(location_name, state_name, user_name). Names are read with GET // through a
5-minute cache per credential; a name the user cannot read stays null.
Labels of codes (*_status, type_name, priority_name...) are in the language of the GLPI
session (getFullSession → glpilanguage, cached per credential), with GLPI's own texts:
pt_BR, pt_PT, es_ES, fr_FR, it_IT and de_DE have tables (taken from GLPI 11's locales/*.po), a
regional variant uses its family (es_MX → es_ES), anything else GLPI's English. Before 3.5.0 the
v1 tools always answered in English ("Solved") while the v2 ones answered in the GLPI language
("Solucionado").
The API v2 labels the status itself but sends priority, urgency, impact and the ticket type as
numbers. Since 3.5.1 the v2 ticket/change/problem tools add priority_name, urgency_name,
impact_name (and type_name on tickets) beside the codes, in the language whose status table
matches the status labels the API returned (the v2 session carries no language); the timeline adds
status_name to validations and solutions and state_name to tasks, with the language cached per
credential (or read from one ticket). English when nothing matches.
glpi_search keys its rows by search option name in the GLPI user's language ("Título",
"Status", "Última atualização") by default since 3.5.0; named_columns: false returns the
numeric option IDs ("1", "12", "19"). Since 3.5.1 coded columns (status, priority, urgency,
impact, ticket type, approval and solution-approval status) hold the label in the session language
and the code sits beside it under "<name> (id)": "Status": "Solucionado", "Status (id)": 5.
A column is labelled only when its search option points at a known table/field; the markdown table
leaves the (id) columns out, and named_columns: false stays the raw search.
Full reference: docs/TOOLS.md (v1) and docs/v2/TOOLS.md (v2);
OAuth2 setup in docs/v2/SETUP.md.
Toolsets
Named presets for GLPI_TOOLSETS (or the toolsets option of instanceFromConfig). Domain
presets hold both families; a family still needs its credentials to register. A tool can be in
more than one preset, and every tool is in at least one besides core (asserted by the tests).
core is the lean default for hosted use: every read tool of the everyday presets (no webhook,
rule or session internals) plus the non-destructive ticket operations.
Presets are self-contained (asserted by the tests): a tool named in another tool's description
or parameters is in every preset that holds the tool naming it. That is why tickets carries
glpi_search / glpi_list_search_options and the user/group reads that put names on people,
and assets carries the generic search its list tool points to.
| Preset | Tools (v1 + v2) | What |
|---|---|---|
core |
93 (59 + 34) | reads of tickets/itil/assets/kb/documents/users/search + entity and people reads, plus create/update ticket, followup, solution, task, validation, actors |
tickets |
53 (33 + 20) | ticket lifecycle incl. my tickets, plus search and user/group reads |
itil |
46 (24 + 22) | problems and changes, shared timeline and categories, user/group reads |
assets |
15 (14 + 1) | assets, reservations, locations, generic search |
kb |
16 (10 + 6) | knowledge base |
documents |
12 (8 + 4) | documents and document links |
users |
10 (5 + 5) | user and group reads |
search |
3 (3 + 0) | generic search, counts, search options |
admin |
55 (37 + 18) | GLPI administration: create/update users and groups, entities, session/profile, rules, followup templates, webhooks (plus the user/group reads) |
v2 |
55 (0 + 55) | every glpi_v2_* tool |
Administration with writes only in admin (3.5.0, owner's decision): creating or changing
users and groups, entities, business rules and webhooks is not in core nor in any everyday
preset (tickets, itil, assets, kb, documents, users, search); the reads that help
with a ticket (users, groups, entities) stay. The v2 preset is the whole family and still holds
them. Asserted by the tests (ADMIN_WRITE_TOOLS, EVERYDAY_TOOLSETS).
Before 3.5.0: users 15 (7 + 8), admin 42 (31 + 11). Before 3.4.0: core 92, tickets 42, itil 38, assets 13.
core (93: 59 v1 + 34 v2)
Lean default: every read tool of the everyday presets plus the non-destructive ticket operations
v1: glpi_list_tickets, glpi_list_my_tickets, glpi_get_ticket, glpi_list_followups, glpi_list_timeline, glpi_list_ticket_validations, glpi_list_ticket_users, glpi_list_ticket_groups, glpi_list_ticket_tasks, glpi_get_ticket_stats, glpi_list_itil_categories, glpi_get_itil_category, glpi_list_itil_followup_templates, glpi_get_itil_followup_template, glpi_list_changes, glpi_get_change, glpi_list_change_followups, glpi_list_change_tasks, glpi_list_problems, glpi_get_problem, glpi_list_problem_followups, glpi_list_problem_tasks, glpi_list_assets, glpi_get_asset, glpi_get_asset_details, glpi_list_reservation_items, glpi_list_reservations, glpi_get_reservation, glpi_list_locations, glpi_get_location, glpi_list_knowbase_items, glpi_get_knowbase_item, glpi_list_knowbase_categories, glpi_get_knowbase_category, glpi_list_documents, glpi_get_document, glpi_list_document_items, glpi_get_document_item, glpi_get_user, glpi_search_user_by_email, glpi_list_users, glpi_list_groups, glpi_get_group, glpi_search, glpi_count_items, glpi_list_search_options, glpi_list_entities, glpi_get_entity, glpi_get_my_entities, glpi_get_my_profiles, glpi_create_ticket, glpi_update_ticket, glpi_add_followup, glpi_add_solution, glpi_create_ticket_validation, glpi_update_ticket_validation, glpi_add_ticket_user, glpi_add_ticket_group, glpi_add_ticket_task
v2: glpi_v2_list_tickets, glpi_v2_get_ticket, glpi_v2_list_timeline, glpi_v2_list_team_members, glpi_v2_list_itil_categories, glpi_v2_get_itil_category, glpi_v2_list_request_types, glpi_v2_list_changes, glpi_v2_get_change, glpi_v2_list_problems, glpi_v2_get_problem, glpi_v2_list_locations, glpi_v2_list_kb_articles, glpi_v2_get_kb_article, glpi_v2_list_kb_categories, glpi_v2_get_kb_category, glpi_v2_list_documents, glpi_v2_get_document, glpi_v2_download_document, glpi_v2_list_users, glpi_v2_get_user, glpi_v2_get_me, glpi_v2_list_groups, glpi_v2_get_group, glpi_v2_list_entities, glpi_v2_get_entity, glpi_v2_create_ticket, glpi_v2_update_ticket, glpi_v2_add_followup, glpi_v2_add_solution, glpi_v2_add_task, glpi_v2_add_validation, glpi_v2_update_validation, glpi_v2_add_team_member
tickets (53: 33 v1 + 20 v2)
Ticket lifecycle (my tickets, followups, solutions, tasks, validations, actors, timeline) plus the search and user/group reads it points to
v1: glpi_list_tickets, glpi_list_my_tickets, glpi_get_ticket, glpi_create_ticket, glpi_update_ticket, glpi_add_followup, glpi_list_followups, glpi_add_solution, glpi_list_timeline, glpi_list_ticket_validations, glpi_create_ticket_validation, glpi_update_ticket_validation, glpi_delete_ticket_validation, glpi_list_ticket_users, glpi_add_ticket_user, glpi_delete_ticket_user, glpi_list_ticket_groups, glpi_add_ticket_group, glpi_delete_ticket_group, glpi_list_ticket_tasks, glpi_add_ticket_task, glpi_get_ticket_stats, glpi_list_itil_categories, glpi_get_itil_category, glpi_list_itil_followup_templates, glpi_get_itil_followup_template, glpi_search, glpi_list_search_options, glpi_get_user, glpi_search_user_by_email, glpi_list_users, glpi_get_group, glpi_list_groups
v2: glpi_v2_list_tickets, glpi_v2_get_ticket, glpi_v2_create_ticket, glpi_v2_update_ticket, glpi_v2_delete_ticket, glpi_v2_list_timeline, glpi_v2_add_followup, glpi_v2_add_solution, glpi_v2_add_task, glpi_v2_add_validation, glpi_v2_update_validation, glpi_v2_list_team_members, glpi_v2_add_team_member, glpi_v2_remove_team_member, glpi_v2_list_itil_categories, glpi_v2_get_itil_category, glpi_v2_list_request_types, glpi_v2_get_user, glpi_v2_get_me, glpi_v2_get_group
itil (46: 24 v1 + 22 v2)
Problems and changes (plus the shared ITIL timeline and categories, and the user/group reads)
v1: glpi_list_changes, glpi_get_change, glpi_create_change, glpi_update_change, glpi_list_change_followups, glpi_add_change_followup, glpi_add_change_solution, glpi_list_change_tasks, glpi_list_problems, glpi_get_problem, glpi_create_problem, glpi_update_problem, glpi_list_problem_followups, glpi_add_problem_followup, glpi_add_problem_solution, glpi_list_problem_tasks, glpi_list_timeline, glpi_list_itil_categories, glpi_get_itil_category, glpi_get_user, glpi_search_user_by_email, glpi_list_users, glpi_get_group, glpi_list_groups
v2: glpi_v2_list_changes, glpi_v2_get_change, glpi_v2_create_change, glpi_v2_update_change, glpi_v2_list_problems, glpi_v2_get_problem, glpi_v2_create_problem, glpi_v2_update_problem, glpi_v2_list_timeline, glpi_v2_add_followup, glpi_v2_add_solution, glpi_v2_add_task, glpi_v2_add_validation, glpi_v2_update_validation, glpi_v2_list_team_members, glpi_v2_add_team_member, glpi_v2_remove_team_member, glpi_v2_list_itil_categories, glpi_v2_get_itil_category, glpi_v2_get_user, glpi_v2_get_me, glpi_v2_get_group
assets (15: 14 v1 + 1 v2)
Assets, reservations and locations (plus generic search)
v1: glpi_list_assets, glpi_get_asset, glpi_get_asset_details, glpi_create_asset, glpi_update_asset, glpi_list_reservation_items, glpi_list_reservations, glpi_get_reservation, glpi_create_reservation, glpi_update_reservation, glpi_list_locations, glpi_get_location, glpi_search, glpi_list_search_options
v2: glpi_v2_list_locations
kb (16: 10 v1 + 6 v2)
Knowledge base articles and categories
v1: glpi_list_knowbase_items, glpi_get_knowbase_item, glpi_create_knowbase_item, glpi_update_knowbase_item, glpi_delete_knowbase_item, glpi_list_knowbase_categories, glpi_get_knowbase_category, glpi_create_knowbase_category, glpi_update_knowbase_category, glpi_delete_knowbase_category
v2: glpi_v2_list_kb_articles, glpi_v2_get_kb_article, glpi_v2_create_kb_article, glpi_v2_update_kb_article, glpi_v2_list_kb_categories, glpi_v2_get_kb_category
documents (12: 8 v1 + 4 v2)
Documents and their links to items
v1: glpi_list_documents, glpi_get_document, glpi_create_document, glpi_delete_document, glpi_list_document_items, glpi_get_document_item, glpi_create_document_item, glpi_delete_document_item
v2: glpi_v2_list_documents, glpi_v2_get_document, glpi_v2_create_document, glpi_v2_download_document
users (10: 5 v1 + 5 v2)
User and group reads (creating or changing them is in admin)
v1: glpi_get_user, glpi_search_user_by_email, glpi_list_users, glpi_list_groups, glpi_get_group
v2: glpi_v2_list_users, glpi_v2_get_user, glpi_v2_get_me, glpi_v2_list_groups, glpi_v2_get_group
search (3: 3 v1 + 0 v2)
Generic search, counts and search options
v1: glpi_search, glpi_count_items, glpi_list_search_options
admin (55: 37 v1 + 18 v2)
GLPI administration: users and groups (create/update), entities, session/profile context, business rules, followup templates, webhooks
v1: glpi_list_entities, glpi_get_entity, glpi_get_my_entities, glpi_get_my_profiles, glpi_list_users, glpi_get_user, glpi_list_groups, glpi_get_group, glpi_create_entity, glpi_update_entity, glpi_delete_entity, glpi_change_active_entities, glpi_get_full_session, glpi_list_rules, glpi_get_rule_ticket, glpi_list_rule_ticket_criteria, glpi_list_rule_ticket_actions, glpi_list_rule_criteria, glpi_list_rule_actions, glpi_create_rule_ticket, glpi_create_rule_criteria, glpi_create_rule_action, glpi_update_rule_action, glpi_list_itil_followup_templates, glpi_get_itil_followup_template, glpi_create_itil_followup_template, glpi_update_itil_followup_template, glpi_list_webhooks, glpi_get_webhook, glpi_create_webhook, glpi_update_webhook, glpi_set_webhook_active, glpi_delete_webhook, glpi_list_webhook_deliveries, glpi_retry_webhook_delivery, glpi_create_user, glpi_update_user
v2: glpi_v2_list_entities, glpi_v2_get_entity, glpi_v2_list_users, glpi_v2_get_user, glpi_v2_list_groups, glpi_v2_get_group, glpi_v2_create_entity, glpi_v2_update_entity, glpi_v2_delete_entity, glpi_v2_list_rule_collections, glpi_v2_list_rules, glpi_v2_get_rule, glpi_v2_create_rule, glpi_v2_get_session, glpi_v2_health_check, glpi_v2_create_user, glpi_v2_update_user, glpi_v2_create_group
v2 (55: 0 v1 + 55 v2)
Every GLPI 11 API v2 tool (glpi_v2_*)
As a library
The package root exports the server factory; importing it never starts a transport (the stdio
and HTTP servers are the mcp-glpi and mcp-glpi-http bins).
import { createGlpiServer, instanceFromConfig } from "@nextoolsolutions/mcp-glpi";
const instance = instanceFromConfig({
id: "acme", // lowercase letters, digits, "-"
v1: { url: "https://glpi.acme.com", userToken, appToken },
v2: { url: "https://glpi.acme.com", clientId, clientSecret, username, password, scope: "api", apiVersion: "v2.2" },
policy: { readOnly: true, allowDelete: false }, // defaults: false / false / requireDeleteReason true
toolsets: ["core"], // or "tickets,kb"
toolsInclude: ["glpi_search"], // globs, add to toolsets
toolsExclude: ["*delete*"], // globs, always win
fetchImpl, // optional, see below
});
const { server, summary } = createGlpiServer(instance, { fetchImpl, idempotencyStore });
await server.connect(transport);
instanceFromConfig never reads process.env and throws on an invalid id or URL, on unknown
toolsets and when neither v1 nor v2 is given. instanceFromEnv(id, env) builds the same
thing from GLPI_* variables. Also exported: SERVER_VERSION, the InstanceConfig /
InstanceEnv / InstanceOptions types, TOOLSETS / TOOLSET_NAMES / parseToolsets, the
error classes (GlpiHttpError, GlpiApiError, GlpiV2ApiError, GlpiRedirectError,
GlpiPolicyError) and IdempotencyStore.
fetchImpl. Same call shape as fetch ((url, init) => Promise<Response>), used for every
GLPI request: v1 session and calls, v2 token and calls, assets and webhooks. A host can inject
one that validates the resolved IP. It always receives redirect: "manual".
Safety defaults
- Destructive tools are off unless
GLPI_ALLOW_DELETE=true, and require a writtenreason. GLPI_READ_ONLY=trueblocks every write before it reaches GLPI — set on customer instances.- Every tool publishes MCP annotations derived from its name:
title,readOnlyHint(reads),destructiveHint(delete/purge/remove),idempotentHint(reads,update_*/set_*, deletes) andopenWorldHint: false. - Redirects are never followed: a 3xx from GLPI becomes
redirect not followed: <status> -> <host>(GlpiRedirectError), so session and OAuth headers never reach another host. - The v2 client only talks to the
GLPI_V2_URLorigin; an absolute URL to any other host is refused before a request goes out. - Repeating a
create_/add_call with identical arguments within 120s replays the first result (replayed: true) instead of creating a second record.
Payload
Read tools default to fields: "essential": GLPI's internal bookkeeping (SLA/OLA counters,
delay statistics, HAL links; API v2 durations) is dropped and TinyMCE richtext is flattened to
plain text. Pass fields: "all" for the raw payload.
format: "markdown" returns a table for listings and key: value lines for one item (long
texts never cut there). The markdown is in the text block and in structuredContent
({ data: "<markdown>", format: "markdown", count, note }): clients that support structured
results (Claude among them) give the model structuredContent, so a text-only rendering was
ignored before 3.4.0. JSON stays the default.
Listing tables are compact (3.5.0): a raw ticket row has 22 columns, bare IDs among them, so each
kind of listing has its own column set (src/markdown-views.ts):
| Listing | Columns |
|---|---|
tickets (glpi_list_tickets, glpi_list_my_tickets, glpi_v2_list_tickets) |
id, title, status, category, requester, technician, priority, updated |
| problems, changes (v1 and v2) | id, title, status, category, (v2: technician), priority, updated |
timeline (glpi_list_timeline, glpi_v2_list_timeline) |
type, id, date, author, summary — one line per entry (validations: status → approver · comment) |
| followups / tasks | id, date, author, (tasks: technician), private, summary |
| assets | id, name, serial, inventory number, status, location, user, updated |
| users (v1 and v2) | id, login, name, active, last login |
| KB articles (v1 and v2) | id, title, (v2: category), FAQ, views, updated |
The JSON result keeps every field, and fields: "all" draws every column in markdown too.
NexTool for GLPI MCP questions
How do I add NexTool for GLPI MCP to Claude Code?
Run claude mcp add --env 'GLPI_APP_TOKEN=<YOUR_GLPI_APP_TOKEN>' --env 'GLPI_USER_TOKEN=<YOUR_GLPI_USER_TOKEN>' --env 'GLPI_V2_CLIENT_SECRET=<YOUR_GLPI_V2_CLIENT_SECRET>' --env 'GLPI_V2_PASSWORD=<YOUR_GLPI_V2_PASSWORD>' glpi -- npx -y @nextoolsolutions/mcp-glpi in your terminal. Add --scope user to make it available in every project.
How do I add NexTool for GLPI MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does NexTool for GLPI MCP provide?
It exposes 111 tools, including glpi_list_tickets, glpi_list_my_tickets, glpi_get_ticket, glpi_create_ticket, glpi_update_ticket.
Which versions of GLPI are supported?
The server supports GLPI 9.5, 10, and 11.
Can I run multiple GLPI instances with one server?
Yes, the HTTP entry point allows serving multiple NexTool environments from one place using an instances file.