Skip to main content
Glama
washyu

Homelab MCP Server

by washyu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Homelab MCP Server

No user-submitted related servers found.

    Related Servers

    • homelab-mcp

      jakubfabrici
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables assistants to operate a home lab through one authenticated HTTPS endpoint, including managing Proxmox VMs and containers, Home Assistant and ESPHome devices, Docker, shell access over SSH, Fully Kiosk tablets, and network discovery.
      MIT

    • homelab-mcp

      myraffy
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables management of homelab infrastructure, including Docker/Podman containers, Ollama AI models, Pi-hole DNS, Unifi networks, and Ansible inventory, with built-in security checks and automated pre-push validation.
      1
      MIT

    • mcp-homelab

      asvarnon
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI assistants real-time access to your homelab infrastructure. It enables querying node status, managing Docker containers, controlling Proxmox VMs, and inspecting OPNsense firewall state through natural conversation.
      2
      MIT

    • ProxmoxEmCP

      PureGrain
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Proxmox VE infrastructure, including VMs, containers, storage, and cluster operations via natural language.
      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

    B3.4/5.0

    Scored across 58 tools

    Disambiguation3/5

    While most tools target distinct actions, the abundance of deletion/removal variants (remove_device, purge_devices, decommission_device, etc.) and overlapping VM management tools create ambiguity. Agents may struggle to differentiate between subtly different tools like decommission_device and purge_failed_discoveries.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern with snake_case (e.g., create_proxmox_vm, get_network_sitemap). Preview tools append '_preview' uniformly. Minor deviations like start_interactive_shell are clear but break the pattern slightly.

    Tool Count3/5

    At 58 tools, the count is high for a single server. The broad scope (network discovery, Proxmox, services, Terraform) justifies many tools, but some could be consolidated (e.g., multiple deletion methods). The set feels slightly heavy but not extreme.

    Completeness4/5

    The tool set covers major lifecycle stages (create, read, update, delete, preview) across multiple domains. Notable gaps include lack of a direct sitemap update tool and limited service management beyond installation. However, the presence of preview tools for dangerous operations strengthens completeness.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources