Skip to main content
Glama
Higangssh

homebutler

by Higangssh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Related Servers

Alternatives to homebutler

No user-submitted related servers found.

    Related Servers

    • homelab-mcp

      compactly8274
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for homelab diagnostics + auto-update pipeline, managing Docker hosts via SSH with read-only diagnostics, image-drift visibility, and automated update execution with rollback.
      MIT

    • homelab-mcp

      bjeans
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP servers for managing homelab infrastructure. Monitor Docker/Podman containers, Ollama AI models, Pi-hole DNS, Unifi networks, and Ansible inventory.
      42
      MIT

    • synapse-rmcp

      dinglebear-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server and CLI for host and container operations, enabling Docker and Compose control, SSH, host inspection, logs, ZFS, and safe file transfer. It exposes flux and scout MCP tools with parity from the original TypeScript server.
      2
      AGPL 3.0

    • mcp-sysadmin

      kreodevs
      A
      license
      Not graded
      quality
      A
      maintenance
      Provider-agnostic MCP server for managing heterogeneous infrastructure (SSH, Proxmox VE, Virtualizor, Hetzner Cloud, Cloudflare) via a JSON inventory, exposing tools for VM/container management, DNS, firewalls, and SSH operations.
      MIT

    • MCP Hub

      wnx82
      A
      license
      Not graded
      quality
      A
      maintenance
      A single MCP server that gives an AI assistant comprehensive access to manage a homelab, including SSH, Docker, Proxmox, Synology, Cloudflare, and more, with 85 tools and a centralized configuration.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 44 tools

    Disambiguation4/5

    Most tools have sharply distinct purposes, and descriptions explicitly cross-reference siblings (install_uninstall vs install_purge, backup_list vs backup_drill) to steer selection. However a few boundaries blur, notably doctor/report (both produce health diagnoses), install_status vs install_list, and system_status vs docker_stats vs inventory_scan, which could be confused.

    Naming Consistency4/5

    Names follow a largely predictable prefix_verb/noun scheme grouped by subsystem (docker_*, install_*, backup_*, watch_*, proxmox_*), each readable and consistent within its group. Minor deviations exist in bare noun tools (alerts, doctor, report, processes, wake) that break the otherwise uniform convention.

    Tool Count3/5

    At 44 tools this is heavy, and the surface spans many subsystems (docker, proxmox, backups, installs, watching, network, reporting) so the total is large rather than redundant. Most tools earn their place, but the sheer count raises discovery and misselection cost.

    Completeness4/5

    Coverage is broad and deep: full docker control, backup lifecycle including restore and verification, install lifecycle, proxmox guest management, and monitoring/watching. The one obvious dead end is that docker_stop has no docker_start (acknowledged in the description), leaving containers needing an out-of-band start.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources