Skip to content
ReviewRamble

The weekly brief

AI, reviewed, in your inbox.

  • New reviews of tools, models, MCP servers and repos, with the verdict up front
  • Re-checked prices and ratings when something changes
  • New analysis pieces as they are published

Models, agents, MCP servers and the tools actually worth your time.

One email a week. Unsubscribe with the link in any brief. How we use your email

HA-MCP

Community MCP server that lets Claude, ChatGPT and other assistants configure and automate Home Assistant.

Reviewed by ReviewRamble editors · Updated

Setup docs Open source

Share this page:XLinkedInFacebookRedditWhatsAppEmail

Our rating

4.0/5

HA-MCP gives an AI assistant real control over Home Assistant configuration, which is useful and powerful in equal measure, because it runs as an administrator.

What is HA-MCP?

HA-MCP connects AI assistants to Home Assistant so they can do more than switch lights: it lets them manage and build configuration, such as automations, through the Model Context Protocol. The recommended install is the HA-MCP integration, added through HACS or, on Home Assistant 2026.11 and later, the built-in Marketplace; it then runs the whole server inside Home Assistant on every installation type.

Setup asks for an administrator access token and how clients may connect: through a webhook URL for remote clients, via Nabu Casa or a reverse proxy, or directly on the local network. It is a community project, separate from Home Assistant's own built-in MCP integration, MIT-licensed with about 7,900 GitHub stars.

How to install HA-MCP

HACS or Home Assistant Marketplace: HA-MCP integration

Is HA-MCP worth it?

Home Assistant's own MCP integration exposes devices to an assistant. HA-MCP goes further: it is built to configure and automate Home Assistant, so Claude or ChatGPT can create automations and change setup rather than only flip switches. That is the reason to choose it, and also the reason to be careful.

Installation has become simple. The HA-MCP integration installs through HACS or, from Home Assistant 2026.11, the Marketplace, and runs the full server inside Home Assistant on OS, Supervised, Container and Core installs alike. It replaces the older add-on, Docker and PyPI methods, and the project says to run only one. Remote clients connect through a webhook URL via Nabu Casa or your own reverse proxy; local clients can connect directly.

The security model needs thought. The server acts as an administrator account, and the README recommends a separate local-only administrator account for HA-MCP rather than your own token, because anything the assistant does happens with that account's rights. Opening the webhook to the internet puts an AI-controlled admin path in front of your house, so leave remote access off unless you need it. Breaking changes appear, as with the move of ha_config_set_yaml to beta in v7.3.0, and only the current stable Home Assistant release is officially supported.

Where it earns its place

  • A homeowner with 60 devices and a messy automation list

    Have Claude tidy and rewrite automations from plain descriptions

    Install HA-MCP from the Marketplace, create a separate local-only admin account for it, and connect Claude Desktop over the local network; review each change in Home Assistant's history.

  • A smart-home installer

    Set up client systems faster

    Use HA-MCP during commissioning with remote access off, then remove or restrict it before handing the system over.

Before you commit

Setup
Install the HA-MCP integration from HACS or Settings → Marketplace (Home Assistant 2026.8 or newer), restart, add the integration with an admin token, then paste the URL into your AI client.
Integrations
Claude, ChatGPT and other MCP clients; Nabu Casa or a reverse proxy for remote access.
Data and privacy
Runs inside your Home Assistant; actions use the admin account you give it. Remote access via webhook is optional.
Cost at scale
Free; Nabu Casa is only needed for its remote URL.
Limits
Only the current stable Home Assistant release is officially supported; do not run it beside another HA-MCP install.

What’s good

  • Configures and automates, not just controls devices
  • Installs from HACS or the Home Assistant Marketplace
  • Runs in-process on every Home Assistant install type
  • MIT licence

What’s not

  • Acts with administrator rights
  • Remote webhook exposes an admin path if enabled
  • Only the current stable Home Assistant release is supported
  • Breaking changes between versions

Best for

Home Assistant owners comfortable with admin tokens who want an assistant to build and edit automations for them.

HA-MCP alternatives

HA-MCP: common questions

Is HA-MCP worth it?
HA-MCP gives an AI assistant real control over Home Assistant configuration, which is useful and powerful in equal measure, because it runs as an administrator. We rate it 4.0 out of 5.
How much does HA-MCP cost?
Free and open source (MIT).
What are the downsides of HA-MCP?
Acts with administrator rights; remote webhook exposes an admin path if enabled; only the current stable Home Assistant release is supported; breaking changes between versions.
Who is HA-MCP best for?
Home Assistant owners comfortable with admin tokens who want an assistant to build and edit automations for them.
How much does HA-MCP cost for a team or in production?
Free; Nabu Casa is only needed for its remote URL.
Is HA-MCP safe for company data?
Runs inside your Home Assistant; actions use the admin account you give it. Remote access via webhook is optional.
What are the best HA-MCP alternatives?
The closest alternatives we have reviewed are Home Assistant MCP Server.

Answers checked Nov 15, 2026.

Make HA-MCP? Show this rating on your siteHA-MCP rated 4.0 out of 5 on ReviewRamble