原型 · 预览版：收录官方注册中心里的全部服务器，每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚
新手模式 开
配色跟随系统浅色深色
语言ไทยEnglish中文日本語한국어EspañolDeutsch
☰ 菜单设置
新手模式 开
配色跟随系统浅色深色
语言ไทยEnglish中文日本語한국어EspañolDeutsch

openITCOCKPIT

作者：openITCOCKPIT版本 0.5.0i★ –i在你的电脑上运行
注册名称io.github.openITCOCKPIT/mcp-server

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 开发者工具
  • 你需要填写：OITC_APIKEY, OITC_BASEURL

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

  • 基础检查：1 项中通过 1 项
  • 在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
  • 需要你自己填写： OITC_APIKEY, OITC_BASEURL, OITC_TRANSPORT, OITC_ENABLE_WRITE_TOOLS, OITC_VERIFY_TLS

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

你用的是哪个应用？

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 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"
      }
    }
  }
}

在终端中运行这条命令

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

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.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"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "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"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

  • OITC_APIKEY 机密 必填 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 必填 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.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 openITCOCKPIT 验证，该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行，没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行，改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“开发者工具”中的其他服务器比较i

  • 星标数多于此分类中其他 1393 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 1393 个服务器的 54% 更新
  • 基础检查结果等于或优于此分类中其他 1393 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

openITCOCKPIT 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：OITC_APIKEY, OITC_BASEURL

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.5.0）于2个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。

有什么可以替代它？

同一分类中有：GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

作者：github

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

电脑或云端★ 34,245MIT3天前更新
安装

Desktop Commander

作者：wonderwhy-er

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

在你的电脑上运行★ 10,225MIT15天前更新
安装

Cloudflare MCP

作者：cloudflare

Cloudflare MCP servers

在云端运行★ 4,446Apache-2.014个月前更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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.

问 PopNx