Key takeaways

  • Ask an AI assistant to create an automation, a script or a dashboard in plain language, rather than writing the configuration yourself.
  • When an automation misbehaves, the assistant can read its execution traces, identify the issue and suggest fixes.
  • It reaches everything in Home Assistant, where the built-in MCP server only covers entities exposed to Assist.
  • Guard rails are included: a Read Only Mode toggle, per-tool switches, approval policies and automatic edit backups.
  • The catches: it needs an administrator-level account, some tools are beta, and the stdio route has known problems.

What it is

HA-MCP is a server that lets AI assistants such as Claude and ChatGPT configure and automate Home Assistant. It is open source under the MIT licence, and the code is on GitHub at homeassistant-ai/ha-mcp.

The problem it solves

Home Assistant owners who want more than a few switches end up hand-building automations, scripts and dashboards, which takes time and care. The project's own example request is simply to create an automation that turns on the porch light at sunset.

The maintainers also admit the weak spot: without domain knowledge, agents tend to over-rely on templates. That is why the project pairs the server with agent skills.

What you get

  • Less hand-writing: the assistant can create and edit automations, scripts and scenes.
  • Dashboards too: it can build and edit them, not just control devices.
  • Debugging help: it analyses execution traces, identifies the issue and suggests fixes.
  • A wide toolbox: the README lists 87 tools.
  • Safety switches: a Read Only Mode toggle, per-tool enable and disable, approval policies and automatic edit backups.
  • Local by design: the project says your smart home data stays on your network.

How it compares

Home Assistant ships its own MCP server. According to the project's own comparison, that one only reaches entities exposed to Assist, while ha-mcp covers everything in Home Assistant. The project's rule of thumb is to use the built-in integration for voice-style control of devices you have already exposed, and ha-mcp when you want an assistant that can also build and maintain your setup.

The catches

  • Power: setup means deciding which administrator account the server acts as, so an AI client can change your home's configuration.
  • Maturity: the file and YAML tools require beta feature flags.
  • Transport: the project says stdio has known transport issues.
  • Setup: configure exactly one install method per client.
  • Privacy: the README says there is no telemetry today, but anonymous usage stats are a planned future feature.

What we did not test

We did not run HA-MCP, connect it to a Home Assistant instance or try any assistant. Every claim here comes from a literal quote in the project's README or the GitHub API, and the feature and comparison descriptions are the project's own.

Verdict

Editors' view: this is for Home Assistant users who already lean on an AI assistant and want it to do more than flip switches. If you only want voice control of a few devices, the built-in server may be enough. If you try it, start with Read Only Mode and keep backups.

Repository
homeassistant-ai/ha-mcp
Python · MIT
View on GitHub ↗

Sources

Need help adopting this, or have a software project in mind?

Tell us what you are building. The initial consultation is free. Email [email protected] or follow @zolnaltd.

Start a conversation →