GLPI MCP

GLPI MCP Server

Let AI agents work with GLPI tickets, assets and the knowledge base through the Model Context Protocol

Installation · Tools · Configuration · Security

GLPI MCP Server is a Python-based Model Context Protocol (MCP) server for the GLPI IT service management platform. It talks to GLPI's High-Level API (/api.php, OAuth2) and gives AI assistants and automation tools access to tickets, changes and problems (with their timeline and team), assets, users, groups, entities, the knowledge base and documents, plus generic tools that reach every endpoint GLPI exposes. It supports read and write operations, with read-only and dry-run modes, per-user GLPI access and OAuth login for remote MCP clients.

✨ Features

Core Features

• Search tickets, changes and problems by status, type, priority, category, entity, dates, text or any RSQL filter
• Read the full timeline of an item: followups, tasks, solutions, approvals and documents
• Search and read assets of every type (including custom assets), with financial information
• Find users, groups, entities and profiles
• Search and read knowledge base articles; download documents
• Discover every endpoint and schema from GLPI's own OpenAPI document, so nothing is hard-coded to one GLPI version

Management Operations

• Create, update and delete tickets, changes and problems (if enabled)
• Add followups, tasks, solutions and approval requests
• Assign technicians and groups, add requesters and observers
• Create, update and delete assets and knowledge base articles
• Create, update and delete items at any endpoint with the generic tools

Advanced Capabilities

• Supports GLPI 11.0.6+ (API 2.3) and GLPI 12 (API 3.0, or 2.3 if pinned); the version is detected and pinned in every request
• OAuth password grant with token caching and renewal
• Per-user access: token passthrough, or sign-in with GLPI accounts (OAuth login) for remote MCP clients
• OIDC login through an external identity provider, or a static bearer token
• Read-only mode, dry-run mode and tag-based tool filtering
• HTML rich text converted to plain text to save tokens
• Rate limiting, response size limit and optional tool-search transform
• Multiple transport options (STDIO, SSE, HTTP) and optional Sentry integration

🚀 Installation

Prerequisites

• Python 3.11 to 3.15
• GLPI 11.0.6 or newer (including 12.x). GLPI 10 and GLPI 11.0.0-11.0.5 are not supported: they lack High-Level API 2.3
• The API enabled in Setup > General > API ("Enable API")
• An OAuth client (see GLPI setup)

Quick Install from PyPI

The easiest way to get started is to install from PyPI:

# Using UV (recommended)

uvx glpi-mcp-server

Or using pip

pip install glpi-mcp-server

Remember to configure the environment variables for your GLPI instance before running the server:

# Create environment configuration

export GLPI_URL=https://glpi.example.com export GLPI_CLIENT_ID=your-client-id export GLPI_CLIENT_SECRET=your-client-secret export GLPI_USERNAME=glpi-mcp export GLPI_PASSWORD=change-me

Install from Source

1. Clone the repository:

git clone https://github.com/mhajder/glpi-mcp.git

cd glpi-mcp

1. Install dependencies:

# Using UV (recommended)

uv sync

Or using pip

pip install -e .

1. Configure environment variables:

cp .env.example .env

Edit .env with your GLPI URL and OAuth credentials

1. Run the server:

# Using UV (recommended)

uv run glpi-mcp

Or using the installed command directly

glpi-mcp

Using Docker

A Docker image is available on GitHub Packages for easy deployment. It runs the HTTP Streamable transport on port 8000 (/mcp).

docker pull ghcr.io/mhajder/glpi-mcp:latest

When GLPI login or OIDC is enabled, mount a volume on /data so OAuth client registrations survive container recreation.

Open WebUI

Open WebUI 0.6.31 and later connect to the image directly. In Open WebUI, go to Admin Settings > Integrations > External Tool Servers, add a connection of type MCP (Streamable HTTP) with the URL http:// :8000/mcp, and set Bearer authentication to your MCP_HTTP_BEARER_TOKEN.

With GLPI login or OIDC enabled, use the public URL + /mcp and choose OAuth 2.1 authentication instead; Open WebUI registers itself as a client, so if you restrict redirect URIs, include your Open WebUI URL.

Development Setup

For development with additional tools:

# Clone and install with development dependencies

git clone https://github.com/mhajder/glpi-mcp.git cd glpi-mcp uv sync --group dev

Run tests

uv run pytest

Run with coverage

uv run pytest --cov=src/

Run linting and formatting

uv run ruff check . uv run ruff format .

Run type checking

uv run ty check .

Setup prek hooks

uv run prek install

🔧 Configuration

GLPI setup

1. Enable the API: Setup > General > API > "Enable API".
2. Create an OAuth client: Setup > OAuth clients > Add.

• Grants: Password (for GLPI_USERNAME/GLPI_PASSWORD). Add Authorization Code for GLPI login.
• Scopes: api and user. Add graphql for glpi_graphql_query.
• For GLPI login, set the redirect URI to GLPI_OAUTH_BASE_URL + GLPI_OAUTH_REDIRECT_PATH.
• Copy the generated client ID and secret.

1. Create a GLPI user for the server (for example glpi-mcp) with a profile that has just the rights the tools need. Every tool call acts as this user, unless per-user access is enabled.

Environment Variables

# GLPI Connection Details

GLPI root URL, without /api.php

GLPI_URL=https://glpi.example.com

OAuth client from Setup > OAuth clients

GLPI_CLIENT_ID=your-client-id GLPI_CLIENT_SECRET=your-client-secret

GLPI account the tools act as (OAuth password grant)

GLPI_USERNAME=glpi-mcp GLPI_PASSWORD=change-me

OAuth scopes, space- or comma-separated (default: api user)

GLPI_SCOPES=api user

High-Level API version: auto (default), 2.3 or 3.0

GLPI_API_VERSION=auto

Optional: entity and profile to work in

GLPI_ENTITY=0

GLPI_ENTITY_RECURSIVE=true

GLPI_PROFILE=4

SSL Configuration

GLPI_VERIFY_SSL=true GLPI_TIMEOUT=30

Per-user GLPI access (HTTP transports only; pick at most one)

GLPI_TOKEN_PASSTHROUGH=false

GLPI_OAUTH_LOGIN=false

GLPI_OAUTH_BASE_URL=https://glpi-mcp.example.com

GLPI_OAUTH_REDIRECT_PATH=/auth/callback

GLPI_OAUTH_ALLOWED_REDIRECT_URIS=

Read-Only Mode

READ_ONLY_MODE=false

Dry-Run Mode

DRY_RUN_MODE=false

Disabled Tags

Example: DISABLED_TAGS=assets,knowledgebase,graphql

DISABLED_TAGS=

Response Size Limit (bytes; empty = unlimited)

RESPONSE_MAX_SIZE=500000

Logging Configuration

LOG_LEVEL=INFO

Rate Limiting

RATE_LIMIT_ENABLED=false RATE_LIMIT_MAX_REQUESTS=60 RATE_LIMIT_WINDOW_MINUTES=1

Tool Search Transform (Optional)

TOOL_SEARCH_ENABLED=false TOOL_SEARCH_STRATEGY=bm25 TOOL_SEARCH_MAX_RESULTS=5

Sentry Error Tracking (Optional)

SENTRY_DSN=https://your-key@o12345.ingest.us.sentry.io/6789

MCP Transport Configuration

'stdio' (default), 'sse' or 'http' ('streamable-http' is an alias for 'http')

MCP_TRANSPORT=stdio

MCP_HTTP_HOST=127.0.0.1

MCP_HTTP_PORT=8000

MCP_HTTP_BEARER_TOKEN=

OIDC / OAuth Authentication (optional, for remote hosting)

OIDC_CONFIG_URL=https://id.example.com/.well-known/openid-configuration

OIDC_CLIENT_ID=

OIDC_CLIENT_SECRET=

OIDC_BASE_URL=https://glpi-mcp.example.com

See .env.example for every setting with comments.

API versions

GLPI lists the High-Level API versions it offers at GET /api.php/. On first use the server reads that list and pins one version in every request path (/api.php/v2.3/... or /api.php/v3.0/...), because GLPI silently routes an unknown version to its newest one.

Set GLPI_API_VERSION=2.3 to keep GLPI 12 on the 2.3 schemas (for example while migrating other integrations). The tools that depend on a schema difference handle both: knowledge base articles are filed under categories on 2.3 and under parent articles (parents) on 3.0.

Entity and profile

GLPI scopes every API session to an active profile and entities. By default these are the user's defaults. GLPI_ENTITY, GLPI_ENTITY_RECURSIVE and GLPI_PROFILE send the GLPI-Entity, GLPI-Entity-Recursive and GLPI-Profile headers with every request to change them. glpi_whoami shows the active ones and glpi_get_entity_tree lists the entities available.

🧰 Available Tools

Server & Session

• glpi_server_info: API versions GLPI offers, the pinned version, auth mode and safety modes
• glpi_whoami: The GLPI user the tools act as, with the active profile and entities
• glpi_get_entity_tree: Entities the current user can work in

Tickets, Changes & Problems

All take itil_type: Ticket (default), Change or Problem.

• glpi_search_itil: Search by status, type, priority, category, entity, dates, text or filter
• glpi_get_itil: One item with its description and team
• glpi_get_itil_timeline: Followups, tasks, solutions, approvals and documents
• glpi_create_itil / glpi_update_itil / glpi_delete_itil: Create, update, delete
• glpi_add_itil_followup: Add a followup (public or private)
• glpi_add_itil_task: Add a task with state, time spent, technician and planning
• glpi_add_itil_solution: Add a solution
• glpi_request_itil_validation: Ask a user or group to approve a ticket or change
• glpi_list_itil_team: Requesters, assignees and observers
• glpi_add_itil_team_member / glpi_remove_itil_team_member: Assign or remove users, groups and suppliers

Assets

• glpi_list_asset_types: Asset types of this GLPI, including custom assets
• glpi_search_assets: Search one asset type, or all at once, by name, serial, inventory number or filter
• glpi_get_asset: One asset, optionally with financial information
• glpi_create_asset / glpi_update_asset / glpi_delete_asset: Create, update, delete

Users, Groups, Entities & Profiles

• glpi_search_users / glpi_get_user: Find users; get one by ID or login
• glpi_search_groups / glpi_get_group: Find groups; get one by ID
• glpi_search_entities / glpi_get_entity: Find entities; get one by ID
• glpi_list_profiles: Profiles (