Skip to main content
Glama
homeassistant-ai

Home Assistant MCP Server

Official
by homeassistant-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Home Assistant MCP Server

No user-submitted related servers found.

    Related Servers

    • ha-mcp

      osrd-gh
      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

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

    • HA Vibecode Agent

      Coolver
      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

    • mcp-ha

      Devitek
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Home Assistant that lets you control and query your smart home through natural language via MCP clients. Provides tools for entities, devices, services, automations, scripts, history, add-ons, and system info, with read-only access by default and optional configurable write support.
      1
      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

    A4/5.0

    Scored across 77 tools

    Disambiguation3/5

    Most tools have clearly distinct purposes (e.g., ha_get_state vs ha_get_entity vs ha_search), but there is notable overlap between configuration management tools like ha_config_set_helper and ha_set_integration for helpers, and ha_config_remove_group vs ha_remove_helpers_integrations for groups. Also, ha_config_get_dashboard has multiple modes (list, search, get) which could confuse an agent about the primary function.

    Naming Consistency3/5

    The tools predominantly follow the ha_<verb>_<noun> pattern (e.g., ha_get_state, ha_config_set_automation), which is consistent. However, there are deviations like ha_bulk_control, ha_call_event, and ha_manage_radio that don't follow the strict ha_<verb>_<noun> structure, and some tools like ha_eval_template mix the pattern with a different style.

    Tool Count2/5

    With 77 tools, this server is far above the typical well-scoped range. The high count reflects the broad domain of Home Assistant, but it overwhelms an agent with too many choices, many of which are edge-case-specific (e.g., ha_manage_theme, ha_get_dashboard_screenshot). This could lead to decision paralysis and increased risk of misselection.

    Completeness4/5

    The tool surface covers a wide range of Home Assistant domains: entity management, automations, scripts, scenes, dashboards, integrations, calendars, todo lists, backups, and more. There are minor gaps such as no direct tool for managing users or advanced network settings, but these are edge cases. Overall, the coverage is very comprehensive for the platform's scope.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources