CommunityStale· 4mo★ 4.3by tevonsb

Home Assistant MCP

Controls Home Assistant devices (lights, switches, thermostats) and accesses automation state through long-lived access tokens.

View repo

Safety & Trust

Delv Safety Grade: C

Score 58/100 · assessed 2026-04-18

Maintainer45

Permissions65

Supply chain40

Transparency70

Incidents100

This community-maintained MCP server bridges Claude with Home Assistant smart home systems, enabling control of lights, switches, thermostats and other IoT devices. The maintainer 'tevonsb' appears to be a solo developer with limited public profile. Installation requires cloning and building from source rather than using a package registry, which increases supply chain risk. The server requires a long-lived Home Assistant access token with potentially broad permissions over your entire smart home. Permissions are moderately scoped to network calls to your Home Assistant instance, but the token itself may grant extensive device control. The repository is open source with reasonable documentation, though maintenance history and bus factor are concerns. No known security incidents, but the combination of smart home control and solo maintenance warrants careful token scoping.

Green flags

Open source repository with visible code for review
Scoped to Home Assistant API, not arbitrary network access
No known security incidents or malicious behaviour
Clear documentation of required environment variables

Red flags

Solo maintainer with limited public profile and unknown bus factor
Requires clone-and-build installation, no npm package distribution
Long-lived access token could grant broad smart home control
Network access to private home network via HA_URL

Permissions requested

Outbound networkPrivate networkAccess secretsIdentity read

Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Install

npm install && npm run build

Env vars needed: HA_URLHA_TOKEN

Review

This MCP server bridges Claude to your Home Assistant instance, letting you query device states and trigger actions through natural language. You authenticate with a long-lived access token, point it at your Home Assistant URL, and suddenly Claude can turn off your office lights or check if the front door is locked. The integration is straightforward: it exposes your HA entities as callable tools, so you can ask Claude to "set the living room thermostat to 20 degrees" and it translates that into the right API call. I'd reach for this when I want conversational control over home automation without building yet another custom dashboard. It's particularly good for complex queries that span multiple devices or conditions. Instead of tapping through the Home Assistant app, you can ask "which lights are on in the house?" and get a plain-English summary. The workflow I keep coming back to: asking Claude to orchestrate morning routines ("turn on the kitchen lights, set the thermostat to 21, and check if the coffee maker is on") without writing a single automation script. The quirks are mostly about scope. This doesn't create or modify Home Assistant automations, it just triggers them and reads state. If you want Claude to rewrite your YAML configs, you're out of luck. The tool list can get noisy if you have hundreds of entities, though in practice Claude handles it fine. You'll need to generate a long-lived token in Home Assistant, which means trusting your MCP setup with full access to your smart home. No granular permissions here. Don't bother if you're happy with your existing Home Assistant interface or if you don't already use Claude Desktop regularly. This isn't a replacement for the HA app, it's a conversational layer on top. Also skip it if your Home Assistant setup is still in the "tinkering with a single smart bulb" phase. The real value emerges when you have enough devices that remembering their exact names and states becomes a chore. For everyone else with a mature HA deployment and a Claude Desktop habit, this is a surprisingly useful quality-of-life improvement.

Verdict

Install this if you already live in Claude Desktop and have a Home Assistant setup worth talking to. The conversational interface beats tapping through menus for multi-device queries and ad-hoc control. Skip it if you're not a regular Claude user or if your smart home is still minimal.

Good at

Natural language queries beat navigating the Home Assistant UI for quick checks across multiple devices.
No custom automation scripts needed for one-off orchestration tasks.
Reads device state cleanly, so you can ask contextual questions like "what's running right now?"
Straightforward setup if you're already comfortable with Home Assistant tokens and MCP config.

Watch out

Requires a long-lived access token with full Home Assistant access, no granular permissions available.
Doesn't create or edit automations, only triggers existing ones and reads state.
Entity list can get overwhelming if you have a large Home Assistant deployment with hundreds of devices.
Limited to hosts that support MCP, so no mobile or web-based Claude access.

Use cases

smart home control
automation management
state queries
device orchestration

Getting started

1. Clone the repo and run `npm install && npm run build` to compile the server. 2. Generate a long-lived access token in Home Assistant (Profile > Security > Long-Lived Access Tokens). 3. Add the server to your Claude Desktop config with `HA_URL` set to your Home Assistant instance (e.g., `http://homeassistant.local:8123`) and `HA_TOKEN` set to your token. 4. Restart Claude Desktop and ask it to list your lights or check a device state to verify the connection. 5. Watch out for token security: this gives Claude full control over your smart home, so keep your config file permissions tight.

Works with

Claude DesktopClaude CodeCursor