GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
openITCOCKPIT monitoring: host and service state, history, downtimes, acknowledgements, patches
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
OITC_APIKEY, OITC_BASEURL, OITC_TRANSPORT, OITC_ENABLE_WRITE_TOOLS, OITC_VERIFY_TLSValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"openitcockpit": {
"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": "your-value",
"OITC_BASEURL": "your-value",
"OITC_TRANSPORT": "your-value",
"OITC_ENABLE_WRITE_TOOLS": "your-value",
"OITC_VERIFY_TLS": "your-value"
}
}
}
}Run this in your terminal
claude mcp add openitcockpit --env OITC_APIKEY=your-value --env OITC_BASEURL=your-value --env OITC_TRANSPORT=your-value --env OITC_ENABLE_WRITE_TOOLS=your-value --env OITC_VERIFY_TLS=your-value -- 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.0Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"openitcockpit": {
"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": "your-value",
"OITC_BASEURL": "your-value",
"OITC_TRANSPORT": "your-value",
"OITC_ENABLE_WRITE_TOOLS": "your-value",
"OITC_VERIFY_TLS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"openitcockpit": {
"type": "stdio",
"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": "your-value",
"OITC_BASEURL": "your-value",
"OITC_TRANSPORT": "your-value",
"OITC_ENABLE_WRITE_TOOLS": "your-value",
"OITC_VERIFY_TLS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
OITC_TRANSPORT envOITC_ENABLE_WRITE_TOOLS envOITC_VERIFY_TLS envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account openITCOCKPIT, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: OITC_APIKEY, OITC_BASEURL
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.5.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
cp .env.example .env # fill in the two secrets, see Configuration
docker compose up --build
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.
| Ask | What answers it |
|---|---|
| "What is broken right now?" | get_problem_overview - causes separated from their consequences |
| "Why is db-01 critical?" | get_service_health, investigate_problem |
| "Is anyone on it already?" | the same tools: downtime and acknowledgement come with the state |
| "What happened during the night shift?" | get_shift_summary |
| "Why did I get no alert for web01?" | explain_notification |
| "Take web01 out until Monday" | schedule_downtime (write) |
| "Which templates could web-05 use?" | get_allowed_elements_for_container |
Every tool by name, with its parameters and what it costs in context: [docs/tools.md](docs/tools.md), generated from the code. What a result looks like and what happens when you write: [docs/using-the-tools.md](docs/using-the-tools.md).
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.
OITC_TOOLSETS=health # find things and see how they are doing
OITC_TOOLSETS=operations # acknowledge, maintenance windows, check now OITC_TOOLSETS=lifecycle # take things out of the monitoring, or delete them
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.
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.
oitc-mcp-eval --model your-model --samples 3 # against the configured instance
oitc-mcp-eval --compare # newest run of every model ./scripts/eval-throwaway.sh --model your-model # instance created and removed for you
docs/evals.md.
| Configuration | every setting, and which secret goes where |
| Connecting a client | HTTP and stdio, with working examples |
| Installation | Docker, from source, MCP Registry |
| Tools | every tool, generated from the code |
| Working with the tools | result shapes, container scope, read-modify-write |
| Toolsets | limiting an instance, writing your own set |
| Skills and prompts | the material served alongside the tools |
| Measuring a model | the eval, its cases, and reading the results |
| Security | what this server can reach, and what it refuses |
| Architecture | how the pieces fit together |
| Tool design | the rules a new tool follows |
| openITCOCKPIT API notes | the behaviour this server works around |
| Versioning | version numbers and compatibility |
| Development | checks, tests, running from a checkout |
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.
MIT.