# MCP Server for Uptime Kuma

> MCP Server for Uptime Kuma is an MCP server for cloud and infrastructure. Manage Uptime Kuma 2 monitors, status pages and maintenance windows from an LLM. It can run locally on your machine or as a hosted remote server.

- **Kind:** MCP server
- **Platforms:** CLI, self-hosted
- **Repository:** https://github.com/davidfuchs/mcp-uptime-kuma
- **MCP Registry name:** io.github.DavidFuchs/mcp-uptime-kuma
- **Categories:** [cloud and infrastructure](https://ai-powered.com/categories/cloud-and-infrastructure), [developer tools](https://ai-powered.com/categories/developer-tools)
- **Listing updated:** 2026-11-18

## About

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.

## Features

- **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

## Install

### Claude Code (Terminal)

```sh
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
```

### Claude Desktop (claude_desktop_config.json)

```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>"
      }
    }
  }
}
```

### Cursor (~/.cursor/mcp.json)

```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>"
      }
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```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>"
      }
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```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>"
      }
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```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>"
      }
    }
  }
}
```

## 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.

## Alternatives

- [REA](https://ai-powered.com/mcp/rea): REA is an open-source MCP server for developer tools.
- [Context7](https://ai-powered.com/mcp/context7): Context7 is a freemium MCP server for developer tools.
- [Chrome DevTools MCP](https://ai-powered.com/mcp/chrome-devtools-mcp-2): Chrome DevTools MCP is an open-source MCP server for browser automation.
- [Codebase Memory](https://ai-powered.com/mcp/codebase-memory): Codebase Memory is an open-source MCP server for knowledge and memory.
- [GitHub](https://ai-powered.com/mcp/github-2): GitHub is an open-source MCP server for developer tools.
- [Serena MCP: the IDE for your agent](https://ai-powered.com/mcp/serena-mcp-the-ide-for-your-agent): Serena MCP: the IDE for your agent is an open-source MCP server for developer tools.
- [awesome-mcp-servers](https://ai-powered.com/mcp/awesome-mcp-servers-2): awesome-mcp-servers is an open-source MCP server for developer tools.
- [XERJ](https://ai-powered.com/mcp/xerj): XERJ is an open-source MCP server for knowledge and memory.

---
Source: https://ai-powered.com/mcp/mcp-server-for-uptime-kuma
