Category · Smart home MCP servers
Home Assistant MCP Server: Control Your Smart Home with AI in 2026
The Home Assistant MCP server is a first-party integration that exposes your selected entities — lights, locks, climate, sensors, scenes and scripts — as callable tools for an AI assistant. Because Home Assistant already runs locally, this is one of the few MCP setups where the agent can act on real hardware without anything traversing a vendor cloud. This page covers what the integration exposes, how to scope it safely, and which servers pair well with it.
What this category covers
Home automation MCP servers let an assistant read state and call services in a smart home stack. Home Assistant ships its own MCP Server integration, which is the important detail: rather than a community wrapper around an API, it is maintained alongside the platform and respects the entity exposure settings you already configure for voice assistants — see our Home Assistant MCP server listing for the specifics. That gives you a natural security boundary — only entities you explicitly expose become visible to the agent. The practical uses are conversational control (turn off everything downstairs), diagnostics (which sensors have not reported in a day), and automation authoring, where an agent reads your existing entities and drafts YAML that references real entity IDs rather than invented ones.
Buying guide
Enable the MCP Server integration from within Home Assistant rather than installing a third-party wrapper — it is first-party, it respects your existing entity exposure settings, and it will not break on upgrade. Then be deliberate about exposure: start with lights, scenes and read-only sensors, and hold back locks, garage doors and anything with a safety implication until you have watched the agent work for a while. Pair with the Filesystem MCP server only if you want the agent editing configuration, and pair that with Git MCP so every change is recoverable. Add the Memory MCP server so the assistant retains your room names and device quirks instead of relearning them each session. For history-heavy questions, add a database server pointed at your recorder — the agent answering how long the heating ran last month needs SQL, not the entity API.
The Tools, Ranked
First-party integration exposing lights, locks, climate, sensors, scenes and scripts. Free, open source and entirely local — the only fully local smart home MCP server.
Scoped read and write access to your Home Assistant config directory, so an agent can edit automations.yaml directly.
Read commit history and file contents at any revision — the safety net when an agent edits smart home config.
Query the recorder database directly for long-term sensor history that the Home Assistant UI aggregates away.
The default Home Assistant recorder backend, queryable for history and statistics on smaller installs.
For installs that ship Home Assistant metrics into Prometheus, this gives the agent proper time-series analysis.
A knowledge-graph memory so the assistant remembers your room names, device quirks and household routines between sessions.
Lets the agent pull integration documentation while writing an automation, rather than guessing at service parameters.
Version-specific documentation lookups, useful because Home Assistant service schemas change between releases.
Manage the containers a typical Home Assistant stack runs alongside — Zigbee2MQTT, Mosquitto, Node-RED.
Triggers multi-step automations that reach outside the home, bridging Home Assistant events to external services.
Route household notifications somewhere people actually read, rather than the Home Assistant companion app.