hass-mcp-server

Adoption-wise, this looks best categorized as a bridge that exposes Home Assistant as an MCP capability layer, not as a full AI smart-home platform and not as a general-purpose agent framework. The current evidence is mainly the official GitHub repository description, which supports the core positioning: it provides an HTTP-based MCP server so assistants such as Claude can interact with a Home Assistant instance. That is enough to describe what it is, but not enough to prove robustness in complex setups, production readiness, or usability for non-technical users.

In practice, its role is to turn entities, state, and some control surfaces inside an existing Home Assistant deployment into tools/context accessible by an AI assistant. A more accurate analogy is a “Home Assistant MCP connector” or an “LLM-facing wrapper for home automation APIs,” not a consumer voice assistant replacement. It helps with AI access to an existing HA environment; it does not replace device onboarding, automation design, or the broader smart-home platform itself.

For cost and setup, the evidence only shows an open-source GitHub project.