NexTool MCP for GLPI

Add a comment/followup to a change.

Add a solution to a change (status changes to Solved).

Add a comment/followup to a ticket.

Add a comment/followup to a problem.

Add a solution to a problem (status changes to Solved).

Add a solution to a ticket (status changes to Solved).

Add a group to a ticket as requester, observer, or assigned. type: 1=Requester, 2=Assigned, 3=Observer.

Add 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).

Add a user to a ticket as requester, observer, or assigned. type: 1=Requester, 2=Assigned, 3=Observer.

Change the active entity for the current session. Essential for multi-entity GLPI instances. Use is_recursive=true to include sub-entities.

Count matching items without transferring them — answers 'how many' in one cheap call. Use glpi_list_search_options to discover criteria field IDs.

Create an asset. Common fields: name, entities_id, serial, otherserial, locations_id, states_id, manufacturers_id, users_id, comment.

Create a new change. Common fields: name, content, entities_id, users_id_requester.

Create a document (metadata). Fields: name, entities_id, comment, etc.

Create a link between a document and an item (Ticket, KnowbaseItem, etc.).

Create a new entity. Fields: name (required), entities_id (parent, 0=Root), comment, address, etc.

Create a new followup template. Fields: name, content, comment, itemtype (Ticket/Change/Problem).

Create a new knowledge base category.

Create a new knowledge base article. Fields: name, answer (HTML content), knowbaseitemcategories_id, etc.

Create a new problem. Common fields: name, content, entities_id, users_id_requester.

Book a reservable item. begin/end use 'YYYY-MM-DD HH:MM:SS'. reservationitems_id comes from glpi_list_reservation_items (not the asset ID).

Create a new action for a rule. Fields: rules_id, action_type (assign/regex_result/append_regex_result), field, value.

Create a new criteria for a rule. Fields: rules_id, criteria (field name), condition, pattern.

Create a new ticket business rule. Fields: name, match (AND/OR), is_active, sub_type, ranking, etc.

Create a new ticket. Common fields: name (title), content (description), entities_id, users_id_requester, itilcategories_id, type (1=Incident, 2=Request), urgency, impact, priority.

Create an approval request assigning a validator (users_id_validate).

Create a new GLPI user. Required: name (login). Common: realname, firstname, password, email (via _useremails array).

Create a webhook. Common fields: name, url, itemtype (e.g. Ticket), event (new, update, delete), is_active, payload, http_method, use_cra_challenge.

Retrieve a single asset by type and ID. For hardware detail use glpi_get_asset_details.

Use 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.

Retrieve a change by ID, with names beside the IDs and status/priority labels in the GLPI user's language.

Retrieve a document by ID.

Retrieve a Document_Item link by ID.

Retrieve an entity by ID.

Get the full session info including active entity, profile, and user details. Useful for debugging and verifying the current session context.

Retrieve a group by ID.

Retrieve an ITIL category by ID.

Retrieve a followup template by ID.

Retrieve a knowledge base category by ID.

Retrieve a knowledge base article by ID.

Retrieve a location by ID.

Get the list of entities available to the current user.

Get the list of profiles available to the current user.

Retrieve a problem by ID, with names beside the IDs and status/priority labels in the GLPI user's language.

Retrieve a reservation by ID.

Retrieve a ticket business rule (RuleTicket) by ID.

Retrieve 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).

Ticket 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: }] (Ticket search option IDs: 80 = entity, 4 = requester, 5 = technician, 7 = category; same criteria shape as glpi_search).

Retrieve a user by ID.

Retrieve a webhook definition by ID, including its payload template.

List 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.

List followups (comments) of a change, with the author's name (user_name).

List change management items, most recently updated first by default, with status_name and priority_name (in the GLPI user's language) and category_name.

List tasks for a change, with author, technician and group names.

List links between documents and other items.

List documents with optional pagination.

List GLPI entities (organizational units) with optional pagination.

List followups (comments) of a ticket, oldest first, with the author's name (user_name).

List GLPI groups with optional pagination.

List ITIL categories (ticket/change/problem classification).

List ITIL followup templates (predefined followup texts).

List knowledge base categories with optional pagination.

List knowledge base articles with optional pagination.

List GLPI locations with optional pagination.

"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".

List followups (comments) of a problem, with the author's name (user_name).

List problem management items, most recently updated first by default, with status_name and priority_name (in the GLPI user's language) and category_name.

List tasks for a problem, with author, technician and group names.

List items flagged as reservable (the catalogue reservations point at).

List reservations (bookings) of reservable items.

List rule actions via GET /RuleAction. Optionally filter by rules_id (works for any rule type: RuleTicket, RuleChange, RuleMailCollector).

List rule criteria via GET /RuleCriteria. Optionally filter by rules_id (works for any rule type: RuleTicket, RuleChange, RuleMailCollector).

List all ticket business rules (RuleTicket) with optional pagination.

List actions of a specific ticket rule (sub-items of RuleTicket).

List criteria (conditions) of a specific ticket rule (sub-items of RuleTicket).

List available search fields for an itemtype. Critical for building search criteria with glpi_search. Returns field IDs, names, and types.

List 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.

List 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.

List tasks (to-do items) for a ticket, with author, technician and group names (user_name, tech_name, tech_group_name).

List 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.

List 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).

Followups, 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.

List all users with optional pagination and dropdown expansion.

Delivery 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.

List configured webhooks (event, itemtype, target URL, active flag). Requires GLPI 10.0.7 or newer.

Queue 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.

Search 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 ' (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.

Find users by exact email address (returns the user items: id, login, real name, first name...).

Turn a webhook on or off without touching the rest of its definition.

Update an existing asset by type and ID.

Update an existing change by ID.

Update an existing entity by ID.

Update a followup template by ID.

Update a knowledge base category by ID.

Update a knowledge base article by ID.

Update an existing problem by ID.

Update an existing reservation by ID.

Update a rule action by ID. Fields: action_type, field, value.

Update an existing ticket by ID.

Approve/refuse a validation (status: accepted/refused) or change the approver.

Update an existing user by ID.

Update a webhook definition by ID.