Uptime Kuma is a self-hosted monitoring tool that provides uptime monitoring for websites and services. It offers a user-friendly interface to track the availability and performance of various endpoints.
MCP server exposing Dashbrr's REST API as tools, so an LLM can read and manage a dashbrr instance: configured services, per-service health, and summary panels for many apps. Write tools cover settings management, download-queue deletes, Overseerr approvals, UI preferences, and the Plex auth PIN flow.
34
MIT
Why this server?
Enables management of Uptime Kuma instances, providing tools to list monitors, create or end maintenance windows, and silence alerts during scheduled downtime.
Enables unified management of maintenance windows and incidents across Atlassian Statuspage and Uptime Kuma. It allows AI assistants to schedule maintenance, update service statuses, and list monitors through a single MCP-compatible interface.
9
MIT
Why this server?
Provides tools for monitoring and managing Uptime Kuma monitors, including fetching summaries, heartbeats, and uptime, as well as creating, pausing, and deleting monitors, managing notifications, tags, maintenance windows, and status pages.
MCP server for Uptime Kuma that enables monitoring and management of uptime monitors, heartbeats, notifications, tags, and maintenance windows via natural language.
35
844 npm
54
MIT
Why this server?
Provides tools for interacting with an Uptime Kuma instance, enabling management of monitors (create, edit, delete, pause, resume), retrieval of heartbeats, uptime status, Prometheus metrics, notifications, and status pages.
Enables managing Uptime Kuma monitoring through natural language, including creating, editing, pausing, and deleting monitors, plus retrieving heartbeats, status, metrics, notifications, and status pages.
12
MIT
Why this server?
Allows deploying Uptime Kuma from the App Store to monitor website and service uptime.
Enables unified administrative control over Cloudflare, Porkbun, Docker, Proxmox VE, Nginx Proxy Manager/NPMPlus, Uptime Kuma, Authentik, and Coolify. Exposes service discovery and action execution through three MCP tools with roughly 150 cataloged operations for managing DNS, containers, VMs, proxies, monitors, users, and related infrastructure.
3
-
Why this server?
Provides tools for monitoring service availability, including retrieving status pages, monitoring heartbeat data, and viewing summaries of all configured monitors.
Provides unified access to multiple homelab services including Nginx Proxy Manager, Pi-hole, Uptime Kuma, Portainer, and UPS NUT for monitoring, management, and automation through a single modular interface.
MIT
Why this server?
Reads public status-page JSON, the newest heartbeat, and safe incident summaries from Uptime Kuma without requiring admin credentials, reporting not_published when no page exists.
Enables incident responders to query and correlate observability and DevOps evidence across Grafana, Prometheus, Loki, Uptime Kuma, CloudWatch, IAM, and PostHog from a local MCP client, with bounded reads and redacted audit records.
MIT
Why this server?
Provides tools to manage Uptime Kuma monitors and groups, including creating, updating, pausing, resuming, and deleting monitors, as well as retrieving heartbeats, charts, important events, stats, and managing tags and notifications.
Enables LLM clients to manage Uptime Kuma HTTP(S) monitors, groups, tags, and notifications, and to retrieve heartbeats, stats, and incident history through MCP tools.
