What is the key difference between MCP Uptime Kuma and Statuser?

MCP Uptime Kuma belongs to the Monitoring category with local stdio execution, while Statuser belongs to the Monitoring category with local stdio execution.

How do I install MCP Uptime Kuma or Statuser in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are MCP Uptime Kuma and Statuser free or paid?

MCP Uptime Kuma operates under a Free / Open Source model (No auth required). Statuser operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

MCP Uptime Kuma lists 22 tools with 1 views and 54 GitHub stars. Statuser lists 6 tools with 0 views and 24 GitHub stars.

Can I use both MCP Uptime Kuma and Statuser together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

MCP Uptime Kuma vs Statuser

In-depth architectural comparison of the MCP Uptime Kuma and Statuser MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

MCP Uptime Kuma

Monitoring · Local stdio

Quality: 60/100 (Good) | Auth: No auth required

Statuser

Monitoring · Local stdio

Quality: 48/100 (Fair) | Auth: No auth required

Verdict Summary: Choose MCP Uptime Kuma if you need specialized Monitoring tools running via a local process. Choose Statuser if your workspace requires Monitoring integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose MCP Uptime Kuma when:

You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME, UPTIME_KUMA_PASSWORD, UPTIME_KUMA_2FA_TOKEN, UPTIME_KUMA_JWT_TOKEN, UPTIME_KUMA_HEADERS.
Primary tools included: getMonitorSummary, listMonitors, listMonitorTypes.

Explore MCP Uptime Kuma Details

Choose Statuser when:

You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: STATUSER_API_KEY.
Primary tools included: .

Feature & Specification Comparison

Specification	MCP Uptime Kuma Monitoring	Statuser Monitoring
Summary	A Model Context Protocol (MCP) server for Uptime Kuma version 2.	Monitor services, manage incidents and status pages in Statuser.cloud from your AI assistant.
Category & Scope	Monitoring	Monitoring
Quality signal

Tools & Capabilities Breakdown

MCP Uptime Kuma Tools (22)

getMonitorSummary

Get a quick overview of all monitors with their current status. Supports filtering.

listMonitors

Get the full list of all monitors with configurations. Supports filtering.

listMonitorTypes

Get all available monitor types supported by Uptime Kuma.

getMonitor

Get detailed configuration for a specific monitor by ID.

createMonitor

Create a new monitor (requires name and type at minimum).

updateMonitor

Update an existing monitor's configuration.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

MCP Uptime Kuma Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mcp-uptime-kuma": {
      "command": "npx",
      "args": [
        "-y",
        "-p",
        "@davidfuchs/mcp-uptime-kuma",
        "mcp-uptime-kuma-get-jwt"
      ],
      "env": {
        "UPTIME_KUMA_URL": "YOUR_UPTIME_KUMA_URL_HERE",
        "UPTIME_KUMA_USERNAME": "YOUR_UPTIME_KUMA_USERNAME_HERE",
        "UPTIME_KUMA_PASSWORD": "YOUR_UPTIME_KUMA_PASSWORD_HERE",
        "UPTIME_KUMA_2FA_TOKEN": "YOUR_UPTIME_KUMA_2FA_TOKEN_HERE",
        "UPTIME_KUMA_JWT_TOKEN": "YOUR_UPTIME_KUMA_JWT_TOKEN_HERE",
        "UPTIME_KUMA_HEADERS": "YOUR_UPTIME_KUMA_HEADERS_HERE"
      }
    }
  }
}

Statuser Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "statuser": {
      "command": "npx",
      "args": [
        "-y",
        "@statuser/mcp"
      ],
      "env": {
        "STATUSER_API_KEY": "YOUR_STATUSER_API_KEY_HERE"
      }
    }
  }
}

Frequently Asked Questions

MCP Uptime Kuma is categorized under Monitoring and uses a local stdio subprocess. In contrast, Statuser belongs to Monitoring using local stdio subprocess. Select MCP Uptime Kuma when you need capabilities focused on monitoring and Statuser when you require tools for monitoring.

More alternatives to MCP Uptime Kuma More alternatives to Statuser Monitoring category hub