NexTool MCP for GLPI

What NexTool MCP for GLPI does

NexTool MCP for GLPI MCP server gives MCP-compatible assistants access to GLPI service-desk data and actions. Supported areas include tickets, problems, changes, assets, knowledge-base records, users, rules, and webhooks. It supports GLPI 10 and GLPI 11, using REST API v1 or, when configured, the GLPI 11 API v2.

The server runs actions as the configured GLPI user, so GLPI profiles and entity permissions remain in effect. This makes it suitable for assistants that need to search service records, review incidents, work with ITIL objects, or perform approved updates without creating a separate permission model.

How it works

The local package is distributed as @nextoolsolutions/mcp-glpi and can run over stdio. A shared Streamable HTTP mode is also available for serving multiple users or GLPI instances from one machine. The repository includes a Dockerfile for the stdio deployment.

NexTool MCP for GLPI MCP server can expose all tools by default or limit them with GLPI_TOOLSETS. Presets include core, tickets, itil, assets, kb, documents, users, search, admin, and v2. The v2 tools become available when the GLPI 11 OAuth settings are supplied.

Safety controls include MCP annotations describing read-only and destructive behavior. Setting GLPI_READ_ONLY=true blocks writes before they reach GLPI. Delete tools remain disabled unless GLPI_ALLOW_DELETE=true, and enabled deletes require a written reason. Repeated identical create calls within a short window are replayed rather than submitted again. Redirects are not followed.

Setup and configuration

Prepare GLPI by enabling its REST API and external-token login. A GLPI API client can provide an App-Token, while the selected user supplies the user token. The repository recommends a dedicated user with only the permissions the assistant needs.

A basic local launch uses Node.js 18 or newer:

GLPI_URL=https://glpi.example.com GLPI_USER_TOKEN=xxx GLPI_APP_TOKEN=yyy npx -y @nextoolsolutions/mcp-glpi

The required connection settings are GLPI_URL and GLPI_USER_TOKEN; GLPI_APP_TOKEN is optional in the documented configuration. GLPI 11 API v2 additionally uses its URL, OAuth client ID and secret, username, and password.

Claude Desktop, Claude Code, Cursor, Windsurf, and VS Code can run the local server with their MCP configuration formats. The hosted early-access service uses https://mcp.nextoolsolutions.com/mcp, requires NexTool access, and requires the GLPI instance to be reachable from the internet. Local deployment is the option for intranet-only GLPI installations.

Tools and capabilities

NexTool MCP for GLPI MCP server provides tool groups for:

• Ticket operations
• Problems and changes
• Asset management
• Knowledge-base access
• Document, user, search, and administrative operations
• GLPI 11 API v2 operations
• Configured rules and webhooks

The exact exposed set depends on GLPI_TOOLSETS and the configured GLPI API. The hosted service also provides sign-in, connector setup, encrypted GLPI credentials, rate limits, and audit logs according to the repository description.

Limitations and notes

The project is not affiliated with Teclib', and GLPI is a registered trademark of Teclib'. The hosted option is described as early access and is not appropriate for a GLPI endpoint that cannot be reached from the internet. API errors can result from invalid tokens, missing App-Tokens, restricted client IPs, login-page URLs, or redirects; the configured URL should point to the GLPI root and final origin.

The server does not bypass GLPI authorization: every action uses the configured user's profile and entities. Delete operations are additionally controlled by the local settings and are always refused on the hosted free plan.