H
homeassistant-ai/ha-mcp
Configure and automate Home Assistant with Claude, ChatGPT, and other AI assistants.
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
- Copy the command above
- Paste it as one entry under
mcpServersinclaude_desktop_config.json— local servers take command + args (example: clients) - Restart your client
Client config (built from the install command this repo gives)
{
"mcpServers": {
"homeassistant-ai-ha-mcp": {
"command": "uvx",
"args": ["ha-mcp@latest"]
}
}
}Parsed from the README we fetched on 2026-11-09; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"homeassistant-ai-ha-mcp": {
"command": "uvx",
"args": ["ha-mcp@latest"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio homeassistant-ai-ha-mcp -- uvx ha-mcp@latest
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 7,748 ★ · homeassistant-ai/ha-mcp · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: MCP server
- Harvest history
- first seen 2026-11-10 · last seen 2026-11-12 · seen 3× · listed by 1 sources
- Install
uvx ha-mcp@latest
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
uvx ha-mcp@latest. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We have no tags recorded for it yet.
Who maintains it?
repository
homeassistant-ai/ha-mcp；first catalogued 2026-11-10；last seen 2026-11-12。There is no official certification or quality rating here — we record sources and dates only.> Breaking change (v7.3.0): ha_config_set_yaml has been moved to beta.
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
# HA-MCP — Manage Home Assistant with AI
Configure and automate Home Assistant with Claude, ChatGPT, and other AI assistants.
## 🚀 Get Started
The recommended way to run ha-mcp is the HA-MCP integration. It installs into Home Assistant through HACS (the built-in Marketplace on Home Assistant 2026.11+), runs the full server in-process, and works on every Home Assistant installation type — Home Assistant OS, Supervised, Container, and Core — with full feature parity. It is the easiest setup in every case: setup asks for an administrator access token and how clients may connect.
Add it to Home Assistant via HACS or, on Home Assistant 2026.11+, the Marketplace (the preferred install):
Quick start:
> The setup below is for version 9.0.0 (October 28, 2026) and later; earlier versions show a shorter setup form without the administrator account step.
1. Install the HA-MCP integration (requires Home Assistant 2026.8.0 or newer; see compatibility details). On Home Assistant 2026.8–2026.10, open HACS, search for HA-MCP, then Download.
On Home Assistant 2026.11 or newer, open Settings → Marketplace, accept its first-run warning, and search for HA-MCP, then Install. HA-MCP is in the default catalog, so installing it and receiving its updates do not require connecting GitHub or adding a custom repository. The badge above also opens its catalog page.
Already installed from the earlier homeassistant-ai/ha-mcp-integration repository? It keeps receiving the same releases. On the Marketplace, keep GitHub connected for its background checks on that custom repository.
Older installed releases may still appear as HA-MCP Custom Component; searching for HA-MCP matches both names.
2. Restart Home Assistant.
3. Decide which administrator account the server acts as. Either create a long-lived access token on your own account (your profile → Security → Long-lived access tokens → Create token; it works from anywhere if it leaks, and the server's changes show under your name), or, safer, create an account just for HA-MCP under Settings → People → Add person with Allow login, Local access only and Administrator on. Never use your own login for the second option.
4. Go to Settings → Devices & Services → Add Integration, search for HA-MCP and choose HA-MCP Server. Paste your token, or enter the user name and password of the account you made for HA-MCP (HA-MCP creates its token), pick how clients may connect — Remote access through Home Assistant (start with Secret URL, the simplest; Home Assistant sign-in adds a login) and/or Network access: Local network — then click Submit. Both start disabled, so a client on another device needs one of them.
5. Copy the connect URL from the entry's Configure screen (Settings → Devices & Services → “HA-MCP — Manage Home Assistant with AI” → HA-MCP Server → Configure). A notification confirms the server started and points you there.
6. Paste that URL into your AI client — done.
Connect URL. The Configure screen gives you a Home Assistant webhook URL for remote clients — https:// /api/webhook/ through Nabu Casa or any reverse proxy already pointed at Home Assistant (locally, http:// :8123/api/webhook/ ). For clients on the same network, the server is also reachable directly at http:// :9584/private_ .
Configure and automate Home Assistant with Claude, ChatGPT, and other AI assistants.
## 🚀 Get Started
The recommended way to run ha-mcp is the HA-MCP integration. It installs into Home Assistant through HACS (the built-in Marketplace on Home Assistant 2026.11+), runs the full server in-process, and works on every Home Assistant installation type — Home Assistant OS, Supervised, Container, and Core — with full feature parity. It is the easiest setup in every case: setup asks for an administrator access token and how clients may connect.
Add it to Home Assistant via HACS or, on Home Assistant 2026.11+, the Marketplace (the preferred install):
Quick start:
> The setup below is for version 9.0.0 (October 28, 2026) and later; earlier versions show a shorter setup form without the administrator account step.
1. Install the HA-MCP integration (requires Home Assistant 2026.8.0 or newer; see compatibility details). On Home Assistant 2026.8–2026.10, open HACS, search for HA-MCP, then Download.
On Home Assistant 2026.11 or newer, open Settings → Marketplace, accept its first-run warning, and search for HA-MCP, then Install. HA-MCP is in the default catalog, so installing it and receiving its updates do not require connecting GitHub or adding a custom repository. The badge above also opens its catalog page.
Already installed from the earlier homeassistant-ai/ha-mcp-integration repository? It keeps receiving the same releases. On the Marketplace, keep GitHub connected for its background checks on that custom repository.
Older installed releases may still appear as HA-MCP Custom Component; searching for HA-MCP matches both names.
2. Restart Home Assistant.
3. Decide which administrator account the server acts as. Either create a long-lived access token on your own account (your profile → Security → Long-lived access tokens → Create token; it works from anywhere if it leaks, and the server's changes show under your name), or, safer, create an account just for HA-MCP under Settings → People → Add person with Allow login, Local access only and Administrator on. Never use your own login for the second option.
4. Go to Settings → Devices & Services → Add Integration, search for HA-MCP and choose HA-MCP Server. Paste your token, or enter the user name and password of the account you made for HA-MCP (HA-MCP creates its token), pick how clients may connect — Remote access through Home Assistant (start with Secret URL, the simplest; Home Assistant sign-in adds a login) and/or Network access: Local network — then click Submit. Both start disabled, so a client on another device needs one of them.
5. Copy the connect URL from the entry's Configure screen (Settings → Devices & Services → “HA-MCP — Manage Home Assistant with AI” → HA-MCP Server → Configure). A notification confirms the server started and points you there.
6. Paste that URL into your AI client — done.
Connect URL. The Configure screen gives you a Home Assistant webhook URL for remote clients — https:// /api/webhook/ through Nabu Casa or any reverse proxy already pointed at Home Assistant (locally, http:// :8123/api/webhook/ ). For clients on the same network, the server is also reachable directly at http:// :9584/private_ .
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/homeassistant-ai-ha-mcp/)
- Source
- github · https://github.com/homeassistant-ai/ha-mcp
- Traction
- 7,748 ★
- added
- 2d ago