N
NexTools-Solutions/nextool-mcp-glpi
Open-source Model Context Protocol server that connects AI assistants
★ 2·updated 2026-11-19
View on GitHub ↗Direct link · no redirect page
Install & config
Remote endpoint (mcpServers - Claude Desktop / Cursor / Windsurf)
{
"mcpServers": {
"nextools-solutions-nextool-mcp-glpi": {
"url": "https://mcp.nextoolsolutions.com/mcp"
}
}
}Paste this into the mcpServers config of Claude Desktop or Cursor. The endpoint comes from public evidence; we do not install or host it. Official Registry record: this endpoint lists no request headers. That is not the same as key-free - the project docs decide.
VS Code (.vscode/mcp.json - the key is servers, remote needs type: http)
{
"servers": {
"nextools-solutions-nextool-mcp-glpi": {
"type": "http",
"url": "https://mcp.nextoolsolutions.com/mcp"
}
}
}VS Code differs from the other three: the top-level key is <code>servers</code> and a remote endpoint also needs <code>"type": "http"</code>. Paste into .vscode/mcp.json.
Claude Code (command line)
claude mcp add --transport http nextools-solutions-nextool-mcp-glpi https://mcp.nextoolsolutions.com/mcp
Claude Code does not read a config file; add the server with this command.
Config file: macOS
~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json, Linux ~/.config/Claude/claude_desktop_config.json. Key names differ by client: Clients & CLI- Star count
- 2 ★ · NexTools-Solutions/nextool-mcp-glpi · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 2 ★ · 3 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
NexTools-Solutions/nextool-mcp-glpi;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# NexTool MCP for GLPI
Excerpted from the repository README (abridged)
Open-source Model Context Protocol server that connects AI assistants
(Claude, ChatGPT, Cursor, VS Code, Windsurf…) to your GLPI service desk: tickets, ITIL objects
(problems, changes), assets, knowledge base, users, rules and webhooks. It works with GLPI 10 and 11, and
supports both the REST API v1 and the GLPI 11 API v2 in one server.
> Not affiliated with Teclib'. GLPI is a registered trademark of Teclib'.
| Package | What it is |
| @nextoolsolutions/mcp-glpi | The MCP server (stdio and HTTP) and a library to embed it |
| @nextoolsolutions/mcp-glpi-core | Shared transport, write policy, idempotency and payload formatting |
Two ways to use it:
Hosted, early access: nothing to install. Sign in with a NexTool account, then add one URL as a connector in Claude or ChatGPT. Request access at https://nextoolsolutions.com/mcp. How it works, step by step: https://nextoolsolutions.com/en/mcp/como-funciona.
Local, open source (this repository): runs on your machine with your GLPI credentials. It is free and also works with GLPI instances that are only reachable on your intranet.
## 1. Prepare GLPI (both ways)
1. Enable the REST API: Setup → General → API. Turn on "Enable REST API" and "Enable login with external token".
2. API client (optional but recommended): in the same screen, add an API client and copy its App-Token. If you restrict it by IP, allow the address the MCP connects from.
3. User token: Administration → Users → (the user) → Remote access keys. Copy the API token.
Every action runs as this user and follows their GLPI profile and entities. Use a dedicated user with only the rights the assistant needs.
4. GLPI 11 API v2 (optional): create an OAuth client in GLPI 11 and note its client ID and secret. You also need a username and password, for the password grant.
## 2. Local install (open source)
Published on npm as @nextoolsolutions/mcp-glpi and listed in the
official MCP Registry as com.nextoolsolutions/glpi. Requires Node.js 18+.
bash
GLPI_URL=https://glpi.example.com GLPI_USER_TOKEN=xxx GLPI_APP_TOKEN=yyy npx -y @nextoolsolutions/mcp-glpi
From source instead: clone this repository, then npm ci && npm run build in mcp-glpi-core and in mcp-glpi, and run
node mcp-glpi/dist/index.js.
### Environment variables
| Variable | Meaning |
| GLPI_URL | GLPI base URL, e.g. https://glpi.example.com (REST API v1) |
| GLPI_USER_TOKEN | User API token (step 1.3) |
| GLPI_APP_TOKEN | App-Token of the API client (step 1.2), optional |
| GLPI_V2_URL, GLPI_V2_CLIENT_ID, GLPI_V2_CLIENT_SECRET, GLPI_V2_USERNAME, GLPI_V2_PASSWORD | GLPI 11 API v2 (OAuth). Optional; enables the glpi_v2_ tools |
| GLPI_TOOLSETS | Tool presets: core (recommended start), tickets, itil, assets, kb, documents, users, search, admin, v2. Combine with commas. Default: every tool |
| GLPI_READ_ONLY | true blocks every write before it reaches GLPI |
| GLPI_ALLOW_DELETE | true enables delete tools (default off); they then require a written reason |
All options are listed in mcp-glpi/README.md.
### Claude Code
bash
claude mcp add glpi \
-e GLPI_URL=https://glpi.example.com -e GLPI_USER_TOKEN=xxx -e GLPI_APP_TOKEN=yyy -e GLPI_TOOLSETS=core \
-- npx -y @nextoolsolutions/mcp-glpi
(Claude, ChatGPT, Cursor, VS Code, Windsurf…) to your GLPI service desk: tickets, ITIL objects
(problems, changes), assets, knowledge base, users, rules and webhooks. It works with GLPI 10 and 11, and
supports both the REST API v1 and the GLPI 11 API v2 in one server.
> Not affiliated with Teclib'. GLPI is a registered trademark of Teclib'.
| Package | What it is |
| @nextoolsolutions/mcp-glpi | The MCP server (stdio and HTTP) and a library to embed it |
| @nextoolsolutions/mcp-glpi-core | Shared transport, write policy, idempotency and payload formatting |
Two ways to use it:
Hosted, early access: nothing to install. Sign in with a NexTool account, then add one URL as a connector in Claude or ChatGPT. Request access at https://nextoolsolutions.com/mcp. How it works, step by step: https://nextoolsolutions.com/en/mcp/como-funciona.
Local, open source (this repository): runs on your machine with your GLPI credentials. It is free and also works with GLPI instances that are only reachable on your intranet.
## 1. Prepare GLPI (both ways)
1. Enable the REST API: Setup → General → API. Turn on "Enable REST API" and "Enable login with external token".
2. API client (optional but recommended): in the same screen, add an API client and copy its App-Token. If you restrict it by IP, allow the address the MCP connects from.
3. User token: Administration → Users → (the user) → Remote access keys. Copy the API token.
Every action runs as this user and follows their GLPI profile and entities. Use a dedicated user with only the rights the assistant needs.
4. GLPI 11 API v2 (optional): create an OAuth client in GLPI 11 and note its client ID and secret. You also need a username and password, for the password grant.
## 2. Local install (open source)
Published on npm as @nextoolsolutions/mcp-glpi and listed in the
official MCP Registry as com.nextoolsolutions/glpi. Requires Node.js 18+.
bash
GLPI_URL=https://glpi.example.com GLPI_USER_TOKEN=xxx GLPI_APP_TOKEN=yyy npx -y @nextoolsolutions/mcp-glpi
From source instead: clone this repository, then npm ci && npm run build in mcp-glpi-core and in mcp-glpi, and run
node mcp-glpi/dist/index.js.
### Environment variables
| Variable | Meaning |
| GLPI_URL | GLPI base URL, e.g. https://glpi.example.com (REST API v1) |
| GLPI_USER_TOKEN | User API token (step 1.3) |
| GLPI_APP_TOKEN | App-Token of the API client (step 1.2), optional |
| GLPI_V2_URL, GLPI_V2_CLIENT_ID, GLPI_V2_CLIENT_SECRET, GLPI_V2_USERNAME, GLPI_V2_PASSWORD | GLPI 11 API v2 (OAuth). Optional; enables the glpi_v2_ tools |
| GLPI_TOOLSETS | Tool presets: core (recommended start), tickets, itil, assets, kb, documents, users, search, admin, v2. Combine with commas. Default: every tool |
| GLPI_READ_ONLY | true blocks every write before it reaches GLPI |
| GLPI_ALLOW_DELETE | true enables delete tools (default off); they then require a written reason |
All options are listed in mcp-glpi/README.md.
### Claude Code
bash
claude mcp add glpi \
-e GLPI_URL=https://glpi.example.com -e GLPI_USER_TOKEN=xxx -e GLPI_APP_TOKEN=yyy -e GLPI_TOOLSETS=core \
-- npx -y @nextoolsolutions/mcp-glpi
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/nextools-solutions-nextool-mcp-glpi/)
- Source
- awesome · https://github.com/NexTools-Solutions/nextool-mcp-glpi
- Browse by field
- MCP servers
- Traction
- 2 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.