How do I connect MCP Uptime Kuma MCP Server to Claude?

Run `claude mcp add mcp-uptime-kuma -- npx -y -p @davidfuchs/mcp-uptime-kuma mcp-uptime-kuma-get-jwt http://localhost:3001 admin mypassword` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.

Is MCP Uptime Kuma MCP Server free?

The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.

What can MCP Uptime Kuma MCP Server do?

MCP Uptime Kuma MCP Server documents 28 tools to the agent, including active, addNotification, addTag. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.

MCP Uptime Kuma

Unclaimed

by DavidFuchs

A Model Context Protocol (MCP) server for Uptime Kuma version 2.

Set up this server

Compare servers My Stack

01 / Choose your client

02 / Before you connect

Authentication is not specified. Check the project instructions before connecting.

Install the runtime required by the project and make it available to your client.

Project instructionsEnvironment variable names (optional)

Use names from the project instructions, separated by commas. Enter names only, never secret values.

03 / Add the configuration

Source: generated from public install instructions

claude mcp add --transport stdio 'mcp-uptime-kuma' -- 'npx' '-y' '-p' '@davidfuchs/mcp-uptime-kuma' 'mcp-uptime-kuma-get-jwt' 'http://localhost:3001' 'admin' 'mypassword'

Run in your terminal after replacing any placeholders.

04 / Check it in your client

Open your client’s MCP settings and confirm the server connects and lists its tools. A copied configuration does not confirm a working connection.

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

28 of 28 tools

Documented tools (28)

From project documentation. A server handshake does not verify each tool’s description or behavior.

active

Filter by active (true) or inactive (false) monitors

addNotification

Create a new notification channel.

addTag

Create a new tag that can be assigned to monitors.

createMaintenance

Schedule a new maintenance window.

createMonitor

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

deleteMonitor

Permanently delete a monitor and all its heartbeat history.

deleteNotification

Permanently delete a notification channel.

deleteTag

Permanently delete a tag (removes it from all monitors).

getHeartbeats

Get status check history for a specific monitor.

getMaintenanceWindows

List all scheduled maintenance windows.

getMonitor

Get detailed configuration for a specific monitor by ID.

getMonitorSummary

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

getSettings

Get Uptime Kuma server settings.

keywords

Space-separated keywords for fuzzy matching against monitor pathNames

listHeartbeats

Get status check history for all monitors.

listMonitors

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

listMonitorTypes

Get all available monitor types supported by Uptime Kuma.

listNotifications

List all configured notification channels (Slack, Discord, email, webhooks, etc.).

listStatusPages

List all configured status pages.

listTags

List all tags defined in Uptime Kuma.

maintenance

Filter by maintenance mode status

pauseMonitor

Pause a monitor to stop performing checks.

resumeMonitor

Resume a paused monitor to restart checks.

status

(getMonitorSummary only): Heartbeat status ("0"=DOWN, "1"=UP, "2"=PENDING, "3"=MAINTENANCE)

type

Monitor type(s), comma-separated (e.g., "http", "http,ping,dns")

updateMonitor

Update an existing monitor's configuration.

updateNotification

Update an existing notification channel.

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about MCP Uptime Kuma MCP Server

How do I connect MCP Uptime Kuma MCP Server to Claude?: Run `claude mcp add mcp-uptime-kuma -- npx -y -p @davidfuchs/mcp-uptime-kuma mcp-uptime-kuma-get-jwt http://localhost:3001 admin mypassword` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.
Is MCP Uptime Kuma MCP Server free?: The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can MCP Uptime Kuma MCP Server do?: MCP Uptime Kuma MCP Server documents 28 tools to the agent, including active, addNotification, addTag. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.