Uptime Kuma MCP Server
A Model Context Protocol (MCP) server for Uptime Kuma version 2. Supports stdio and streamable HTTP transports. Its 28 documented tools cluster into read & search, create & write, delete, update.
People connecting DevOps & monitoring tools to Claude, Cursor, VS Code, or another MCP client. The project is written in TypeScript.
VERIFIED ACTIVE
LAST COMMIT 2026-08-16 · ★ 47 · #11 OF 101 MAINTAINED DEVOPS & MONITORING · VERIFIED 2026-08-25
MIT · TypeScript servers · how we verify → /methodology
01 · Install Uptime Kuma
before you install - you'll need
Set UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME, UPTIME_KUMA_PASSWORD, UPTIME_KUMA_JWT_TOKEN, ALLOWED_ORIGIN, UPTIME_KUMA_INCLUDE_SECRETS, MCP_AUTH_TOKEN before connecting. UPTIME_KUMA_2FA_TOKEN is optional or environment-specific per the README.
Claude Code
claude mcp add davidfuchs-mcp-uptime-kuma -- npx -y @davidfuchs/mcp-uptime-kuma Claude Desktop / Cursor / VS Code - add to config
{
"mcpServers": {
"davidfuchs-mcp-uptime-kuma": {
"command": "npx",
"args": [
"-y",
"@davidfuchs/mcp-uptime-kuma"
]
}
}
} Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.
Using another client? Same JSON, different key
Claude Desktop · mcpServers
Cursor · mcpServers
VS Code · servers
Windsurf · mcpServers
Zed · context_servers
Cline · mcpServers
Roo Code · mcpServers
Continue · mcpServers
LibreChat · mcpServers
Gemini CLI · mcpServers
Codex CLI · mcp_servers
Full setup guides: every client.
02 · Evidence
Security posture
What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.
runs as local process (stdio) - runs on your machine with your user's permissions
license MIT - declared in the repository
npm package @davidfuchs/mcp-uptime-kuma - published under the repo owner's npm scope (@davidfuchs)
registry namespace io.github.DavidFuchs is GitHub-verified and matches the repo owner
03 · What Uptime Kuma can do
Prose above is summarized from the project's README and registry record - no invented capabilities.
What you can build
With this server connected, an agent can get a quick overview of all monitors with their current status. Supports filtering, get all available monitor types supported by Uptime Kuma, get detailed configuration for a specific monitor by ID, and create a new monitor (requires name and type at minimum).
Capability map
Tools grouped from the project's README - what Uptime Kuma lets an agent do.
read & search
11 tools - e.g. Get a quick overview of all monitors with their current status. Supports filtering.; Get the full list of all monitors with configurations. Supports filtering.; Get all available monitor types supported…
getMonitorSummary · listMonitors · listMonitorTypes · getMonitor · listHeartbeats · getHeartbeats…
create & write
4 tools - e.g. Create a new monitor (requires name and type at minimum).; Create a new notification channel.; Create a new tag that can be assigned to monitors.
createMonitor · addNotification · addTag · createMaintenance
delete
3 tools - e.g. Permanently delete a monitor and all its heartbeat history.; Permanently delete a notification channel.; Permanently delete a tag (removes it from all monitors).
deleteMonitor · deleteNotification · deleteTag
update
2 tools - e.g. Update an existing monitor's configuration.; Update an existing notification channel.
updateMonitor · updateNotification
Pause Monitor
1 tool - e.g. Pause a monitor to stop performing checks.
pauseMonitor
Resume Monitor
1 tool - e.g. Resume a paused monitor to restart checks.
resumeMonitor
Keywords
1 tool - e.g. Space-separated keywords for fuzzy matching against monitor pathNames
keywords
Type
1 tool - e.g. Monitor type(s), comma-separated (e.g., "http", "http,ping,dns")
type
Latest releases
v0.11.9 · 2026-08-16
finish #65 - stop coercing junk into numeric arguments, and filter summaries by parent
v0.11.8 · 2026-08-15
verify monitor writes actually persisted instead of trusting "Saved." · heartbeat ordering edge cases, staleness signal, and the limit aliases (#56) · authenticate and Origin-validate the streamable HTTP transport (#62)
v0.11.4 · 2026-08-14
load .env.test with override so ambient env vars cannot redirect the integration suite · relabel tool schema dialect from draft-07 to 2020-12 (#83) · Bump the npm_and_yarn group across 1 directory with 6 updates · Bump…
04 · Who maintains Uptime Kuma
mcp-uptime-kuma is maintained by davidfuchs. It's the only MCP server we track from this author; the repo dates to Nov 2025.
05 · Facts
- repository
- github.com/davidfuchs/mcp-uptime-kuma
- category
- DevOps & monitoring - ranked #11 of 101 actively-maintained DevOps & monitoring servers as of 2026-08-25.
- release cadence
- 6 releases in the last 90 days (latest 2026-08-16)
- registry
- io.github.DavidFuchs/mcp-uptime-kuma (active, first published 2025-11-25 · 13 versions)
- packages
- npm:@davidfuchs/mcp-uptime-kuma
06 · Uptime Kuma FAQ
Is Uptime Kuma still maintained?
Yes - as of 2026-08-25, its last commit was 2026-08-16 and it shipped 6 releases in the last 90 days. We re-verify nightly.
What can Uptime Kuma do?
With this server connected, an agent can get a quick overview of all monitors with their current status. Supports filtering, get all available monitor types supported by Uptime Kuma, get detailed configuration for a specific monitor by ID, and create a new monitor (requires name and type at minimum).
How do I install Uptime Kuma?
Run `npx -y @davidfuchs/mcp-uptime-kuma`. The README documents 8 environment variables (UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME, UPTIME_KUMA_PASSWORD…) to set first. Set UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME, UPTIME_KUMA_PASSWORD, UPTIME_KUMA_JWT_TOKEN, ALLOWED_ORIGIN, UPTIME_KUMA_INCLUDE_SECRETS, MCP_AUTH_TOKEN before connecting. UPTIME_KUMA_2FA_TOKEN is optional or environment-specific per the README. You can also paste the ready-made client config above.
Does Uptime Kuma run locally?
Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.
07 · Alternatives to Uptime Kuma
Alternatives to Uptime Kuma
Maintained DevOps & monitoring servers if Uptime Kuma isn't the fit.
- World Monitor Live global intelligence: real-time markets, conflicts, country risk, chokepoints, energy. 39 tools. ★ 83,963 · 2026-08-24
- Open Metadata Official OpenMetadata MCP: governed context and business semantics for AI assistants and agents. ★ 14,959 · 2026-08-25
- Kubeshark MCP Server Real-time Kubernetes network traffic visibility and API analysis for HTTP, gRPC, Redis, Kafka, DNS. ★ 12,057 · 2026-08-18
- Grafana An MCP server giving access to Grafana dashboards, data and more. ★ 3,384 · 2026-08-24
- Radar Kubernetes visibility for AI agents: query workloads, events, logs, topology, and Helm releases. ★ 3,103 · 2026-08-24
- Testkube MCP MCP server for Testkube - Manage test workflows, executions, and artifacts via AI assistants ★ 1,647 · 2026-08-24
Pairs well with
Servers that cover what Uptime Kuma doesn't - only shown when the pairing reason fits the companion.
More DevOps & monitoring MCP servers · Process · Dynatrace MCP · Taskbounty Check · Go Model · Log Analyzer MCP
More TypeScript MCP servers · Apple Health MCP · Eight Sleep MCP · Garminmcp · Google Ads MCP · Google Health MCP · see all