A side-by-side look at the MCP Server and Homebutler MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Server for monitoring work as a local process; choose Homebutler for monitoring as a local process. You can also run both side by side in one mcpServers block.
VS_API_KEY, VISUALSENTINEL_API_KEY, VS_API_BASE.proxmox_status, proxmox_guests, proxmox_node.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 57/100 · Good | 71/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Freemium | Free |
| Required env vars | VS_API_KEYVISUALSENTINEL_API_KEYVS_API_BASE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 304 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 40 |
| Full listing | View MCP Server | View Homebutler |
No tool names declared yet. Check the project README from the listing page.
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 portsPaste 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.
{
"mcpServers": {
"visualsentinel-mcp-server": {
"command": "npx",
"args": [
"-y",
"@visualsentinel/mcp-server"
],
"env": {
"VS_API_KEY": "YOUR_VS_API_KEY_HERE",
"VISUALSENTINEL_API_KEY": "YOUR_VISUALSENTINEL_API_KEY_HERE",
"VS_API_BASE": "YOUR_VS_API_BASE_HERE"
}
}
}
}
{
"mcpServers": {
"higangssh-homebutler": {
"command": "npx",
"args": [
"-y",
"homebutler@latest"
]
}
}
}