UISP vs MCP Uptime Kuma
A side-by-side look at the UISP and MCP Uptime Kuma 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 UISP for monitoring work; choose MCP Uptime Kuma for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | U UISP | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 48/100 · Fair | 60/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | UISP_API_KEYUISP_BASE_URLMCP_TRANSPORTAUTH_MODECONDUIT_S2S_SECRETLOG_LEVEL |
Tools & capabilities
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_sitessearch sites/endpoints/clients by name, address, MAC address, or IP address.uisp_list_site_clientslist all client sites belonging to a given (parent) site.uisp_get_site_statisticsget upload/download traffic between a site and its parent site.uisp_get_site_traffic_summaryget a site's total upload/download for a given interval up to now.uisp_list_deviceslist devices (hostname/IP/MAC, status, parent site).uisp_get_deviceget a single device's status overview.uisp_get_device_detailget a device's detail, optionally including interfaces and/or connected stations.uisp_get_device_statisticsget device telemetry (CPU/RAM/signal/temperature/throughput).uisp_list_device_interfaceslist a device's network interfaces, including configured IP addresses.uisp_get_device_by_maclook up a device by its MAC address.- +15 more on the listing page
MCP Uptime Kuma tools 26
getMonitorSummaryGet a quick overview of all monitors with their current status. Supports filtering.
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.
UISP
No confirmed install command for UISP yet — follow the setup steps linked from its listing page rather than a guessed package name.
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"
}
}
}
}
Frequently asked questions
UISP is categorized under Monitoring and uses an install path we have not confirmed yet. MCP Uptime Kuma belongs to Monitoring and uses a local stdio subprocess. Pick UISP for monitoring work and MCP Uptime Kuma 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.
UISP has no declared pricing — check the project's own site. Auth: api key required. MCP Uptime Kuma 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 uisp and mcp-uptime-kuma as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, UISP has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. MCP Uptime Kuma has 60/100 (Good) with 1 views, 0 installs and 55 GitHub stars.
