How do I install the Kuma Operations skill?

Run npx skillmds add mvanhorn-printing-press-libra/kuma-operations in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Kuma Operations skill do?

Use when investigating or safely modifying Uptime Kuma v2 monitors. It is listed under Coding & Dev Tools on SkillMD.

Is Kuma Operations safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kuma Operations?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Kuma Operations free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Kuma Operations?

mvanhorn (@mvanhorn-printing-press-libra) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kuma Operations by mvanhorn-printing-press-libra

Name: Kuma Operations
Rating: 4.2 (5 reviews)
Author: mvanhorn

File contents

Uptime Kuma operations

Prerequisites: Install the CLI

This skill drives the kuma-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:
```
npx -y @mvanhorn/printing-press-library install kuma --cli-only
```
Verify: kuma-pp-cli --version
Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill.

If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer). This installs into $GOPATH/bin (default $HOME/go/bin), so add that directory to $PATH instead:

go install github.com/mvanhorn/printing-press-library/library/monitoring/kuma/cmd/kuma-pp-cli@latest

If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.

Native HTTP MCP service

This skill's kuma-pp-cli is the generated Go Socket.IO operator CLI, not the native kumactl MCP server. For MCP clients, install and deploy the separately published native service, then expose its Streamable HTTP endpoint with:

kumactl-mcp --transport streamable-http --host 127.0.0.1 --port 40108 --path /mcp

The native service and this CLI use the preserved UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME, and UPTIME_KUMA_PASSWORD environment variables. Do not substitute kumactl-mcp for the commands below; this package has no kumactl dependency or embedded MCP transport.

Use kuma-pp-cli for authenticated Kuma v2 inspection. Credentials come from UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME, and UPTIME_KUMA_PASSWORD. UPTIME_KUMA_URL must be the server origin (for example https://kuma.example.com), not a dashboard page URL.

Discovering the command surface

Run kuma-pp-cli agent-context --pretty to get machine-readable JSON describing every command, flag, and auth variable. Prefer this over parsing --help. Commands annotated mcp:read-only are safe to run unattended; set-retries is annotated mcp:destructive.

Investigation

Run kuma-pp-cli health.
Run kuma-pp-cli monitors --json and identify the exact monitor ID.
Run kuma-pp-cli incident-context --monitor <id> --json.
Use kuma-pp-cli heartbeats --monitor-id <id> --hours 3 --json for the timeline.

Mutations

set-retries is dry-run by default. Review the proposed complete monitor update, then repeat the exact command with --yes only when explicitly authorized. Do not invent monitor IDs or alter notification settings as part of an unrelated retry change.

---name: kuma-operationsdescription: Use when investigating or safely modifying Uptime Kuma v2 monitors.--- # Uptime Kuma operations ## Prerequisites: Install the CLI This skill drives the `kuma-pp-cli` binary. **You must verify the CLI is installed before invoking any command from this skill.** If it is missing, install it first: 1. Install via the Printing Press installer. It defaults binaries to `$HOME/.local/bin` on macOS/Linux and `%LOCALAPPDATA%\Programs\PrintingPress\bin` on Windows: ```bash npx -y @mvanhorn/printing-press-library install kuma --cli-only ``` 2. Verify: `kuma-pp-cli --version` 3. Ensure the reported install directory is on `$PATH` for the agent/runtime that will invoke this skill. If the `npx` install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer). This installs into `$GOPATH/bin` (default `$HOME/go/bin`), so add that directory to `$PATH` instead: ```bash go install github.com/mvanhorn/printing-press-library/library/monitoring/kuma/cmd/kuma-pp-cli@latest ``` If `--version` reports "command not found" after install, the runtime cannot see the binary directory on `$PATH`. Do not proceed with skill commands until verification succeeds. ## Native HTTP MCP service This skill's `kuma-pp-cli` is the generated Go Socket.IO operator CLI, not the native `kumactl` MCP server. For MCP clients, install and deploy the separately published native service, then expose its Streamable HTTP endpoint with: ```bash kumactl-mcp --transport streamable-http --host 127.0.0.1 --port 40108 --path /mcp ``` The native service and this CLI use the preserved `UPTIME_KUMA_URL`, `UPTIME_KUMA_USERNAME`, and `UPTIME_KUMA_PASSWORD` environment variables. Do not substitute `kumactl-mcp` for the commands below; this package has no `kumactl` dependency or embedded MCP transport. Use `kuma-pp-cli` for authenticated Kuma v2 inspection. Credentials come from `UPTIME_KUMA_URL`, `UPTIME_KUMA_USERNAME`, and `UPTIME_KUMA_PASSWORD`. `UPTIME_KUMA_URL` must be the server origin (for example `https://kuma.example.com`), not a dashboard page URL. ## Discovering the command surface Run `kuma-pp-cli agent-context --pretty` to get machine-readable JSON describing every command, flag, and auth variable. Prefer this over parsing `--help`. Commands annotated `mcp:read-only` are safe to run unattended; `set-retries` is annotated `mcp:destructive`. ## Investigation 1. Run `kuma-pp-cli health`. 2. Run `kuma-pp-cli monitors --json` and identify the exact monitor ID. 3. Run `kuma-pp-cli incident-context --monitor <id> --json`. 4. Use `kuma-pp-cli heartbeats --monitor-id <id> --hours 3 --json` for the timeline. ## Mutations `set-retries` is dry-run by default. Review the proposed complete monitor update, then repeat the exact command with `--yes` only when explicitly authorized. Do not invent monitor IDs or alter notification settings as part of an unrelated retry change.

Frequently asked questions