R135 · Agent principles and patterns › Agent interaction protocols

ha-mcp: an MCP server that lets an assistant edit a live smart home, and its safety defaults

Read the original

mcpphysical-systemsagent-permissionsopen-source

Source: github.com/homeassistant-ai/ha-mcp (MIT, about 7.9k stars as of 2026-11-18); highlighted by André Lindenberg on LinkedIn (2026-11-17).

What it does

ha-mcp is an MCP server that gives Claude, ChatGPT and other MCP clients about 86 tools across Home Assistant: fuzzy entity search and config search, service calls and bulk device control, real-time states, automations, scripts, helpers, dashboards, areas, zones, calendars and blueprints, history and statistics, camera snapshots, automation traces, and backup, restore and updates. The flagship example is debugging: tell the assistant a motion-sensor automation isn't working and it reads the automation's execution trace, finds the failing step and edits it.

Deployment options

Safety model

The defaults lean toward capability: an admin-level credential, approvals off, and a secret URL as the default credential for remote access. That suits a hobbyist's own home. A shared or critical deployment needs to tighten them.

Why it is interesting beyond smart homes

It is a mature, heavily used example of an agent with write access to a physical system, and it shows which controls a real project converged on: snapshots before edits, read-only and per-tool switches, opt-in for the most dangerous file-level tools, and traces as the debugging substrate. Reading execution traces before editing is the same diagnose-then-change discipline that works for agents on any production system.

Risks and failure modes

Review checklist for an agent with write access to physical systems

Connections

See R135 on the knowledge map

Part of the Research notes on nowucca.com. Figures and claims are the source's own unless the summary says otherwise.