openITCOCKPIT
io.github.openITCOCKPITPublished by GitHub account openITCOCKPITv0.5.0Updated Oct 24, 2026
openITCOCKPIT monitoring: host and service state, history, downtimes, acknowledgements, patches
Overview
An MCP server that lets an assistant read and, when enabled, change an openITCOCKPIT monitoring instance: host and service state, history, downtimes and patches
- What you can do
- Inspect monitoring state: problem overview, service health, problem investigation, shift summaries and notification explanations, with downtimes and acknowledgements shown alongside state. Look up configuration context: which templates and elements a container may use. Act on monitoring (write tools, off by default): schedule downtimes, acknowledge problems, run checks, manage maintenance windows. Manage lifecycle and configuration: take hosts or services out of monitoring, delete them, and edit monitoring configuration. Limit the exposed surface with toolsets such as health, operations, lifecycle, patch, reporting, catalog, onboarding, config and provisioning.
- When to use it
- Useful when an assistant should answer operational questions about an openITCOCKPIT 5.6+ instance, such as what is broken, why a service is critical, or why an alert did not fire. Add it when you also want the model to schedule downtimes or adjust monitoring configuration, starting read-only and enabling writes only after review.
- Requirements
- Runs as a local Docker container over stdio (the image defaults to HTTP, which also needs MCP_AUTH_TOKEN and a published port). Needs an openITCOCKPIT 5.6 or newer instance, the OITC_BASEURL setting without a path, and the OITC_APIKEY secret for a dedicated least-privilege user. Write tools require OITC_ENABLE_WRITE_TOOLS set to true.
Installation
In SourceWeft
- Open openITCOCKPIT in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
openITCOCKPIT MCP Server
An MCP server that puts an openITCOCKPIT monitoring instance in front of an LLM client: what is broken and why, what someone already handles, what changed - and, off by default, the tools that act on it.
[!CAUTION] Use at your own risk. This server lets a language model read and - with write tools enabled - change your monitoring configuration. A model can misunderstand a request or pick the wrong call. Review what it proposes before you approve it, and start with read-only access. The software is provided "as is", without warranty or liability of any kind; see the MIT License.
- Requires openITCOCKPIT 5.6 or newer (compatibility).
- 42 tools, 20 read-only and 22 that change something.
- Write tools are off by default and are not registered until you enable them.
- Names, never IDs. Tools take hostnames, template names and container paths; the server resolves them.
- Scope-checked writes. References are validated against the target container before anything is sent, which openITCOCKPIT's own API does not do.
Quickstart
Point your client at http://localhost:8000/mcp with the bearer token from your
.env. Compose reads that same file for the published port, so setting
OITC_PORT there moves both sides at once.
Three settings matter to start: MCP_AUTH_TOKEN (what clients present to this
server), OITC_BASEURL and OITC_APIKEY (what this server presents to
openITCOCKPIT). Everything else has a default -
all of it.
What you can ask it
Every tool by name, with its parameters and what it costs in context: docs/tools.md, generated from the code. What a result looks like and what happens when you write: docs/using-the-tools.md.
Limiting an instance
Running a monitoring instance is not one job, so a surface small enough to be easy would be too small to be useful. Instead the server keeps every tool the work needs and a toolset hands one agent its share: around ten tools, complete for that job and nothing beyond it. A tool that was never registered cannot be called at all.
The shipped sets are health, operations, lifecycle, patch, reporting,
catalog, onboarding, config and provisioning. Sets are defined in a file
you can replace: docs/toolsets.md.
Measuring a model
oitc-mcp-eval asks operator questions against your instance and checks whether
a model answers them from the tools instead of inventing. It keeps every run in
SQLite, so models and changes stay comparable.
Documentation
Security in one paragraph
The server holds one openITCOCKPIT credential and never sends it to a client. Clients authenticate with their own token; in delegated mode each request carries a short-lived user token instead, and the server acts as that user with their permissions. Write tools stay unregistered until you enable them. The details, including what to give the openITCOCKPIT user: docs/security.md.
License
MIT.
Source: README.md at commit 49e0515
Tools
0Version history
2- v0.5.0LatestSep 17, 2026
- v0.4.0Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts