Skip to main content
Glama
RomanovVIII

ST67 Home Assistant MCP

by RomanovVIII
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ST67 Home Assistant MCP

No user-submitted related servers found.

    Related Servers

    • Home Assistant MCP Server

      diverdown1964
      F
      license
      B
      quality
      Not graded
      maintenance
      Enables control and monitoring of Home Assistant smart home devices through MCP, allowing users to list entities, check device states, and call services to control lights, switches, sensors, and other connected devices.
      4
      -

    • homeassistant-gateway

      vypdev
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables secure, auditable access to Home Assistant through MCP, with a read-only observer profile and an operator profile for controlled mutations.
      2
      MIT

    • hass-mcp

      TheWhykiki
      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
      111 npm
      MIT

    • Sakura-MCP-Server

      Guyao146
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables secure remote control of Home Assistant and Life Dashboard/DSH via MCP, supporting entity state queries, whitelisted entity/scene control, lifecycle overview reading, DSH workspace summaries, and follow-up sending.
      1
      GNU Lesser General Public v2.1 only
    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.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool occupies a distinct role: Lovelace preview and apply split read-only planning from approved writes, while ha_rest and ha_ws are clearly separated by protocol and ha_status is local-only. No two tools appear interchangeable, and the constraints in each description reinforce the boundary.

    Naming Consistency4/5

    All tools share the ha_ prefix and snake_case, and the Lovelace pair uses verb-like preview/apply. ha_rest, ha_ws, and ha_status are protocol/resource nouns rather than verb_noun actions, so the pattern is consistent but not a strict action-oriented convention.

    Tool Count5/5

    Five tools is a compact, appropriate surface for a Home Assistant bridge: two for Lovelace lifecycle, two generic protocol access points, and one status check. Nothing feels redundant or missing at the count level.

    Completeness5/5

    The generic ha_rest and ha_ws tools give broad coverage of Home Assistant's API surface, while ha_lovelace_preview/apply provide a safe complete edit workflow for dashboards. A local status check rounds out the set, leaving no obvious dead ends for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources