Repocrunch vs Homebutler

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

Repocrunch logoRepocrunchMonitoring · Local subprocess (stdio)MCP server that gives AI agents structured, ground-truth GitHub repository intelligence. Analyze tech stack, dependencies, architecture, health metrics, and security indicators with deterministic JSON output.47FairAuth: not declaredHomebutler 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 required

Verdict: choose Repocrunch 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.

Which MCP server should you choose?

Repocrunch logoChoose Repocrunch when

  • You need dedicated capabilities in the Monitoring domain.
  • You prefer a local stdio subprocess transport.
Explore Repocrunch

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecRepocrunch logoRepocrunchHomebutler logoHomebutler
CategoryMonitoringMonitoring
Quality signal47/100 · Fair71/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars9304
Directory activity 2 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
ToolsNot listed40

Tools & capabilities

Repocrunch tools

No tool names declared yet. Check the project README from the listing page.

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

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.

Repocrunch

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "kimwwk-repocrunch": {
      "command": "uvx",
      "args": [
        "repocrunch"
      ]
    }
  }
}

Homebutler

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "higangssh-homebutler": {
      "command": "npx",
      "args": [
        "-y",
        "homebutler@latest"
      ]
    }
  }
}

Frequently asked questions

Repocrunch is categorized under Monitoring and uses a local stdio subprocess. Homebutler belongs to Monitoring and uses a local stdio subprocess. Pick Repocrunch for monitoring work and Homebutler 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.

Repocrunch has no declared pricing — check the project's own site. Homebutler is listed as free. Auth: no auth required. 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 kimwwk-repocrunch and higangssh-homebutler as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Repocrunch has a quality signal of 47/100 (Fair) with 2 views, 0 installs and 9 GitHub stars. Homebutler has 71/100 (Great) with 4 views, 0 installs and 304 GitHub stars.