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
      75 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.
      636
      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
      96 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.9/5.0

    Scored across 77 tools

    Disambiguation4/5

    The tool set is large and has several naturally overlapping surfaces (ha_search vs ha_get_state vs ha_get_entity vs ha_get_overview for reading, and ha_config_set_group vs ha_config_set_helper(helper_type='group')), but every description carries explicit 'WHEN NOT TO USE' sections that steer the agent to the correct tool. ha_call_service and ha_bulk_control are also carefully distinguished from the dedicated tools. A few read tools still require careful reading to pick correctly.

    Naming Consistency3/5

    All names use the ha_ prefix and a verb_noun shape, but the verb/infix conventions are mixed: some resources use ha_config_get/set/remove (automation, script, scene, label, category), others use bare ha_get/set/remove (entity, device, zone, todo), and many use ha_manage (app, pipeline, blueprints, hacs, theme, radio, backup, updates). The inconsistency is readable but not predictable.

    Tool Count2/5

    77 tools is far above the 25-tool threshold for 'too many' and makes selection cognitively heavy. The breadth (entities, devices, areas, automations, scripts, scenes, dashboards, helpers, integrations, HACS, apps, backups, radios, energy, calendar, etc.) partly justifies the count, but consolidation into more action-parameterized tools would reduce it substantially.

    Completeness4/5

    Coverage of the Home Assistant domain is exceptionally broad, with full CRUD/lifecycle for automations, scripts, scenes, helpers, dashboards, entities, devices, labels, categories, zones, todos, and calendars, plus diagnostics, history, traces, backups and updates. The one notable gap is that ha_get_skill_guide — which many write tools mark as a mandatory first call — is currently broken, creating a dead end in the documented workflow.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources