Integrates with Home Assistant to provide smart home control capabilities via Model Context Protocol (MCP).
If you already use Home Assistant, the home assistant mcp server is the piece that lets your assistant work with it directly. Integrates with Home Assistant to provide smart home control capabilities via Model Context Protocol (MCP).
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Prompts — The Prompts tool exposed by this serverTools — The server implements control for various Home Assistant domains. Currently supports: - 💡 Lights: Turn on/off, brightness control - 🌡️ ClimateDebugging — Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the [MCPConfiguration is passed through the environment: HOMEASSISTANT_TOKEN, HOMEASSISTANT_BASE_URL, UV_PUBLISH_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as @modelcontextprotocol/inspector, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Home Assistant's toolset — Prompts, Tools, Debugging — is a fair guide to whether it matches your workflow. It is maintained by miguelg719; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Home Assistant's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Prompts | The Prompts tool exposed by this server. |
| Tools | The server implements control for various Home Assistant domains. Currently supports: - 💡 Lights: Turn on/off, brightness control - 🌡️ Climate: Temperature control, HVAC modes - 🔒 Locks: Lock/unlock functionality - 🚨 |
| Debugging | Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector). |
"mcpServers": {
"home-assistant-server": {
"command": "uv",
"args": [
"--directory",
"/path/to/home-assistant-server",
"run",
"home-assistant-server"
]
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| HOMEASSISTANT_TOKEN | Credential the server authenticates with. | Yes |
| HOMEASSISTANT_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| UV_PUBLISH_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.