MCP Uptime Kuma vs UISP
A side-by-side look at the MCP Uptime Kuma and UISP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
U
UISPMonitoringMCP server for Ubiquiti UISP's REST API - network/ISP infrastructure monitoring for MSPs.48FairAuth: api key requiredVerdict: choose MCP Uptime Kuma for monitoring work as a local process; choose UISP for monitoring. 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.
UChoose UISP when
- You need dedicated capabilities in the Monitoring domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
UISP_API_KEY, UISP_BASE_URL, MCP_TRANSPORT, AUTH_MODE, CONDUIT_S2S_SECRET, LOG_LEVEL. - You want tools like
uisp_list_sites, uisp_get_site, uisp_search_sites.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | U UISP | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 60/100 · Good | 48/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | UPTIME_KUMA_URLUPTIME_KUMA_USERNAMEUPTIME_KUMA_PASSWORDUPTIME_KUMA_2FA_TOKENUPTIME_KUMA_JWT_TOKEN |
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
UISP tools 27
uisp_list_siteslist sites (network locations - sites, endpoints, and clients - each optionally tied to a UCRM client/service record).uisp_get_siteget a single site's detail.uisp_search_sites
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"
}
}
}
}
UISP
No confirmed install command for UISP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
MCP Uptime Kuma is categorized under Monitoring and uses a local stdio subprocess. UISP belongs to Monitoring and uses an install path we have not confirmed yet. Pick MCP Uptime Kuma for monitoring work and UISP 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. UISP has no confirmed install command yet — follow its own setup instructions.
MCP Uptime Kuma has no declared pricing — check the project's own site. UISP has no declared pricing — check the project's own site. Auth: api key required. 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 uisp 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. UISP has 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
