MCP Uptime Kuma vs VMware Aria
A side-by-side look at the MCP Uptime Kuma and VMware Aria 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 VMware Aria for monitoring as a local process. 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 VMware Aria 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:
VMWARE_ARIA_CONFIG, VMWARE_ARIA_PROD_PASSWORD.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 60/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | UPTIME_KUMA_URLUPTIME_KUMA_USERNAMEUPTIME_KUMA_PASSWORD |
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
VMware Aria 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",
"-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"
}
}
}
}
VMware Aria
{
"mcpServers": {
"zw008-vmware-aria": {
"command": "uvx",
"args": [
"--from",
"vmware-aria",
"vmware-aria"
],
"env": {
"VMWARE_ARIA_CONFIG": "YOUR_VMWARE_ARIA_CONFIG_HERE",
"VMWARE_ARIA_PROD_PASSWORD": "YOUR_VMWARE_ARIA_PROD_PASSWORD_HERE"
}
}
}
}
Frequently asked questions
MCP Uptime Kuma is categorized under Monitoring and uses a local stdio subprocess. VMware Aria belongs to Monitoring and uses a local stdio subprocess. Pick MCP Uptime Kuma for monitoring work and VMware Aria 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. VMware Aria is listed as free. Auth: other. 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 zw008-vmware-aria 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. VMware Aria has 52/100 (Good) with 2 views, 0 installs and 3 GitHub stars.
