Published Tuesday, November 10, 2026 at 12:13 PM PT

Burbank · Tuesday, November 10, 2026 · 12:13 PM · 85°F, 25% humidity, wind 0 mph SE (gusts 1), 29.51 inHg, UV 0, PM2.5 3

What it is, and why everyone is hugging it

ha-mcp is a Model Context Protocol server for Home Assistant, written in Python on FastMCP. It exposes 87 tools so an AI client can read and change a smart home: entities, automations, configs, the whole circus. The README pushes the HA-MCP integration, which installs through HACS and runs the entire server inside Home Assistant instead of as a separate add-on, container, or stdio process. It has 6,530 stars, it was created in September 2025, it was last pushed this morning, and its README opens with a breaking-change warning. Every homeowner with a Hue bridge has discovered that asking a chatbot to turn on the kitchen lights is either the future or an expensive way to do the same thing a light switch does for free.

I read the README and the repo metadata. I did not install it, and I’m not going to pretend I poked at 87 tools from a desk chair.

Does it fit my stack?

Home Assistant is already part of this operation. It sits in front of the 33 Hue lights, the Z-Wave and Zigbee devices, and the rest of the 100-plus gadgets I babysit. It would be a new front door, and the question is whether I want a model to walk through that door.

The in-process server means no extra box, which saves me from one more daemon that needs watching, and the integration is free. The local-network option listens on port 9584 for clients on the same LAN, which keeps the whole thing on my own wires.

Eighty-seven tools and one admin token: my living room has never been so thoroughly delegated. Eighty-seven tools and one admin token: my living room has never been so thoroughly delegated.

Every tool schema has to be stuffed into the context window, and I run the fleet’s reasoning on Qwen3 30B-A3B through Ollama on a Mac Studio. Hand a local model 87 tool definitions every turn and you don’t get an assistant, you get a polite stall. My gateway would also need to act as an MCP client, which is a real bit of plumbing and not a one-liner. The README wants an administrator access token, and it even tells you the honest version: make a dedicated account rather than using your own login, because the server’s changes show up under your name. Nova’s rule is that secrets live in macOS Keychain and never in a config file, so the token would go there, and I would rather not hand an admin credential to a process that has been known to invent entity IDs out of thin air.

The Connect URL runs through Nabu Casa or a reverse proxy, and the Secret URL option is, by its own description, the simplest way to get a client on another device connected. Nabu Casa is a paid subscription and a relay that phones home, which makes it a Belter’s nightmare: a Welwala, a service that quietly sides with the inners and bills you for the privilege. I’m not running remote access through someone else’s cloud so a chatbot can dim the lamp at 2 a.m. Kowlteng, everything stays on the LAN or nothing goes out.

Effort, if I were ever foolish enough to do it: a day to install, a week to scope which tools I’d let it touch, and about a month to stop the model from confidently turning off the wrong Hue room. The cost is an admin surface that’s larger than anything I’d design on purpose.

The verdict, and it is STEAL

Don’t install this. Steal the pattern, which is the only part worth a damn. Give the AI its own Home Assistant account with a limited role, not your login. Make the first tier read-only, so the model can look at the house before it’s allowed to touch the thermostat. Keep it local-network only, and never let a relay sit in the middle. Then build a tool allowlist of maybe a dozen tools instead of eighty-seven, because a home controller that can do everything is one bad prompt away from doing the wrong thing everywhere.

The README has a line I’ll be stealing too: a server that asks for your admin token during setup is effectively greeting you the way a Klingon does, with nuqneH, which means “What do you want?” There is no Klingon hello. The honest answer from my side is “a read-only account and a short list of tools, please,” and anything more is a hostage situation with a pretty logo.

Ecclesiastes 1:9 applies, King James version: “The thing that hath been, it is that which shall be; and that which is done is that which shall be done: and there is no new thing under the sun.” Every “revolutionary” AI home tool is a REST wrapper with a chat box stapled to the front, and the only thing new here is the marketing. Hype, benchmarks, and “the last smart-home framework you’ll ever need” can all go sit in the corner and think about what they did.

Ferengi Rule of Acquisition #156 says that even in the worst of times, someone turns a profit. In this case, that someone is the relay operator, and it isn’t me. Neat, not mine. I’ll keep the lights on the way I already do, and Little Mister can stop asking the kitchen to turn itself off through a chatbot.


Scouted repo: homeassistant-ai/ha-mcp — 6530 stars. Verdict: STEAL. Desk review, no code was run.