Open source + hosted (beta)
NexTool MCP for GLPI
Connect Claude, ChatGPT, Cursor, VS Code and Windsurf to your GLPI and work on tickets by talking to the AI.
An MCP (Model Context Protocol) server for GLPI 10 and 11: tickets, ITIL, assets, knowledge base and users, through REST API v1 and the GLPI 11 API v2.
Not affiliated with Teclib'. GLPI is a registered trademark of Teclib'.
What NexTool MCP for GLPI is
MCP is the open standard AI assistants use to call external tools. NexTool MCP for GLPI gives the assistant GLPI tools, with descriptions and safety rules, so it can work on your real data.
Tickets and ITIL
Tickets, followups, tasks, solutions, validations, problems and changes, with the unified timeline.
Assets and reservations
Computers, monitors, printers and other assets, with details, reservations and locations.
Knowledge base
Search and read articles and categories; create and edit when the profile allows it.
Users, groups and entities
User lookup by e-mail, groups, entities and the token's active profiles.
REST API v1 and API v2
Over 110 tools on the classic REST API (GLPI 10 and 11) and over 50 on the GLPI 11 API v2, over OAuth2.
Your AI assistant
Claude, ChatGPT, Cursor, VS Code, Windsurf or any MCP-compatible client.
Two ways to use it
The service hosted by NexTool, with nothing to install, or the open source server running on your machine.
Open beta
Hosted by NexTool
- One address:
https://mcp.nextoolsolutions.com/mcp - Sign in with your NexTool portal account
- Connector for Claude and ChatGPT, nothing to install
- GLPI credentials stored encrypted
- Requires a GLPI reachable from the internet
Open to everyone and free during the beta. Create your NexTool portal account and connect your GLPI under My Account → NexTool MCP.
Available now
Open source (local)
- Package
@nextoolsolutions/mcp-glpi, MIT license - Runs on your computer or server
- Works with a GLPI on your intranet
- You control tokens, tools and read-only mode
- Free, with open source code on GitHub
How to connect the hosted version Open beta
Create your free NexTool portal account, register the connection to your GLPI under My Account → NexTool MCP and use the address below in your assistant. On first use, it asks you to sign in to the portal.
- 1
In Claude, open Settings → Connectors.
- 2
Click Add custom connector and paste the URL:
https://mcp.nextoolsolutions.com/mcp - 3
Sign in with your NexTool portal account and authorize access.
- 1
In ChatGPT, under Settings → Apps & Connectors, turn on developer mode (under Advanced).
- 2
Create a new connector and enter the MCP server URL:
https://mcp.nextoolsolutions.com/mcp - 3
Sign in with your NexTool portal account and authorize access.
Developer mode availability depends on your ChatGPT plan.
- 1
Add the server:
claude mcp add --transport http nextool https://mcp.nextoolsolutions.com/mcp - 2
Inside Claude Code, run
/mcpand choose to authenticate: the browser opens the portal sign-in./mcp - 3
Prefer a key? Generate one under My Account → NexTool MCP in the portal and send it in the header:
claude mcp add --transport http nextool https://mcp.nextoolsolutions.com/mcp \ --header "Authorization: Bearer nxm_..."
Cursor: ~/.cursor/mcp.json (or .cursor/mcp.json in the project)
{
"mcpServers": {
"nextool": {
"url": "https://mcp.nextoolsolutions.com/mcp",
"headers": { "Authorization": "Bearer nxm_..." }
}
}
}
VS Code: .vscode/mcp.json in the project
{
"servers": {
"nextool": {
"type": "http",
"url": "https://mcp.nextoolsolutions.com/mcp",
"headers": { "Authorization": "Bearer nxm_..." }
}
}
}
The nxm_ key is shown only once, when it is generated. Keep it like a password and revoke it in the portal if it leaks.
Your GLPI must be reachable from the internet over HTTPS. If it only accepts allowlisted IPs, the portal shows the IP to allow when you test the connection.
Full step by step, connection test messages and example requests: How it works
Install the open source version
The server runs as a local process started by the assistant itself. It requires Node.js 18 or later and the GLPI tokens described under Prerequisites.
Available on npm and in the official MCP Registry. The @nextoolsolutions/mcp-glpi package is published on npm and listed in the official MCP Registry as com.nextoolsolutions/glpi. The commands below use npx, which downloads and runs the latest version: no cloning or building required.
Quick test: the server starts and waits for an MCP client on standard input (stdio).
GLPI_URL=https://glpi.example.com \
GLPI_USER_TOKEN=<user-token> \
GLPI_APP_TOKEN=<app-token> \
npx -y @nextoolsolutions/mcp-glpi
Registers the server in Claude Code with its environment variables:
claude mcp add glpi \
-e GLPI_URL=https://glpi.example.com \
-e GLPI_USER_TOKEN=<user-token> \
-e GLPI_APP_TOKEN=<app-token> \
-- npx -y @nextoolsolutions/mcp-glpi
Edit claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/; Windows: %APPDATA%\Claude\) and restart Claude Desktop:
{
"mcpServers": {
"glpi": {
"command": "npx",
"args": ["-y", "@nextoolsolutions/mcp-glpi"],
"env": {
"GLPI_URL": "https://glpi.example.com",
"GLPI_USER_TOKEN": "<user-token>",
"GLPI_APP_TOKEN": "<app-token>",
"GLPI_READ_ONLY": "true"
}
}
}
}
Cursor: ~/.cursor/mcp.json (or .cursor/mcp.json in the project)
{
"mcpServers": {
"glpi": {
"command": "npx",
"args": ["-y", "@nextoolsolutions/mcp-glpi"],
"env": {
"GLPI_URL": "https://glpi.example.com",
"GLPI_USER_TOKEN": "<user-token>",
"GLPI_APP_TOKEN": "<app-token>"
}
}
}
}
VS Code: .vscode/mcp.json in the project
{
"servers": {
"glpi": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@nextoolsolutions/mcp-glpi"],
"env": {
"GLPI_URL": "https://glpi.example.com",
"GLPI_USER_TOKEN": "<user-token>",
"GLPI_APP_TOKEN": "<app-token>"
}
}
}
}
- 1
Alternative for those who prefer to build from source. Clone and build (the core first, then the server):
git clone https://github.com/NexTools-Solutions/nextool-mcp-glpi.git cd nextool-mcp-glpi/mcp-glpi-core && npm ci && npm run build cd ../mcp-glpi && npm ci && npm run build - 2
Use the absolute path of
dist/index.jsinstead ofnpx. Example in Claude Code:claude mcp add glpi \ -e GLPI_URL=https://glpi.example.com \ -e GLPI_USER_TOKEN=<user-token> \ -e GLPI_APP_TOKEN=<app-token> \ -- node /path/nextool-mcp-glpi/mcp-glpi/dist/index.jsIn the JSON files, use
"command": "node"and the path inargs.
GLPI 11: API v2 (OAuth2)
For the 55 glpi_v2_* tools, register an OAuth client in GLPI 11 and set the variables below. Both families can run together: each one turns on with its own credentials.
GLPI_V2_URL=https://glpi.example.com
GLPI_V2_CLIENT_ID=<client-id>
GLPI_V2_CLIENT_SECRET=<client-secret>
GLPI_V2_USERNAME=<username>
GLPI_V2_PASSWORD=<password>
Tool presets
With GLPI_TOOLSETS you turn on only what you need (several, comma-separated). Fewer tools, less context per conversation. Without it, every tool is registered.
GLPI_TOOLSETS=core
GLPI_TOOLSETS=tickets,kb
| Preset | What it includes |
|---|---|
core | Lean default: everyday reads and non-destructive ticket operations |
tickets | Ticket lifecycle |
itil | Problems and changes |
assets | Assets, reservations and locations |
kb | Knowledge base |
documents | Documents and links |
users | Users and groups |
search | Generic search and counts |
admin | Entities, rules, followup templates and webhooks |
v2 | Every API v2 tool |
Safety switches
| Variable | Effect |
|---|---|
GLPI_READ_ONLY=true | Blocks every write before it reaches GLPI. Recommended to start with. |
GLPI_ALLOW_DELETE=true | Enables the delete tools, off by default. Each deletion requires a written reason. |
GLPI prerequisites
They apply to both ways of using it.
- 1
Enable the REST API
In Setup → General → API, enable the REST API and login with a token. Note the API URL shown on screen.
- 2
API client (optional)
On the same screen, add an API client. If it has an App-Token, use it in
GLPI_APP_TOKEN; you can restrict the client by IP range. - 3
User token
In Administration → Users, open the user the AI will act as and, under Remote access keys, generate the API token. It goes in
GLPI_USER_TOKEN. - 4
Pick the user carefully
Every action follows that user's profile permissions in GLPI. To start, use a profile with the minimum needed or turn on read-only mode.
Hosted version: GLPI must be reachable from the internet over HTTPS. If it only accepts allowlisted IPs, the portal shows the IP to allow when you test the connection. GLPI only on your intranet? Use the open source version.
Security and privacy
What protects your GLPI, in plain language.
Every tool says what it does
All of them carry MCP read-only or destructive annotations: you and the assistant know what only reads and what changes data.
Deletes blocked
Delete tools are off by default. When enabled, each deletion requires a written reason.
Encrypted credentials (hosted)
GLPI tokens are encrypted with a key only the connector can open. Not even the portal can read them.
Audit without content
We log who used which tool and when, without storing your questions or the answers.
No duplicate records
A repeated create with the same data within 2 minutes returns the first result instead of opening another ticket.
Tokens never follow redirects
The server never follows a redirect from GLPI, so tokens never reach another address.
Plans
For the version hosted by NexTool. Start on Free; Pro is for teams that run several GLPI instances.
Free
DefaultNo charge
- 1 connected GLPI
- Over 160 GLPI tools, read and write: tickets, ITIL, assets, knowledge base and users
- Connector for Claude and ChatGPT; API key for Claude Code, Cursor and VS Code
- Optional read-only connection
- Up to 60 requests per minute
- Deletes blocked and GLPI credentials encrypted
Pro
Multiple environmentsContact us
- Everything in Free
- Up to 10 GLPI instances in one account, one connector per environment (production, staging, customers)
- Up to 300 requests per minute
- Read-only per connection (e.g. production read-only, staging with write access)
- Included in NexBot, or through the NexTool MCP Pro license of your NexTool environment
Coming soon
- Audit log you can query in the portal soon
- Organization accounts, with multiple users soon
- Semantic search for similar tickets and articles soon
- Tools from the NexTool modules soon
The hosted version is in beta and is free during the beta. The open source version, which runs on your own machine, is free and has no limit on connections. View the repository on GitHub
Frequently asked questions
Does it work with GLPI 10?
Yes. The REST API v1 covers GLPI 10 and 11; the API v2 is GLPI 11 only.
What if my GLPI is only on the intranet?
Use the open source version: it runs inside your network, next to the assistant. The hosted one needs to reach GLPI over the internet.
Is it an official Teclib' product?
No. NexTool MCP for GLPI is made by NexTool Solutions and is not affiliated with Teclib'. GLPI is a registered trademark of Teclib'.
How much does it cost?
The open source version is free, under the MIT license. The hosted one is in open beta: any NexTool portal account can use the Free plan, at no cost during the beta. Pro, for several GLPI instances, is available on request.
Can the AI delete data in my GLPI?
Only if you allow it: deletes are off by default and read-only mode blocks any write. And the AI never goes beyond the permissions of the token's user.
Does my data go through NexTool?
With the local version, no: the assistant talks straight to your GLPI. With the hosted one, calls go through the NexTool connector, which keeps only a usage audit, without questions or answers.
Talk to us
Want Pro for several GLPI instances, or have a question about NexTool MCP? Leave your contact details and tell us a bit about your setup. You don't need a form to get started: just create your portal account.
Prefer to run it on your own machine?
The open source version is already on npm, free, and runs on your machine, even with a GLPI on your intranet.
The hosted version uses your NexTool portal account. Already have one? Open My Account → NexTool MCP.
Not affiliated with Teclib'. GLPI is a registered trademark of Teclib'.