MCP Uptime Kuma runs on your own machine — the client starts it, so there is no endpoint to ping. 775 installs a week from npm. Last commit 11 Oct 2026.
A Model Context Protocol (MCP) server for Uptime Kuma version 2.
What the code does
We read the source, 5 d ago · rules 995398eba69f
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.
ENV UPTIME_KUMA_PASSWORD=""
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'),
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.
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.
claude mcp add mcp-uptime-kuma -e 'UPTIME_KUMA_URL=<UPTIME_KUMA_URL>' -- npx -y @davidfuchs/mcp-uptime-kuma{
"mcpServers": {
"mcp-uptime-kuma": {
"command": "npx",
"args": [
"-y",
"@davidfuchs/mcp-uptime-kuma"
],
"env": {
"UPTIME_KUMA_URL": "<UPTIME_KUMA_URL>"
}
}
}
}[mcp_servers.mcp-uptime-kuma]
command = "npx"
args = ["-y", "@davidfuchs/mcp-uptime-kuma"]
env = { UPTIME_KUMA_URL = "<UPTIME_KUMA_URL>" }{
"mcpServers": {
"mcp-uptime-kuma": {
"command": "npx",
"args": [
"-y",
"@davidfuchs/mcp-uptime-kuma"
],
"env": {
"UPTIME_KUMA_URL": "<UPTIME_KUMA_URL>"
}
}
}
}{
"servers": {
"mcp-uptime-kuma": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@davidfuchs/mcp-uptime-kuma"
],
"env": {
"UPTIME_KUMA_URL": "<UPTIME_KUMA_URL>"
}
}
}
}Put your own value in place of
<UPTIME_KUMA_URL> (The URL of your Uptime Kuma instance).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
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":"..."})).
Alternatives to MCP Uptime Kuma
same job, measured the same wayA Model Context Protocol (MCP) server for esa.io
MCP (Model Context Protocol) server for Appwrite
A Model Context Protocol server for Sitecore
A Model Context Protocol (MCP) server for NuGet.
GitLab MCP (Model Context Protocol) server for AI agents
Trello Model Context Protocol (MCP) Server for AI Agents
A Model Context Protocol (MCP) server for process management.
A Model Context Protocol (MCP) server for Prometheus monitoring
MCP Uptime Kuma — questions
Answers built from our own checks of this server.