MCP Uptime Kuma vs SigNoz MCP Server
A side-by-side look at the MCP Uptime Kuma and SigNoz MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Uptime Kuma for monitoring work as a local process; choose SigNoz MCP Server 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.
- 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.
Choose SigNoz MCP Server when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
SIGNOZ_URL, SIGNOZ_API_KEY, LOG_LEVEL, TRANSPORT_MODE, MCP_SERVER_PORT, MCP_SERVER_HOST. - You want tools like
signoz_get_org_overview, signoz_list_metrics, signoz_query_metrics.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 60/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | UPTIME_KUMA_URLUPTIME_KUMA_USERNAMEUPTIME_KUMA_PASSWORDUPTIME_KUMA_2FA_TOKENUPTIME_KUMA_JWT_TOKENUPTIME_KUMA_HEADERS | SIGNOZ_URLSIGNOZ_API_KEYLOG_LEVELTRANSPORT_MODEMCP_SERVER_PORTMCP_SERVER_HOST |
| Verified owner | Community listing | Community listing |
| GitHub stars | 55 | 125 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 26 | 43 |
| Full listing | View MCP Uptime Kuma | View SigNoz MCP Server |
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
SigNoz MCP Server tools 43
signoz_get_org_overviewGet the current status and overall posture of the SigNoz deployment, with typed projections plus `sourceStats` containing every reported stats fieldsignoz_list_metricsDiscover active metric names and catalog metadatasignoz_query_metricsQuery known metrics for values, trends, breakdowns, or formulassignoz_get_top_metricsReturn top 100 metrics ranked by ingested sample volume with pre-computed percentages for cost and volume analysissignoz_check_metric_usageGiven a list of metric names (up to 50 per call), return which dashboards and alerts reference each onesignoz_check_metric_cardinalityReturn label/attribute keys for a single metric with cardinality counts and sample values, sorted highest-cardinality firstsignoz_get_field_keysDiscover available field keys for metrics, traces, or logssignoz_get_field_valuesGet possible values for a field keysignoz_list_alertsList firing/silenced/inhibited Alertmanager alert *instances* (not rule definitions)signoz_list_alert_rulesList configured alert-rule summaries, including inactive/OK and disabled rulessignoz_get_alertGet one alert rule's full definition by `idsignoz_get_alert_historyGet one rule's firing or state-transition history- +31 more on 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",
"-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"
}
}
}
}
SigNoz MCP Server
{
"mcpServers": {
"signoz-mcp-server": {
"url": "https://your-public-mcp-url.com/mcp"
}
}
}
Frequently asked questions
MCP Uptime Kuma is categorized under Monitoring and uses a local stdio subprocess. SigNoz MCP Server belongs to Monitoring and uses a remote HTTP/SSE transport. Pick MCP Uptime Kuma for monitoring work and SigNoz MCP Server 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 has no declared pricing — check the project's own site. SigNoz MCP Server has no declared pricing — check the project's own site. 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 signoz-mcp-server 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 60/100 (Good) with 1 views, 0 installs and 55 GitHub stars. SigNoz MCP Server has 57/100 (Good) with 1 views, 0 installs and 125 GitHub stars.