Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

openITCOCKPIT

by openITCOCKPITversion 0.5.0i★ –iRuns on your computer
Registry nameio.github.openITCOCKPIT/mcp-server

Install

Overview

Description from the maker (original English)

openITCOCKPIT monitoring: host and service state, history, downtimes, acknowledgements, patches

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Developer tools
  • You need to fill in: OITC_APIKEY, OITC_BASEURL

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: OITC_APIKEY, OITC_BASEURL, OITC_TRANSPORT, OITC_ENABLE_WRITE_TOOLS, OITC_VERIFY_TLS

Values 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.0

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

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.

Open in VS Code

Or copy the settings yourself

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.

Values you fill in

  • OITC_APIKEY secret required env
    API key of a dedicated, least-privilege openITCOCKPIT user. This server presents it to openITCOCKPIT; it is never handed to a client.
  • OITC_BASEURL required env
    Base URL of the openITCOCKPIT instance, e.g. https://openitcockpit.example.org - without a path.
  • OITC_TRANSPORT env
    Transport mode. The image defaults to 'http', which additionally requires MCP_AUTH_TOKEN and a published port; a client that runs this container itself wants 'stdio'.
  • OITC_ENABLE_WRITE_TOOLS env
    Register the 15 tools that change the monitoring configuration. Off by default: they are not even registered unless this is 'true'.
  • OITC_VERIFY_TLS env
    Verify the openITCOCKPIT TLS certificate. On by default; for a self-signed instance set OITC_CA_BUNDLE rather than turning this off.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account openITCOCKPIT, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

  • More stars than 0% of the other 1393 servers in this category
  • Published to the registry more recently than 54% of the other 1393 servers in this category
  • Basic checks equal to or better than 100% of the other 1393 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is openITCOCKPIT safe?

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.

What keys or codes does it need?

You need to fill in: OITC_APIKEY, OITC_BASEURL

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.5.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

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

by 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.

Computer or cloud★ 34,245MITUpdated 3 days ago
Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 15 days ago
Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago
Install

README from the maker

Open the README

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.

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

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.

What you can ask it

AskWhat 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).

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.

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.

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.

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.

Documentation

Configurationevery setting, and which secret goes where
Connecting a clientHTTP and stdio, with working examples
InstallationDocker, from source, MCP Registry
Toolsevery tool, generated from the code
Working with the toolsresult shapes, container scope, read-modify-write
Toolsetslimiting an instance, writing your own set
Skills and promptsthe material served alongside the tools
Measuring a modelthe eval, its cases, and reading the results
Securitywhat this server can reach, and what it refuses
Architecturehow the pieces fit together
Tool designthe rules a new tool follows
openITCOCKPIT API notesthe behaviour this server works around
Versioningversion numbers and compatibility
Developmentchecks, tests, running from a checkout

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.

Ask PopNx