Skip to main content
Glama
LoganInTX

hass-mcp-extensions

by LoganInTX

Related Servers

Alternatives to hass-mcp-extensions

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for controlling and querying Home Assistant via its REST API, exposing tools to get entity states, list all states, and call services.
      16
      141 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enhanced Home Assistant MCP server with 22 context efficient tools for smart home control, automation trace debugging, entity registry management, CEL expression queries, and long-term statistics.
      22
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server and Home Assistant add-on that enables AI assistants to manage smart homes by creating automations, designing dashboards, and interacting with entities. It features native access to Home Assistant APIs, built-in Git versioning for safe rollbacks, and full management of HACS integrations.
      632
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to control Home Assistant via natural language, including device control, automation management, and system configuration.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Comprehensive development tools for Home Assistant, enabling file management, template testing, entity/state management, service calls, log access, and system information retrieval through MCP.
      MIT

    TDQS

    A3.6/5.0

    Scored across 28 tools

    Disambiguation3/5

    Several tools overlap in purpose (e.g., get_error_log vs get_core_log, call_service_tool vs entity_action, list_entities vs search_entities_tool), though descriptions help differentiate. Still, the boundaries are not always clear for an agent.

    Naming Consistency3/5

    Most tools follow a verb_noun pattern with snake_case, but some use noun_verb (e.g., entity_action) or have inconsistent suffixes like '_tool'. The pattern is recognizable but not fully consistent.

    Tool Count3/5

    28 tools is on the higher side for a single server, but given the breadth of Home Assistant, it is justifiable. Some redundancy suggests it could be streamlined.

    Completeness3/5

    Core operations are covered (read entities, call services, manage automations/scenes, logs), but missing delete operations for automations/scenes and no tool to create a scene from scratch. Gaps exist but are not critical.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing