Practical overview
When it fits
Use Ha MCP when an AI client needs a tool connection to a Home Assistant instance for device control, state queries, service calls or automation management.
Who it is for
- Home Assistant users who want to use an AI assistant to interact with smart-home devices and automations.
- Developers connecting MCP-compatible AI clients to Home Assistant tools.
Documented uses
- Query Home Assistant entity states through an AI assistant.
- Control smart-home devices using natural-language requests.
- Invoke Home Assistant services from an AI client.
- Manage Home Assistant automations through exposed tools.
Requirements & limits
The recommended in-process server is installed in Home Assistant through HACS or by copying the component into the configuration directory. The project also documents an app (add-on) for Home Assistant OS and Supervised installations.
- The custom component is documented for Home Assistant OS, Supervised, Container and Core; the app (add-on) method is documented for OS and Supervised.
- Choose webhook access for remote clients when Home Assistant is reachable through Nabu Casa or an existing reverse proxy; same-network clients can use the direct connection.
- Only one installation method should run at a time.
- File and YAML editing tools are opt-in and require a separate File & YAML services entry.
- The repository specifies an MIT license and Python as the primary language.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install Ha MCP as a Home Assistant custom component
Set up the in-process MCP server and obtain its client connection URL.
Before you start
- A Home Assistant installation; this method is documented for OS, Supervised, Container and Core.
- HACS, or access to copy the component into Home Assistant's custom_components directory.
- An AI client that can connect to the server.
Steps
Install the HA-MCP Custom Component through HACS, adding the project's custom repository if needed; alternatively, copy custom_components/ha_mcp_tools/ into Home Assistant's config/custom_components directory.
Restart Home Assistant.
In Settings → Devices & Services, add the HA-MCP Custom Component integration and choose HA-MCP Server; submitting creates the entry and starts the server.
Open the entry's Configure screen, copy the connection URL and paste it into the AI client.
Expected outcome
The in-process server is started and its connection URL is available for an AI client.
Guide limitations
- Run only one installation method at a time; the in-process server replaces the app, Docker and uvx/PyPI stdio methods.
- Remote webhook access uses a Home Assistant domain through Nabu Casa or an existing reverse proxy. Same-network clients can use the direct server address.
- File and YAML editing tools require a separate entry and are opt-in.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 7 October 2026
- Original website title
- homeassistant-ai/ha-mcp · Official homepage title · retained in its source language

