Werk #22263: New: MCP server lets AI agents query Checkmk monitoring data (experimental feature)
| Component | REST API | ||||
| Title | New: MCP server lets AI agents query Checkmk monitoring data (experimental feature) | ||||
| Date | Aug 26, 2026 | ||||
| Level | Prominent Change | ||||
| Class | New Feature | ||||
| Compatibility | Compatible - no manual interaction needed | ||||
| Checkmk versions & editions |
|
This is an experimental feature: its interface, tools, and behavior may still change incompatibly in a future release.
Checkmk sites can now run a built-in MCP (Model Context Protocol) server, so MCP-compatible AI clients and agents (for example Claude Code or Codex) can query the site's monitoring data directly.
The server runs as its own long-running service, alongside the agent-receiver, and is reachable at https://<host>/<site>/check_mk/mcp.
It's disabled by default.
Enable it under Global settings > AI features > Enable MCP server.
The MCP server is the first Checkmk feature to register OAuth discovery paths (RFC 8414/9728 well-known routes) at the system Apache level, outside the site's own URL prefix. After enabling it, run the following once as root to apply that part of the configuration:
omd update-apache-config SITE
The agent's actions are bound to the permissions of the authenticated user (see Werk #22264).
In this initial release, an agent can:
- look up the local Checkmk version
- query hosts, services, downtimes, comments, and Event Console events
- retrieve service availability and metric history
- get a monitoring overview, and pending or recent configuration changes
- read the current Setup (WATO) configuration
- discover which tools and data are available
The MCP server is a read-only interface, so configuration changes (such as activation) cannot be triggered via MCP.
A separate, disabled-by-default setting (Send MCP usage data to Checkmk) lets a site send anonymized usage telemetry: which tools were called, response times and sizes, error codes, the AI client used, and a random session ID. This helps us improve the feature. It never collects request arguments or result content (monitoring data).
For setup and troubleshooting (including running the MCP server behind a reverse proxy), see the knowledge article Using the Checkmk MCP Server.