Homebutler vs Infra Lens MCP

A side-by-side look at the Homebutler and Infra Lens MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Homebutler logoHomebutlerMonitoring · Local subprocess (stdio)All-in-one homelab management MCP server. Monitor system resources, manage Docker containers, Wake-on-LAN, scan networks, check open ports, and run alerts — across multiple servers via SSH. Single 10MB binary, zero dependencies.71GreatAuth: no auth requiredInfra Lens MCP logoInfra Lens MCPMonitoring · Local subprocess (stdio)SSH Linux metrics, baselines, anomaly detection, and plain-English infrastructure explanations.57GoodAuth: not declared

Verdict: choose Homebutler for monitoring work as a local process; choose Infra Lens MCP for monitoring as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Homebutler logoChoose 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.
Explore Homebutler

Infra Lens MCP logoChoose Infra Lens MCP when

  • You need dedicated capabilities in the Monitoring domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like analyze_server, analyze_server_snapshot, snapshot.
Explore Infra Lens MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecHomebutler logoHomebutlerInfra Lens MCP logoInfra Lens MCP
CategoryMonitoringMonitoring
Quality signal71/100 · Great57/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars3052
Directory activity 6 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools4010

Tools & capabilities

Homebutler tools 40

  • proxmox_statusGet Proxmox VE version, cluster status, and resources
  • proxmox_guestsList Proxmox QEMU and LXC guests, optionally filtered by node, status, or type
  • proxmox_nodeGet detailed Proxmox node status
  • proxmox_tasksGet the 50 most recent Proxmox tasks for a node
  • system_statusGet system status including CPU, memory, disk usage, and uptime
  • proxmox_guest_startStart one explicitly targeted Proxmox guest after confirmation and return the accepted task UPID
  • proxmox_guest_rebootReboot one explicitly targeted Proxmox guest after confirmation and return the accepted task UPID
  • proxmox_guest_shutdownGracefully shut down one explicitly targeted Proxmox guest after confirmation and return the accepted task UPID
  • proxmox_task_statusInspect one asynchronous Proxmox task by node and opaque UPID
  • proxmox_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 host
  • docker_listList Docker containers with their status, image, and ports
  • +28 more on the listing page

Infra Lens MCP tools 10

  • analyze_serverAnalyze a bounded sampled window with progress/cancellation support, then store only the completed observation
  • analyze_server_snapshotAnalyze and store one immediate snapshot without a sampling delay
  • snapshotStore a point-in-time observation without anomaly analysis
  • record_baselineSave a labeled healthy-state sample
  • compare_to_baselineCompare current state with a named baseline
  • get_historyReturn CPU, memory, or load history from SQLite
  • inspect_host_capabilitiesCheck required Linux commands and proc files before collection
  • plan_remediationPropose evidence-backed, approval-required remediation without executing changes
  • draft_incident_reportDraft an incident report and postmortem from persisted observations
  • compare_incident_windowsCompare adjacent windows for one host or the same window across two hosts

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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "higangssh-homebutler": {
      "command": "npx",
      "args": [
        "-y",
        "homebutler@latest"
      ]
    }
  }
}

Infra Lens MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "infra-lens-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "infra-lens-mcp"
      ]
    }
  }
}

Frequently asked questions

Homebutler is categorized under Monitoring and uses a local stdio subprocess. Infra Lens MCP belongs to Monitoring and uses a local stdio subprocess. Pick Homebutler for monitoring work and Infra Lens MCP 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. Infra Lens MCP 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 infra-lens-mcp 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. Infra Lens MCP has 57/100 (Good) with 0 views, 0 installs and 2 GitHub stars.