MCP Server for Uptime Kuma
Manage Uptime Kuma 2 monitors, status pages and maintenance windows from an LLM
- Platforms
- CLI, self-hosted
- Runs
- Locally or Remotely
- Version
- 0.16.0
- Listing updated
- today
Similar MCP servers
About MCP Server for Uptime Kuma
MCP Server for Uptime Kuma is an MCP server for cloud and infrastructure. It can run locally on your machine or as a hosted remote server.
This server holds a live Socket.IO connection to your Uptime Kuma 2 instance, so status and heartbeat data are current without polling. Its 36 tools cover monitors of any type, notification channels, tags, maintenance windows, status pages and Docker hosts. Uptime Kuma 1.x is not supported.
It is tuned for context: summaries come first, and the roughly 85 type-specific monitor fields are looked up only when needed. Read tools show *** for passwords, tokens and API keys, and writing *** back keeps the stored value. UPTIME_KUMA_READ_ONLY removes every tool that creates, changes, pauses or deletes, and tools are annotated so clients can run reads unattended and ask before the rest.
Two run modes exist. Local stdio starts through npx on each machine. A shared Docker container serves streamable HTTP with bearer-token auth, Origin checks and rate limiting, which suits claude.ai and web clients, and the README warns to set MCP_AUTH_TOKEN and use TLS before exposing it. Login can use a username and password, a JWT token, or nothing if authentication is disabled.
Install
Run in a terminal
claude mcp add mcp-uptime-kuma --env UPTIME_KUMA_URL='<UPTIME_KUMA_URL>' --env UPTIME_KUMA_PASSWORD='<UPTIME_KUMA_PASSWORD>' --env UPTIME_KUMA_2FA_TOKEN='<UPTIME_KUMA_2FA_TOKEN>' --env UPTIME_KUMA_JWT_TOKEN='<UPTIME_KUMA_JWT_TOKEN>' --env UPTIME_KUMA_HEADERS='<UPTIME_KUMA_HEADERS>' -- npx -y @davidfuchs/mcp-uptime-kumaAdd to claude_desktop_config.json
{
"mcpServers": {
"mcp-uptime-kuma": {
"command": "npx",
"args": [
"-y",
"@davidfuchs/mcp-uptime-kuma"
],
"env": {
"UPTIME_KUMA_URL": "<UPTIME_KUMA_URL>",
"UPTIME_KUMA_PASSWORD": "<UPTIME_KUMA_PASSWORD>",
"UPTIME_KUMA_2FA_TOKEN": "<UPTIME_KUMA_2FA_TOKEN>",
"UPTIME_KUMA_JWT_TOKEN": "<UPTIME_KUMA_JWT_TOKEN>",
"UPTIME_KUMA_HEADERS": "<UPTIME_KUMA_HEADERS>"
}
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"mcp-uptime-kuma": {
"command": "npx",
"args": [
"-y",
"@davidfuchs/mcp-uptime-kuma"
],
"env": {
"UPTIME_KUMA_URL": "<UPTIME_KUMA_URL>",
"UPTIME_KUMA_PASSWORD": "<UPTIME_KUMA_PASSWORD>",
"UPTIME_KUMA_2FA_TOKEN": "<UPTIME_KUMA_2FA_TOKEN>",
"UPTIME_KUMA_JWT_TOKEN": "<UPTIME_KUMA_JWT_TOKEN>",
"UPTIME_KUMA_HEADERS": "<UPTIME_KUMA_HEADERS>"
}
}
}
}Add to .vscode/mcp.json
{
"servers": {
"mcp-uptime-kuma": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@davidfuchs/mcp-uptime-kuma"
],
"env": {
"UPTIME_KUMA_URL": "<UPTIME_KUMA_URL>",
"UPTIME_KUMA_PASSWORD": "<UPTIME_KUMA_PASSWORD>",
"UPTIME_KUMA_2FA_TOKEN": "<UPTIME_KUMA_2FA_TOKEN>",
"UPTIME_KUMA_JWT_TOKEN": "<UPTIME_KUMA_JWT_TOKEN>",
"UPTIME_KUMA_HEADERS": "<UPTIME_KUMA_HEADERS>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"mcp-uptime-kuma": {
"command": "npx",
"args": [
"-y",
"@davidfuchs/mcp-uptime-kuma"
],
"env": {
"UPTIME_KUMA_URL": "<UPTIME_KUMA_URL>",
"UPTIME_KUMA_PASSWORD": "<UPTIME_KUMA_PASSWORD>",
"UPTIME_KUMA_2FA_TOKEN": "<UPTIME_KUMA_2FA_TOKEN>",
"UPTIME_KUMA_JWT_TOKEN": "<UPTIME_KUMA_JWT_TOKEN>",
"UPTIME_KUMA_HEADERS": "<UPTIME_KUMA_HEADERS>"
}
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"mcp-uptime-kuma": {
"command": "npx",
"args": [
"-y",
"@davidfuchs/mcp-uptime-kuma"
],
"env": {
"UPTIME_KUMA_URL": "<UPTIME_KUMA_URL>",
"UPTIME_KUMA_PASSWORD": "<UPTIME_KUMA_PASSWORD>",
"UPTIME_KUMA_2FA_TOKEN": "<UPTIME_KUMA_2FA_TOKEN>",
"UPTIME_KUMA_JWT_TOKEN": "<UPTIME_KUMA_JWT_TOKEN>",
"UPTIME_KUMA_HEADERS": "<UPTIME_KUMA_HEADERS>"
}
}
}
}Using several servers? Build one config file with the MCP config generator.
Configuration
UPTIME_KUMA_URLThe URL of your Uptime Kuma instanceRequiredUPTIME_KUMA_USERNAMEYour Uptime Kuma username (not required if using JWT token authentication or if authentication is disabled)UPTIME_KUMA_PASSWORDYour Uptime Kuma password (not required if using JWT token authentication or if authentication is disabled)UPTIME_KUMA_2FA_TOKENYour 2FA token (only required if two-factor authentication is enabled on your account)UPTIME_KUMA_JWT_TOKENYour JWT token for authentication (takes precedence over username/password if provided)UPTIME_KUMA_HEADERSJSON 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_SECRETSSet to true to return credentials (passwords, tokens, auth headers) unredacted in tool output; by default they read "***"UPTIME_KUMA_READ_ONLYSet to true to expose only the tools that report, and none that create, change, pause or deleteUPTIME_KUMA_URLThe URL of your Uptime Kuma instanceRequiredUPTIME_KUMA_USERNAMEYour Uptime Kuma username (not required if using JWT token authentication or if authentication is disabled)UPTIME_KUMA_PASSWORDYour Uptime Kuma password (not required if using JWT token authentication or if authentication is disabled)UPTIME_KUMA_2FA_TOKENYour 2FA token (only required if two-factor authentication is enabled on your account)UPTIME_KUMA_JWT_TOKENYour JWT token for authentication (takes precedence over username/password if provided)UPTIME_KUMA_HEADERSJSON 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_SECRETSSet to true to return credentials (passwords, tokens, auth headers) unredacted in tool output; by default they read "***"UPTIME_KUMA_READ_ONLYSet to true to expose only the tools that report, and none that create, change, pause or deleteMCP_AUTH_TOKENShared secret clients must send as "Authorization: Bearer <token>"; requests without it are rejectedRequiredPORTPort the HTTP server listens onHOSTAddress to bind. Default 0.0.0.0; use 127.0.0.1 to accept local connections onlyALLOWED_ORIGINComma-separated origins allowed to call /mcp. Default * (no Origin validation)RATE_LIMIT_MAXRequests allowed per client IP every 15 minutes. 0 turns the limit offTRUST_PROXYTrust reverse-proxy X-Forwarded-For headers for rate limiting: a hop count (1), true/false, or an IP/subnet list. Unset = no trust
What it does
- 36 management tools
- Create and change monitors, channels, tags, maintenance windows and status pages.
- Live data
- A Socket.IO connection keeps status and heartbeats current.
- Read-only mode
- One setting removes every write tool.
- Credential redaction
- Secrets are masked as *** in tool output.
- Stdio or shared HTTP
- Run locally with npx or as a Docker container with bearer auth.
Good for
- Ask what is down right now and since when
- Find monitors that flapped this week
- Add an HTTP monitor with alerts to a channel
- Schedule a maintenance window for a set of monitors
- Build a public status page with groups
MCP Server for Uptime Kuma FAQ
Which Uptime Kuma versions work?
Version 2 or later; 1.x is not supported.
Can I make it read-only?
Yes, set UPTIME_KUMA_READ_ONLY to true.
How do I share it between machines?
Run the Docker container in streamable HTTP mode and set MCP_AUTH_TOKEN.
How does it log in?
Username and password, a JWT token (for 2FA), or no credentials if authentication is off.
How do I add MCP Server for Uptime Kuma to Claude Code?
Run this command in your terminal: claude mcp add mcp-uptime-kuma --env UPTIME_KUMA_URL='<UPTIME_KUMA_URL>' --env UPTIME_KUMA_PASSWORD='<UPTIME_KUMA_PASSWORD>' --env UPTIME_KUMA_2FA_TOKEN='<UPTIME_KUMA_2FA_TOKEN>' --env UPTIME_KUMA_JWT_TOKEN='<UPTIME_KUMA_JWT_TOKEN>' --env UPTIME_KUMA_HEADERS='<UPTIME_KUMA_HEADERS>' -- npx -y @davidfuchs/mcp-uptime-kuma
What are the best alternatives to MCP Server for Uptime Kuma?
The closest alternatives to MCP Server for Uptime Kuma are REA, Context7, Chrome DevTools MCP, Codebase Memory and GitHub.
Where this comes from
- Description: written from the project's README.
- Install steps: from the official MCP Registry entry.


