Homebutler vs OneUptime
A side-by-side look at the Homebutler and OneUptime MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Homebutler for monitoring work as a local process; choose OneUptime 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 Homebutler when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
proxmox_status, proxmox_guests, proxmox_node.
Choose OneUptime when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
create_team, get_team, list_teams.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 71/100 · Great | 70/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 305 | 7,757 |
| Directory activity | 6 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 40 | 199 |
| Full listing | View Homebutler | View OneUptime |
Tools & capabilities
Homebutler tools 40
proxmox_statusGet Proxmox VE version, cluster status, and resourcesproxmox_guestsList Proxmox QEMU and LXC guests, optionally filtered by node, status, or typeproxmox_nodeGet detailed Proxmox node statusproxmox_tasksGet the 50 most recent Proxmox tasks for a nodesystem_statusGet system status including CPU, memory, disk usage, and uptimeproxmox_guest_startStart one explicitly targeted Proxmox guest after confirmation and return the accepted task UPIDproxmox_guest_rebootReboot one explicitly targeted Proxmox guest after confirmation and return the accepted task UPIDproxmox_guest_shutdownGracefully shut down one explicitly targeted Proxmox guest after confirmation and return the accepted task UPIDproxmox_task_statusInspect one asynchronous Proxmox task by node and opaque UPIDproxmox_script_listList the curated Proxmox VE Community Scripts catalog (community-scripts/ProxmoxVE)proxmox_script_commandRender the pinned install command for one Proxmox VE Community Script. Never fetches or runs it; the caller reviews and runs it themselves on the Proxmox hostdocker_listList Docker containers with their status, image, and ports- +28 more on the listing page
OneUptime tools 199
create_teamCreate a new Team in OneUptime. Returns the created Team object with its ID. Use this to add new Teams to your project. Note: projectId is inferred from your API key — you do not need to provide it.get_teamRetrieve a single Team by its unique ID from OneUptime. Use list_teams first if you need to find the ID.list_teamsList and search Teams from OneUptime with optional filtering, pagination, and sorting. Returns an array of Team objects plus the total matching count.update_teamUpdate an existing Team in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_team afterwards to see the updated record.delete_teamPermanently delete a Team from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion.count_teamsCount the total number of Teams in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing.create_labelCreate a new Label in OneUptime. Returns the created Label object with its ID. Use this to add new Labels to your project. Note: projectId is inferred from your API key — you do not need to provide it.get_labelRetrieve a single Label by its unique ID from OneUptime. Use list_labels first if you need to find the ID.list_labelsList and search Labels from OneUptime with optional filtering, pagination, and sorting. Returns an array of Label objects plus the total matching count.update_labelUpdate an existing Label in OneUptime. Only include the fields you want to change - unspecified fields will remain unchanged. Use get_label afterwards to see the updated record.delete_labelPermanently delete a Label from OneUptime. This action cannot be undone. Returns a confirmation message upon successful deletion.count_labelsCount the total number of Labels in OneUptime, optionally filtered by query criteria. Returns a single number. Useful for dashboards, reports, or checking if records exist before listing.- +187 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.
Homebutler
{
"mcpServers": {
"higangssh-homebutler": {
"command": "npx",
"args": [
"-y",
"homebutler@latest"
]
}
}
}
OneUptime
{
"mcpServers": {
"oneuptime": {
"command": "npx",
"args": [
"-y",
"oneuptime"
]
}
}
}
Frequently asked questions
Homebutler is categorized under Monitoring and uses a local stdio subprocess. OneUptime belongs to Monitoring and uses a remote HTTP/SSE transport. Pick Homebutler for monitoring work and OneUptime 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.
Homebutler is listed as free. Auth: no auth required. OneUptime 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 higangssh-homebutler and oneuptime as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Homebutler has a quality signal of 71/100 (Great) with 6 views, 0 installs and 305 GitHub stars. OneUptime has 70/100 (Great) with 2 views, 0 installs and 7,757 GitHub stars.