Skip to main content
Glama

Related Servers

Alternatives to ha-nexus-agent

No user-submitted related servers found.

    Related Servers

    • 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
      83 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server for Home Assistant integration with Claude and other LLMs, enabling querying and controlling Home Assistant entities, automations, and dashboards.
      29
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that exposes Home Assistant's REST and WebSocket APIs as 182 tools, enabling clients like Claude Code to control lights, climate, media, automations, and more. It also provides a status dashboard and supports running as a Home Assistant app or container.
      AGPL 3.0
    • 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
      44,239 PyPI
      5,046
      MIT
    • 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
      96 npm
      MIT

    TDQS

    A3.9/5.0

    Scored across 323 tools

    Disambiguation4/5

    Given 323 tools, overlap is surprisingly well managed: descriptions extensively use 'Use when'/'Not for' cross-references (e.g. entities_turn_on vs helpers_set_input_boolean vs services_call_service, entities_set_value vs helpers_set_input_number) to steer selection. There are still confusable clusters — areas_list_devices vs devices_list_devices vs devices_list_devices_in_area, and the HTTP vs WS transport duplicates (services_call_service vs ws_call_service, history_get_ha_config vs ws_get_config) — but they are documented rather than ambiguous.

    Naming Consistency4/5

    Strong, near-uniform namespace_prefix_verb_noun convention (areas_list_areas, entities_turn_on, supervisor_restart_addon, card_builder_create_card), making the surface scannable despite its size. Minor deviations exist, most notably the redundant git_git_* double prefix (git_git_status, git_git_init_config) and a few oddities like discover_refresh_index.

    Tool Count1/5

    323 tools is an extreme mismatch for any single server, far beyond the 50+ threshold, and forces the agent to lean on discover_tool_search just to navigate its own surface. Even with good organization, this volume guarantees a tiny per-call footprint of relevance and heavy cognitive overhead.

    Completeness4/5

    Coverage across the Home Assistant domain is remarkably broad — entities, devices, areas, labels, automations/scripts/scenes, dashboards, supervisor/add-ons, HACS, ESPHome, energy, voice, calendar, todo, statistics/history, git, files and zones all have lifecycle operations. A few acknowledged gaps (no area update tool, no partial Supervisor restore, no options-flow read) exist but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow