Skip to main content
Glama
chip10

HomeLab MCP

by chip10
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to HomeLab MCP

No user-submitted related servers found.

    Related Servers

    • 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

    • ha-mcp

      qubit999
      A
      license
      A
      quality
      C
      maintenance
      A self-hosted MCP server for Home Assistant that exposes full control over entity states, service calls, history, templates, and areas via local stdio, enabling AI assistants to manage your smart home.
      9
      64 npm
      MIT

    • hass-mcp-server

      jarahkon
      A
      license
      B
      quality
      C
      maintenance
      MCP server for full Home Assistant control, enabling AI agents to manage dashboards, automations, files, apps, entities, and more via REST API, WebSocket, and SSH.
      66
      113 npm
      MIT
    • Home Assistant MCP Server by homeassistant-ai

      Home Assistant MCP Serverofficial

      homeassistant-ai
      A
      license
      A
      quality
      A
      maintenance
      A comprehensive MCP server that enables AI assistants to interact with Home Assistant, control smart home devices, query states, execute services, and manage automations via natural language.
      77
      31,054 PyPI
      4,867
      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

    C2.8/5.0

    Scored across 26 tools

    Disambiguation4/5

    Tools are grouped into clear subsystems with distinct actions per resource, so an agent can generally tell them apart. The only minor overlap is ha_call_service versus ha_turn_on/ha_turn_off, but the descriptions clarify the direct vs generic path.

    Naming Consistency4/5

    Names consistently use lowercase snake_case with domain prefixes like pve_, ha_, frigate_, and docker_. Most follow a verb_noun pattern, but a few noun-only endpoints such as pve_nodes, frigate_stats, and ha_error_log are slight deviations.

    Tool Count4/5

    26 tools is above the typical well-scoped range, but the server covers four distinct subsystems: Proxmox, Home Assistant, Frigate, and Docker. Each area has a focused set of operational tools, so the count feels justified rather than bloated.

    Completeness4/5

    The tool surface covers the main operational workflows for all four domains: guest lifecycle, container control, Home Assistant state/service/automation, and Frigate monitoring. Some advanced operations like Docker inspect or Proxmox guest creation are absent, but core homelab management is well covered.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources