Home › Cloud & Monitoring › MCP Server for Uptime Kuma
MCP Server for Uptime Kuma
Manage your Uptime Kuma 2 instance from an LLM: monitors, status pages, notifications, maintenance
Connect
Review any command before running it. Package names and URLs come from the server's own registry entry.
Package (npm 0.17.0)
npx -y @davidfuchs/mcp-uptime-kuma@0.17.0
Or add to your MCP client config:
{
"mcpServers": {
"mcp-uptime-kuma": {
"command": "npx",
"args": [
"-y",
"@davidfuchs/mcp-uptime-kuma@0.17.0"
],
"env": {
"UPTIME_KUMA_URL": "<YOUR_VALUE>",
"UPTIME_KUMA_PASSWORD": "<YOUR_VALUE>",
"UPTIME_KUMA_2FA_TOKEN": "<YOUR_VALUE>",
"UPTIME_KUMA_JWT_TOKEN": "<YOUR_VALUE>",
"UPTIME_KUMA_HEADERS": "<YOUR_VALUE>"
}
}
}
}
UPTIME_KUMA_URLrequired — The URL of your Uptime Kuma instanceUPTIME_KUMA_USERNAME— Your Uptime Kuma username (not required if using JWT token authentication or if authentication is disabled)UPTIME_KUMA_PASSWORDsecret — Your Uptime Kuma password (not required if using JWT token authentication or if authentication is disabled)UPTIME_KUMA_2FA_TOKENsecret — Your 2FA token (only required if two-factor authentication is enabled on your account)UPTIME_KUMA_JWT_TOKENsecret — Your JWT token for authentication (takes precedence over username/password if provided)UPTIME_KUMA_HEADERSsecret — JSON object of extra HTTP headers sent on every request to Uptime Kuma, for reaching it through an authenticating proxy such as Cloudflare Access (e.g. {"CF-Access-Client-Id":"...","CF-Access-Client-Secret":"..."})UPTIME_KUMA_INCLUDE_SECRETS— Set to true to return credentials (passwords, tokens, auth headers) unredacted in tool output; by default they read "***"UPTIME_KUMA_READ_ONLY— Set to true to expose only the tools that report, and none that create, change, pause or deleteUPTIME_KUMA_TOOLSETS— Comma-separated tool sets to register (monitors, heartbeats, notifications, tags, maintenance, status-pages, docker-hosts, settings); unset registers allUPTIME_KUMA_DYNAMIC_TOOLSETS— Set to true to start with the monitors tools and let the assistant load the other tool sets when it needs them; the client must refresh its tool list on notifications/tools/list_changed
Package (npm 0.17.0)
Package: npm @davidfuchs/mcp-uptime-kuma
UPTIME_KUMA_URLrequired — The URL of your Uptime Kuma instanceUPTIME_KUMA_USERNAME— Your Uptime Kuma username (not required if using JWT token authentication or if authentication is disabled)UPTIME_KUMA_PASSWORDsecret — Your Uptime Kuma password (not required if using JWT token authentication or if authentication is disabled)UPTIME_KUMA_2FA_TOKENsecret — Your 2FA token (only required if two-factor authentication is enabled on your account)UPTIME_KUMA_JWT_TOKENsecret — Your JWT token for authentication (takes precedence over username/password if provided)UPTIME_KUMA_HEADERSsecret — JSON object of extra HTTP headers sent on every request to Uptime Kuma, for reaching it through an authenticating proxy such as Cloudflare Access (e.g. {"CF-Access-Client-Id":"...","CF-Access-Client-Secret":"..."})UPTIME_KUMA_INCLUDE_SECRETS— Set to true to return credentials (passwords, tokens, auth headers) unredacted in tool output; by default they read "***"UPTIME_KUMA_READ_ONLY— Set to true to expose only the tools that report, and none that create, change, pause or deleteUPTIME_KUMA_TOOLSETS— Comma-separated tool sets to register (monitors, heartbeats, notifications, tags, maintenance, status-pages, docker-hosts, settings); unset registers allMCP_AUTH_TOKENrequired secret — Shared secret clients must send as "Authorization: Bearer <token>"; requests without it are rejectedPORT— Port the HTTP server listens onHOST— Address to bind. Default 0.0.0.0; use 127.0.0.1 to accept local connections onlyALLOWED_ORIGIN— Comma-separated origins allowed to call /mcp. Default * (no Origin validation)RATE_LIMIT_MAX— Requests allowed per client IP every 15 minutes. 0 turns the limit offTRUST_PROXY— Trust reverse-proxy X-Forwarded-For headers for rate limiting: a hop count (1), true/false, or an IP/subnet list. Unset = no trust
This server takes extra arguments — see its repository.
Related servers
Netdata
Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
kubeshark
Real-time Kubernetes network traffic visibility and API analysis for HTTP, gRPC, Redis, Kafka, DNS.
pal-mcp-server
The power of Claude Code / GeminiCLI / CodexCLI + [Gemini / OpenAI / OpenRouter / Azure / Grok / Ollama / Custom Model / All Of The Above]…
awslabs/mcp
Suite of servers for integrating with AWS services and resources.
cloudflare/mcp-server-cloudflare
Cloudflare MCP servers
spec-workflow-mcp
A Model Context Protocol (MCP) server that provides structured spec-driven development workflow tools for AI-assisted software…
Data from the Official MCP Registry