Skip to main content
Glama
Sign In
Fistacho

ha-nexus-agent

by Fistacho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ha-nexus-agent

No user-submitted related servers found.

    Related Servers

    • 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
      130 npm
      MIT

    • hass-mcp

      HiTechLabTN
      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

    • HA MCP Server

      driin0
      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
    • 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
      124,995 PyPI
      5,395
      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
      170 npm
      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.8/5.0

    Scored across 330 tools

    Disambiguation3/5

    Most individual tools are clearly documented with explicit 'Use when' / 'Not for' boundaries, but the 330-tool surface still contains many near-siblings: entities_list_entities vs ws_get_states, history_get_ha_config vs ws_get_config, services_call_service vs ws_call_service, and helpers_set_input_* vs generic entities_* tools. These overlaps are resolvable only by reading long descriptions, so misselection risk remains high.

    Naming Consistency4/5

    The set is predominantly namespace_verb_noun and follows the same pattern across domains (entities_get_entity, automations_delete_script, labels_create_label). A few names are misleading rather than inconsistent, such as history_get_system_info returning only a liveness message and hacs_list_hacs_critical_updates actually listing any pending upgrade.

    Tool Count1/5

    330 tools is far beyond a well-scoped MCP surface and vastly exceeds the calibration's 50+ 'extreme mismatch' threshold. Many tools are niche diagnostics, duplicate low-level access paths, or convenience wrappers, making the catalogue costly to search and easy to misuse.

    Completeness4/5

    The surface is extremely broad, covering entity control, registries, services, automations/scripts/scenes, dashboards, backups, add-ons, HACS, ESPHome, energy, voice, and labels. A few gaps exist, such as removing a device from all config entries at once and partial Supervisor restores, but most Home Assistant workflows have a corresponding tool.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources