Skip to main content
Glama
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
      73 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
      72,385 PyPI
      4,819
      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
      86 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

    C2.9/5.0

    Scored across 317 tools

    Disambiguation4/5

    Most tools are clearly namespaced by domain (e.g., esphome_*, card_builder_*, services_*), reducing ambiguity. However, there is overlap between entities_bulk_control and areas_control_area (both turn on/off multiple entities), and services_render_template vs ws_render_template serve nearly identical purposes. Overall, the set is mostly distinct with minor confusions.

    Naming Consistency4/5

    The dominant pattern is <namespace>_<verb>_<noun> (e.g., calendar_create_event, devices_list_devices), which is consistent across most namespaces. Minor deviations exist: some namespaces mix verb order (e.g., esphome_lvgl_get_page_widgets vs esphome_lvgl_add_widget) and a few tools omit a namespace (e.g., history_get_state_history). Still, the overall convention is predictable.

    Tool Count2/5

    With 317 tools, this is an extreme count for a single MCP server, even for a comprehensive Home Assistant wrapper. The tool count is excessive for an agent to manage working memory, though the discover_* tools partially mitigate this. The server's scope is broad, but the sheer number makes it unwieldy.

    Completeness3/5

    The server covers many domains extensively (entities, services, automations, devices, areas, zones, labels, energy, voice, card builder, esphome, etc.). However, there are notable gaps, e.g., no update/remove for calendars (calendar_create_event/delete_event but no edit), no conditional wait tool, and no person management. The coverage is broad but not uniform, with some areas missing operations.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources