mcpbeat Sign in

MCP Uptime Kuma MCP Server

by davidfuchs Your server? Claim it
local only

MCP Uptime Kuma runs on your own machine — the client starts it, so there is no endpoint to ping. 934 installs a week from npm. Last commit 11 Sep 2026.

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

Installs per day peak 449 · avg 86 · +586% w/w
a month agotoday
934
Installs / week
npm · @davidfuchs/mcp-uptime-kuma
49
Stars
1 open issues
11 Sep 2026
Last commit
0 releases in 90 days
MIT
License
TypeScript

What the code does

We read the source, 21 h ago · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Secret passed into the image build Dockerfile:60
ENV UPTIME_KUMA_PASSWORD=""
Asks for container control access src/types/docker-host.ts:12, src/server.ts:1595
  dockerDaemon: z.string().optional().describe('Unix socket path (e.g. /var/run/docker.sock) when dockerType=socket, or TCP URL (e.g. http://docker-proxy:2375) when dockerType=tcp'),
In the project's build, not in the package

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

Builds a database query by concatenation .github/workflows/publish-npm.yml:28
      - name: Update package.json version
        run: |
          npm version ${{ steps.version.outputs.VERSION }} --no-git-tag-version

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add mcp-uptime-kuma -- npx -y @davidfuchs/mcp-uptime-kuma
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp-uptime-kuma": {
      "args": [
        "-y",
        "@davidfuchs/mcp-uptime-kuma"
      ],
      "command": "npx"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp-uptime-kuma]
command = "npx"
args = ["-y", "@davidfuchs/mcp-uptime-kuma"]
.cursor/mcp.json
{
  "mcpServers": {
    "mcp-uptime-kuma": {
      "args": [
        "-y",
        "@davidfuchs/mcp-uptime-kuma"
      ],
      "command": "npx"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp-uptime-kuma": {
      "args": [
        "-y",
        "@davidfuchs/mcp-uptime-kuma"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: UPTIME_KUMA_URL (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 (Your Uptime Kuma password (not required if using JWT token authentication or if authentication is disabled)), UPTIME_KUMA_2FA_TOKEN (Your 2FA token (only required if two-factor authentication is enabled on your account)), UPTIME_KUMA_JWT_TOKEN (Your JWT token for authentication (takes precedence over username/password if provided)), UPTIME_KUMA_HEADERS (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":"..."})). The author declared them in the registry entry; get the values from the project itself.

Alternatives to MCP Uptime Kuma

same job, measured the same way
Esa MCP Server
by koki-develop

A Model Context Protocol (MCP) server for esa.io

74 installs/wk local only
MCP For API
by appwrite

MCP (Model Context Protocol) server for Appwrite

33 496 installs/wk local only
MCP Sitecore Server
by antonytm

A Model Context Protocol server for Sitecore

484 installs/wk local only
Microsoft NuGet
by microsoft

A Model Context Protocol (MCP) server for NuGet.

local only
Gitlab MCP Server
by dubuqingfeng

GitLab MCP (Model Context Protocol) server for AI agents

62 installs/wk local only
Trello MCP Server
by billnobill

Trello Model Context Protocol (MCP) Server for AI Agents

40 installs/wk local only
MCP Prometheus
by jeanlopezxyz

A Model Context Protocol (MCP) server for Prometheus monitoring

112 installs/wk local only
Procm
by coder-ka

A Model Context Protocol (MCP) server for process management.

75 installs/wk local only

MCP Uptime Kuma — questions

Answers built from our own checks of this server.

Why is there no uptime for MCP Uptime Kuma?
MCP Uptime Kuma runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @davidfuchs/mcp-uptime-kuma was installed 934 times last week.
How do I connect MCP Uptime Kuma?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls @davidfuchs/mcp-uptime-kuma straight from npm; nothing to host, nothing to sign up for.
How many people use MCP Uptime Kuma?
The npm package @davidfuchs/mcp-uptime-kuma was installed 934 times in the last week. Week over week that is +586%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is MCP Uptime Kuma open source?
Yes — it is published under the MIT licence, written in TypeScript, 49 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.