Mcp Uptime Kuma
Connect your agent to a self-hosted Uptime Kuma v2 instance so it can inspect monitors and status without opening the dashboard.
Overview
io.github.DavidFuchs/mcp-uptime-kuma is a MCP server for the Operate phase that connects agents to a Uptime Kuma v2 instance for monitor and status operations.
What is this MCP server?
- MCP bridge for Uptime Kuma version 2
- npm package @davidfuchs/mcp-uptime-kuma (v0.7.0) over stdio
- Configurable URL plus username/password or JWT token auth
- Optional 2FA token environment variable when enabled on the account
- Lets agents query monitor state instead of manual dashboard checks
- Server version 0.7.0 in published MCP schema
- Explicitly described as MCP for Uptime Kuma version 2
- Five documented environment variables including required UPTIME_KUMA_URL
Community signal: 25 GitHub stars.
What problem does it solve?
You run Uptime Kuma but still manually copy monitor status into chat when an agent could help triage outages.
Who is it for?
Indie operators who self-host Uptime Kuma v2 and want Claude Code or Cursor to read or manage monitors during incidents.
Skip if: Builders without an Uptime Kuma instance, teams needing full APM traces, or anyone on Uptime Kuma v1-only setups incompatible with this v2-focused server.
What do I get? / Deliverables
After setup with your Kuma URL and credentials, your agent can interact with Uptime Kuma v2 through MCP instead of ad-hoc API curls.
- Agent-driven access to Uptime Kuma v2 via MCP
- Configurable auth path (password, JWT, or optional 2FA token)
- Less dashboard context-switching during outages
Recommended MCP Servers
Journey fit
Uptime and service health belong in Operate once you are running production URLs, cron checks, and incident response—not in early idea validation. The server targets Uptime Kuma monitoring APIs and credentials, which is canonical monitoring rather than deploy or error-log triage alone.
How it compares
Uptime Kuma-specific MCP integration, not a generic Prometheus exporter or a deploy skill.
Common Questions / FAQ
Who is io.github.DavidFuchs/mcp-uptime-kuma for?
It is for solo builders and small teams running Uptime Kuma v2 who want agent access to monitor data via MCP.
When should I use io.github.DavidFuchs/mcp-uptime-kuma?
Use it in Operate/monitoring when services are live and you want agents to help check status, explain failures, or assist with Kuma workflows.
How do I add io.github.DavidFuchs/mcp-uptime-kuma to my agent?
Install @davidfuchs/mcp-uptime-kuma, set UPTIME_KUMA_URL (required) and auth env vars (username/password, JWT, or 2FA token as needed), then register the stdio MCP server in your agent.