Home Assistant's built-in MCP integration lets AI clients read and control devices exposed to Assist. The open-source ha-mcp project broadens that connection to automation authoring, dashboard editing, trace analysis, registry management, and selected system operations. Its GitHub repository has 5.4k stars. The broader API lets an agent carry a task from diagnosis through an approved configuration change.
Model Context Protocol, or MCP, lets an AI client discover and invoke tools described by machine-readable schemas. ha-mcp sits between the client and a Home Assistant instance, exposing 87 tools across search, control, management, monitoring, system, and safety categories. The catalog covers:
- Building: automations, scripts, scenes, blueprints, helpers, and dashboards.
- Organizing: areas, zones, labels, calendars, and the device and entity registries.
- Diagnosing: logs, execution traces, history, camera snapshots, and backups.
- Administering: HACS, Z-Wave radios, Matter fabrics, and selected configuration files.
Home Assistant's built-in server routes requests through the Assist pipeline, which limits clients to exposed entities and supported intents. ha-mcp adds administrative workflows governed by its enabled tools, credentials, connection mode, and security policies.
Four routes to a running server
The maintainers recommend the HA-MCP Custom Component for access to the complete tool set. It installs through HACS, runs inside Home Assistant, and supports Home Assistant OS, Supervised, Container, and Core installations.