Skip to main content
Glama
aderik

ha-automation-mcp

by aderik

Related Servers

Alternatives to ha-automation-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables MCP-speaking coding agents to talk directly to Home Assistant and the ESPHome dashboard: discovering entities and areas, reading live states, history and logs, rendering Jinja templates, calling services, and creating, editing or triggering automations and dashboards. Also allows ESPHome device configs to be read, validated, compiled and flashed, with all write operations off by default behind an explicit safety policy.
      111
      335 npm
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Connects LLM coding agents to Home Assistant instances, enabling configuration file management, service calls, template testing, and automation diagnostics via MCP tools.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes a Home Assistant instance as an MCP tool set, running as a stateful agent on Cloudflare Workers, enabling clients to read entity states, call services, run scripts and automations, and send commands to phones.
      163 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with Home Assistant to control smart home devices, query entity states, and manage automations using natural language. It provides over 90 tools for comprehensive system management, including dashboard configuration, service execution, and automation debugging.
      MIT

    TDQS

    B3.1/5.0

    Scored across 58 tools

    Disambiguation4/5

    Tools are largely grouped into clear CRUD families by resource (automations, helpers, dashboards, registry, etc.), but some overlaps exist: list_entities vs list_registry_entities, get_state vs get_history, and multiple upsert_* families can be confused without consulting descriptions. Descriptions help distinguish intent, so an agent can usually pick correctly.

    Naming Consistency4/5

    Names are predominantly snake_case with a verb_noun pattern (list_*, get_*, delete_*, etc.), making the set readable. However, there is an inconsistent mix of create_or_update_automation versus the upsert_* convention used for other resources, plus varied verbs like set, append, replace, and overwrite.

    Tool Count2/5

    With 58 tools, the server far exceeds the recommended 3–15 range and spans many disparate Home Assistant admin domains beyond automations (dashboards, registry, devices, config entries). The large number of CRUD groups multiplies the surface and makes the server heavy and harder to navigate.

    Completeness4/5

    The tool surface thoroughly covers automations, helpers, template entities, notify groups, history stats sensors, dashboards (down to view/card level), registry entities, devices, and config entries. Gaps remain for script and scene management, and there is no area creation/deletion, but core automation workflows are complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues