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

TypeScript
★ 71 stars Last pushed 2026-11-19 License: MIT

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/[email protected]

Or add to your MCP client config:

{
  "mcpServers": {
    "mcp-uptime-kuma": {
      "command": "npx",
      "args": [
        "-y",
        "@davidfuchs/[email protected]"
      ],
      "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_URL required — The URL of your Uptime Kuma instance
  • UPTIME_KUMA_USERNAME — Your Uptime Kuma username (not required if using JWT token authentication or if authentication is disabled)
  • UPTIME_KUMA_PASSWORD secret — Your Uptime Kuma password (not required if using JWT token authentication or if authentication is disabled)
  • UPTIME_KUMA_2FA_TOKEN secret — Your 2FA token (only required if two-factor authentication is enabled on your account)
  • UPTIME_KUMA_JWT_TOKEN secret — Your JWT token for authentication (takes precedence over username/password if provided)
  • UPTIME_KUMA_HEADERS secret — 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 delete
  • UPTIME_KUMA_TOOLSETS — Comma-separated tool sets to register (monitors, heartbeats, notifications, tags, maintenance, status-pages, docker-hosts, settings); unset registers all
  • UPTIME_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_URL required — The URL of your Uptime Kuma instance
  • UPTIME_KUMA_USERNAME — Your Uptime Kuma username (not required if using JWT token authentication or if authentication is disabled)
  • UPTIME_KUMA_PASSWORD secret — Your Uptime Kuma password (not required if using JWT token authentication or if authentication is disabled)
  • UPTIME_KUMA_2FA_TOKEN secret — Your 2FA token (only required if two-factor authentication is enabled on your account)
  • UPTIME_KUMA_JWT_TOKEN secret — Your JWT token for authentication (takes precedence over username/password if provided)
  • UPTIME_KUMA_HEADERS secret — 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 delete
  • UPTIME_KUMA_TOOLSETS — Comma-separated tool sets to register (monitors, heartbeats, notifications, tags, maintenance, status-pages, docker-hosts, settings); unset registers all
  • MCP_AUTH_TOKEN required secret — Shared secret clients must send as "Authorization: Bearer <token>"; requests without it are rejected
  • PORT — Port the HTTP server listens on
  • HOST — Address to bind. Default 0.0.0.0; use 127.0.0.1 to accept local connections only
  • ALLOWED_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 off
  • TRUST_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

Data from the Official MCP Registry