A Model Context Protocol (MCP) server for Uptime Kuma version 2.
{
"mcpServers": {
"uptime-kuma": {
"env": {
"UPTIME_KUMA_URL": "http://your-uptime-kuma-instance:3001",
"UPTIME_KUMA_PASSWORD": "your_password",
"UPTIME_KUMA_USERNAME": "your_username"
},
"args": [
"-y",
"@davidfuchs/mcp-uptime-kuma"
],
"command": "npx"
}
}
}A Model Context Protocol (MCP) server for Uptime Kuma version 2.
Is it safe?
No known CVEs for args.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 10 days ago. 16 stars. 2,010,836 weekly downloads.
Will it work with my client?
Transport: stdio, sse, http. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
Context cost
22 tools. ~1,500 tokens (0.7% of 200K). Consider loading selectively.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y args 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
getMonitorSummaryGet a quick overview of all monitors with their current status. Supports filtering.
listMonitorsGet the full list of all monitors with configurations. Supports filtering.
listMonitorTypesGet all available monitor types supported by Uptime Kuma.
getMonitorGet detailed configuration for a specific monitor by ID.
createMonitorCreate a new monitor (requires name and type at minimum).
updateMonitorUpdate an existing monitor's configuration.
deleteMonitorPermanently delete a monitor and all its heartbeat history.
pauseMonitorPause a monitor to stop performing checks.
resumeMonitorResume a paused monitor to restart checks.
listHeartbeatsGet status check history for all monitors.
This server is missing a description.If you've used it, help the community.
Add informationLast scanned 9h ago
No known vulnerabilities.
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.