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

vibeMK

by chexmaversion 0.6.4i★ –iRuns on your computer
Registry nameio.github.chexma/vibemk

Install

Overview

Description from the maker (original English)

Query and configure CheckMK monitoring: hosts, services, rules, downtimes, metrics

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: CHECKMK_SERVER_URL, CHECKMK_SITE, CHECKMK_USERNAME, CHECKMK_PASSWORD

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: CHECKMK_SERVER_URL, CHECKMK_SITE, CHECKMK_USERNAME, CHECKMK_PASSWORD, CHECKMK_VERIFY_SSL, NEVER_ACTIVATE_CHANGES, VIBEMK_READ_ONLY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • PyPIPython’s uv installed (for the uvx command)

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": {
    "vibemk": {
      "command": "uvx",
      "args": [
        "vibemk"
      ],
      "env": {
        "CHECKMK_SERVER_URL": "your-value",
        "CHECKMK_SITE": "your-value",
        "CHECKMK_USERNAME": "your-value",
        "CHECKMK_PASSWORD": "your-value",
        "CHECKMK_VERIFY_SSL": "your-value",
        "NEVER_ACTIVATE_CHANGES": "your-value",
        "VIBEMK_READ_ONLY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add vibemk --env CHECKMK_SERVER_URL=your-value --env CHECKMK_SITE=your-value --env CHECKMK_USERNAME=your-value --env CHECKMK_PASSWORD=your-value --env CHECKMK_VERIFY_SSL=your-value --env NEVER_ACTIVATE_CHANGES=your-value --env VIBEMK_READ_ONLY=your-value -- uvx vibemk

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": {
    "vibemk": {
      "command": "uvx",
      "args": [
        "vibemk"
      ],
      "env": {
        "CHECKMK_SERVER_URL": "your-value",
        "CHECKMK_SITE": "your-value",
        "CHECKMK_USERNAME": "your-value",
        "CHECKMK_PASSWORD": "your-value",
        "CHECKMK_VERIFY_SSL": "your-value",
        "NEVER_ACTIVATE_CHANGES": "your-value",
        "VIBEMK_READ_ONLY": "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": {
    "vibemk": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "vibemk"
      ],
      "env": {
        "CHECKMK_SERVER_URL": "your-value",
        "CHECKMK_SITE": "your-value",
        "CHECKMK_USERNAME": "your-value",
        "CHECKMK_PASSWORD": "your-value",
        "CHECKMK_VERIFY_SSL": "your-value",
        "NEVER_ACTIVATE_CHANGES": "your-value",
        "VIBEMK_READ_ONLY": "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

  • CHECKMK_SERVER_URL required env
    CheckMK server URL, e.g. https://monitoring.example.com
  • CHECKMK_SITE required env
    CheckMK site name, e.g. cmk
  • CHECKMK_USERNAME required env
    CheckMK automation user
  • CHECKMK_PASSWORD secret required env
    Automation secret of that user
  • CHECKMK_VERIFY_SSL env
    Verify the server's TLS certificate
  • NEVER_ACTIVATE_CHANGES env
    Never activate configuration changes in CheckMK
  • VIBEMK_READ_ONLY env
    Offer only the tools that read and refuse every write

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 chexma, 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 1395 servers in this category
  • Published to the registry more recently than 60% of the other 1395 servers in this category
  • Basic checks equal to or better than 100% of the other 1395 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 vibeMK 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: CHECKMK_SERVER_URL, CHECKMK_SITE, CHECKMK_USERNAME, CHECKMK_PASSWORD

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.6.4) reached the registry 35 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) 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 4 days ago
Install

Desktop Commander

by wonderwhy-er

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

Runs on your computer★ 10,225MITUpdated 16 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.

vibeMK 🚀

CheckMK Monitoring via LLM - Professional MCP Server

🎯 Overview

vibeMK enables complete management of your CheckMK monitoring environment directly through LLM interfaces using natural language. This project is in the alpha stage and under development. I accept no liability for any damage resulting from the use of this software.

vibeMK - Current Features

Live Monitoring ✅
  • Host Status: Real-time host state (UP/DOWN/UNREACHABLE) with hard state detection
  • Service Status: Live service monitoring (OK/WARNING/CRITICAL/UNKNOWN)
  • Performance Metrics: Retrieve metrics data with automatic discovery
  • Current Problems: Auto-detect all active monitoring issues
Downtime Management ✅
  • Schedule Downtimes: Create host/service downtimes with flexible duration parsing ("2h", "1h30m")
  • List & Filter: View all downtimes or filter for active ones only
Problem Management ✅
  • Acknowledge Problems: Set acknowledgements for host/service issues (sticky/persistent options)
  • List Acknowledgements: View all current problem acknowledgements
  • Remove Acknowledgements: Delete by pattern or individual removal
Configuration Management ✅
  • Folders: Create/delete monitoring folder structures
  • Rules: Create rules for 2000+ CheckMK ruleset types with proper format handling
  • Time Periods: Create custom notification schedules (business hours, 24/7, etc.)
  • Host Groups: Organize hosts into logical groups
User & Security ✅
  • User Accounts: Create/manage user accounts with role assignment
  • Password Management: Set passwords with policy enforcement
  • Contact Groups: Manage notification groups
  • Host/Service Tags: Comprehensive tagging system

🚀 Quick Start

1. pipx install vibemk   (or: uv tool install vibemk, or pip install vibemk into a virtual environment)
  1. Edit the configuration file of your LLM Client, e.g. Claude Desktop - claude_desktop_config.json (See examples)
  2. Start your LLM Client
  3. CheckMK automation user setup (Administrator permissions or a customized role if changes are to be made, read-only if only analyses are to be performed.)
  4. voila - configure checkmk using natural language
**Complete Installation Guide**: See [INSTALL.md](https://github.com/chexma/vibeMK/blob/main/INSTALL.md) for detailed step-by-step instructions.

Upgrading from 0.3.x or older: git pull is not enough, see Upgrading. More Examples: See examples/llm_configs/ and INSTALL.md Visual Examples: See examples/Screenshots/ for example prompts and usage patterns

🔌 Running it

Locally (default). The LLM client starts vibeMK itself over stdio. Nothing to host, nothing to secure -- the client already owns the process.

Centrally. One instance can serve many clients over Streamable HTTP, so they need neither Python nor vibeMK installed:

export VIBEMK_HTTP_TOKEN="$(python -c 'import secrets; print(secrets.token_urlsafe(32))')"

vibemk --transport http --port 8765

Clients connect to http:// :8765/mcp and send Authorization: Bearer . The token is mandatory, and vibeMK binds to localhost unless told otherwise: the CheckMK account lives on the server, so whoever reaches the port inherits it. See INSTALL.md for what that means before you expose it.

💡 Practical Prompt Examples

# Add new server

"Create a new host 'web-server-05' in folder 'Servers' with IP 192.168.1.105 and discover all services"

Schedule maintenance

"Schedule a 2-hour downtime for the service Check_MK on 'cephnode01' starting at 22:00 tomorrow for 'Debian Updates'"

Downtimes

"show me all current scheduled downtimes."

Metric analysis

"Compare the “response_time” metric of the “HTTPS Webservice” service of the two hosts www.google.de and www.heise.de for the last ten minutes."

Ruleset analysis

"analyze and compare the rulesets "Filesystems (used space and growth)" and see, if there are duplicates or if rules can be combined."

**Advanced Usage**: See `examples/ExamplePrompts.md` for complex scenarios and tips

📚 Checkmk version compatibility

CheckMK VersionCompatibilityFeatures
2.5.x✅ FullAll features available, tested against 2.5.0p14 (Raw and Ultimate)
2.4.x✅ FullAll features available
2.3.x✅ FullAll features available
2.2.x and older🔴 Unsupported

Checkmk Edition Support

  • Raw Edition: Fully supported, including the BI and Event Console endpoints
  • Enterprise Edition: Adds the Agent Bakery and custom graphs
  • Cloud Edition: All Enterprise features

Edition availability follows the operationId of each endpoint in the Checkmk OpenAPI document: cmk.gui.cee.* is Enterprise-only, everything else is served by every edition including Raw.

Security considerations

  • To let a model look without touching, start vibeMK read-only: --read-only or VIBEMK_READ_ONLY=1. Only the tools that read are offered, and a call to any other is refused before it reaches CheckMK
  • Be aware of the potential security risks when you unleash AI on your checkmk
  • Use at your own risk
  • I accept no responsibility for actions performed by an AI

📄 License

This project is licensed under the GNU General Public License v3.0.


Happy Monitoring with CheckMK and LLMs! 🎉

Ask PopNx