Skip to main content
Glama
Sign In
Home Assistant MCP Server

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
      126 npm
      MIT

    • HA Vibecode Agent

      Coolver
      A
      license
      Not graded
      quality
      B
      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.
      652
      MIT

    • mcp-ha

      Devitek
      A
      license
      Not graded
      quality
      B
      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
      189 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.7/5.0

    Scored across 77 tools

    Disambiguation3/5

    Most tools target a distinct resource/action, and descriptions cross-reference alternatives. However, several boundaries are still fuzzy in practice: state vs. registry vs. search, ha_bulk_control vs. ha_call_service, helper groups vs. service groups, and read vs. manage HACS all require careful reading to avoid misselection.

    Naming Consistency4/5

    All names use snake_case with a consistent ha_ prefix and mostly verb_noun/resource_action structure. The main deviations are parallel families such as ha_config_set_* vs. ha_set_* for similar resources and ha_manage_* vs. ha_get_*/ha_set_*.

    Tool Count1/5

    77 tools far exceeds a well-scoped surface (typically 3-15) and is an extreme mismatch even for a broad platform. Home Assistant is wide, but the surface is heavily fragmented into many specialized tools rather than consolidated around core operations.

    Completeness5/5

    Coverage spans entities, devices, areas/floors, automations, scripts, scenes, helpers, dashboards/resources, calendars, todo, zones, labels/categories, integrations, apps, HACS, backups, updates/repairs, logs, services, history, traces, radio, energy, and pipelines. No obvious dead ends remain, and ha_call_service fills service-level gaps.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled

    Resources