Linuxfabrik MCP Server for Icinga
Provides tools for triaging, investigating, and operating Icinga installations through the Icinga 2 Core, Icinga Web, and Icinga Director REST APIs, including managing host and service objects, on-demand checks, acknowledgements, downtimes, and object browsing.
Enables access to historical performance data from a time series database for trending analysis, flapping detection, and root-cause investigation within Icinga monitoring environments.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Linuxfabrik MCP Server for Icingashow me all critical alerts from the last hour"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Server for Icinga
mcp-server-icinga is a Model Context Protocol (MCP) server that lets AI clients such as Claude work with Icinga installations through natural language. It targets Linux System Engineers who run Icinga in production and want a chat-driven interface for daily triage, incident investigation and routine operations on top of the existing Icinga REST APIs.
This project was developed with the assistance of Claude Code by Anthropic.
Scope
The server bridges three Icinga surfaces and the Linuxfabrik monitoring stack:
Icinga 2 Core REST API (port 5665): live host and service objects, on-demand checks, acknowledgements, downtimes.
Icinga Web 2 / Icinga DB Web module: richer state projections, history, comments, notifications, with the limitations of the Icinga Web surface.
Icinga Director API: object browsing, service template introspection, command catalog.
Linuxfabrik monitoring-plugins catalog: implementation, inputs, outputs, states and perfdata of every check plugin, so the server can explain why a service is alerting, not just that it is.
Time series database (default: InfluxDB, modular): historical perfdata for trending, flapping analysis and root-cause investigation.
Each backend lives in its own module so that operators can wire up only what they actually run. The server transparently flags information that the underlying API does not expose, instead of guessing.
Status
Early development. Architecture, configuration and tool surface are unstable and will change.
Requirements
Python 3.14 or newer.
Reachable Icinga installation (one or more of: Icinga 2 Core API, Icinga Web 2 with the Icinga DB Web module, Icinga Director).
Optional: a time series database backend for historical perfdata. Default integration is InfluxDB; the TSDB layer is modular so other backends can be plugged in.
Installation
Installation instructions will be documented once the first release is cut.
Configuration
Configuration documentation will follow as soon as the configuration surface stabilises.
Related Projects
Linuxfabrik monitoring-plugins: the check plugin catalog this server understands.
Linuxfabrik lib: shared Python helpers.
Icinga/icinga-mcp: upstream proof-of-concept MCP server by the Icinga team. Different scope, different architecture.
License
Released into the public domain under the Unlicense.
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Linuxfabrik/mcp-server-icinga'
If you have feedback or need assistance with the MCP directory API, please join our Discord server