uptime-kuma

Manage Uptime Kuma monitors and retrieve heartbeat history via CLI.

7|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/LvcidPsyche/polymarket-arbitrage-bot --skill uptime-kuma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uptime-kuma
Source: https://github.com/LvcidPsyche/polymarket-arbitrage-bot/tree/main/skills/uptime-kuma
Command: npx skills add https://github.com/LvcidPsyche/polymarket-arbitrage-bot --skill uptime-kuma

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires uptime-kuma-api, and includes scripts (resource) components.

What problem does it solve?

Interact with Uptime Kuma monitoring server to check monitor status, add and remove monitors, pause/resume checks, and view heartbeat history.

Core Features & Use Cases

  • CLI wrapper around the Socket.IO API to manage monitors: list, get, add, pause, resume, delete, and view heartbeats and notifications.

Quick Start

Install uptime-kuma-api, configure UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME, and UPTIME_KUMA_PASSWORD, then run python scripts/kuma.py with the desired command.

Frequently Asked Questions about uptime-kuma

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Uptime Kuma monitors from the command line?

You can manage Uptime Kuma monitors by running a Python CLI script that wraps the Socket.IO API to create, view, pause, resume, and delete monitors. It requires the uptime-kuma-api Python package and a running Uptime Kuma instance.

Can I automate Uptime Kuma monitor maintenance across multiple instances?

Yes, you can automate routine Uptime Kuma monitor maintenance across multiple instances by configuring environment variables for authentication and executing CLI commands to audit configurations and check statuses programmatically.

How do I retrieve heartbeat history for a monitor in Uptime Kuma?

To retrieve heartbeat history, run the provided Python CLI script with the command to view heartbeats. It communicates with the Uptime Kuma server via the Socket.IO API to fetch and display the historical monitor data.

Do I need the uptime-kuma-api package to control monitors via CLI?

Yes, the uptime-kuma-api Python package is required. You also need authenticated access to the Uptime Kuma server configured via UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME, and UPTIME_KUMA_PASSWORD environment variables.

What is the best way to audit Uptime Kuma monitor configurations?

The best way to audit Uptime Kuma monitor configurations is using a CLI wrapper to list and get monitor details. This allows teams to quickly check monitor statuses and audit configurations across operational environments.

Why does my CLI wrapper fail to connect to the Uptime Kuma server?

Your CLI wrapper fails to connect if the Uptime Kuma instance is not running or if environment variables are missing. You must configure UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME, and UPTIME_KUMA_PASSWORD for authenticated Socket.IO API access.