MCP Uptime Kuma vs Openhelm MCP
A side-by-side look at the MCP Uptime Kuma and Openhelm MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
O
Openhelm MCPMonitoring · Remote HTTP/SSESite & competitor monitoring: snapshots, evidence-backed diffs, briefs, price checks, mentions.43FairAuth: oauth 2.0Verdict: choose MCP Uptime Kuma for monitoring work as a local process; choose Openhelm MCP for monitoring over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Uptime Kuma when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
UPTIME_KUMA_URL, UPTIME_KUMA_USERNAME, UPTIME_KUMA_PASSWORD, UPTIME_KUMA_2FA_TOKEN, UPTIME_KUMA_JWT_TOKEN, UPTIME_KUMA_HEADERS. - You want tools like
getMonitorSummary, listMonitors, listMonitorTypes.
OChoose Openhelm MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | O Openhelm MCP | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 63/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | other | OAuth 2.0 |
| Pricing | Free | Not declared |
| Required env vars | UPTIME_KUMA_URLUPTIME_KUMA_USERNAMEUPTIME_KUMA_PASSWORDUPTIME_KUMA_2FA_TOKENUPTIME_KUMA_JWT_TOKENUPTIME_KUMA_HEADERS | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 60 | — |
| Directory activity | 5 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 26 | Not listed |
| Full listing | View MCP Uptime Kuma | View Openhelm MCP |
Tools & capabilities
MCP Uptime Kuma tools 26
getMonitorSummaryGet a quick overview of all monitors with their current status. Supports filtering.listMonitorsGet the full list of all monitors with configurations. Supports filtering.listMonitorTypesGet all available monitor types supported by Uptime Kuma.getMonitorGet detailed configuration for a specific monitor by ID.createMonitorCreate a new monitor (requires name and type at minimum).updateMonitorUpdate an existing monitor's configuration.deleteMonitorPermanently delete a monitor and all its heartbeat history.pauseMonitorPause a monitor to stop performing checks.resumeMonitorResume a paused monitor to restart checks.listHeartbeatsGet status check history for all monitors.getHeartbeatsGet status check history for a specific monitor.listNotificationsList all configured notification channels (Slack, Discord, email, webhooks, etc.).- +14 more on the listing page
Openhelm MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Uptime Kuma
{
"mcpServers": {
"mcp-uptime-kuma": {
"command": "npx",
"args": [
"-y",
"@davidfuchs/mcp-uptime-kuma@latest"
],
"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"
}
}
}
}
Openhelm MCP
{
"mcpServers": {
"monitoring": {
"url": "https://openhelm.ai/mcp/site-monitoring"
}
}
}
Frequently asked questions
MCP Uptime Kuma is categorized under Monitoring and uses a local stdio subprocess. Openhelm MCP belongs to Monitoring and uses a remote HTTP/SSE transport. Pick MCP Uptime Kuma for monitoring work and Openhelm MCP for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Uptime Kuma is listed as free. Auth: other. Openhelm MCP has no declared pricing — check the project's own site. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-uptime-kuma and monitoring as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Uptime Kuma has a quality signal of 63/100 (Good) with 5 views, 0 installs and 60 GitHub stars. Openhelm MCP has 43/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.