Developer · Local MCP server
openITCOCKPIT
OpenITCOCKPIT monitoring: host and service state, history, downtimes, acknowledgements, patches.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.openITCOCKPIT/mcp-server- Version
- 0.5.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2026-09-17
- Updated
- 2026-09-17
- Publisher
- openITCOCKPIT (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/openITCOCKPIT) · how
- Website
- openitcockpit.io/
- Repository
- github.com/openITCOCKPIT/openITCOCKPIT-MCP-Server
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker) | docker.io/openitcockpit/mcp-server:0.5.0 | - | stdio |
How to connect openITCOCKPIT
openITCOCKPIT runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: docker.io/openitcockpit/mcp-server:0.5.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e OITC_APIKEY -e OITC_BASEURL -e OITC_TRANSPORT -e OITC_ENABLE_WRITE_TOOLS -e OITC_VERIFY_TLS docker.io/openitcockpit/mcp-server:0.5.0. It reads these environment variables: OITC_APIKEY (required, secret), OITC_BASEURL (required), OITC_TRANSPORT, OITC_ENABLE_WRITE_TOOLS and OITC_VERIFY_TLS; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"OITC_APIKEY",
"-e",
"OITC_BASEURL",
"-e",
"OITC_TRANSPORT",
"-e",
"OITC_ENABLE_WRITE_TOOLS",
"-e",
"OITC_VERIFY_TLS",
"docker.io/openitcockpit/mcp-server:0.5.0"
],
"env": {
"OITC_APIKEY": "<secret>",
"OITC_BASEURL": "<value>",
"OITC_TRANSPORT": "<value>",
"OITC_ENABLE_WRITE_TOOLS": "<value>",
"OITC_VERIFY_TLS": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Openflowkit MCPLocal-first OpenFlowKit diagramming tools for Claude, Cursor, Windsurf & other MCP clients. | Local · stdio |
| Opengate MCPCheck whether an AI answer is grounded in its context - deterministic, no LLM judge. | Local · stdio |
| OpenharnessLets AI coding agents discover and reference each other's recent sessions. | Local · stdio |
| OpenhelmAutonomous cloud agent tasks: real browser + your tools, structured evidence-backed results. | Remote · HTTPLive check: sign-in required |
| openLCA MCP ServerConnect AI assistants to openLCA. 35 tools for database search, model building, and LCIA. | Local · stdio |
| OpenMayhemUse OpenMayhem text, embedding and media models with explicit cost controls. | Remote & Local · HTTP, stdioLive check: sign-in required |
| OpenOCD DebuggerDebug microcontrollers via OpenOCD: flash, breakpoints, memory, registers and variables. | Local · stdio |
| OpenOSINTAI-powered OSINT agent & MCP server. 20 tools: email, breach, IP, WHOIS, DNS, Shodan, GitHub & more. | Local · stdio |