Best for
- Users wanting deep AI integration with smart home
- Privacy-conscious users needing local voice control
- Developers looking for multiple deployment options (STDIO, HTTP, Docker)
- Enthusiasts exploring AI-driven automation
The project offers rich features and an active community, but requires users to have some Home Assistant knowledge. Overall positive reviews, but be mindful of permissions and security configuration.
Strongest · Documentation 14/20 Weakest · Reliability 8/20
Static review · not runListed 2026-08-07
Read the FMRS scoring method →Runtime:Node.js 18+ · Bun · Docker
HASS_HOST
URL of your Home Assistant instance (e.g. http://homeassistant.local:8123); required.
HASS_TOKEN
Long-lived access token created from your Home Assistant account profile page; required and secret.
JWT_SECRET
JWT auth secret for the HTTP/WS transport (min 32 chars); secret and optional.
PORT
HTTP server port (default 4000); optional, only for HTTP transports.
LOG_LEVEL
Log level (debug | info | warn | error); optional.
{
"mcpServers": {
"homeassistant-mcp": {
"command": "bunx",
"args": [
"github:jango-blockchained/advanced-homeassistant-mcp"
],
"env": {
"HASS_HOST": "http://your-ha-instance:8123",
"HASS_TOKEN": "your_long_lived_access_token"
}
}
}
}
Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.
{
"servers": {
"homeassistant-mcp": {
"command": "bunx",
"args": [
"github:jango-blockchained/advanced-homeassistant-mcp"
],
"env": {
"HASS_HOST": "http://your-ha-instance:8123",
"HASS_TOKEN": "your_long_lived_access_token"
}
}
}
}
Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).
claude mcp add homeassistant-mcp -e HASS_HOST=http://your-ha-instance:8123 -e HASS_TOKEN=your_long_lived_access_token -- bunx github:jango-blockchained/advanced-homeassistant-mcp
Run it in a terminal; replace any <…> placeholders with your own values first.
Add the bunx config to claude_desktop_config. and restart Claude; the tool list should show the 50+ tools such as lights, climate and locks. Ask "What's the temperature in the living room?" — a real entity state in the answer confirms the connection works.
Once connected, you can ask your AI assistant things like:
No matching tools
Listed from the project's documentation, not tested by this site.
Home Assistant MCP is a Model Context Protocol server that gives AI assistants (like Claude, GPT, Cursor, Copilot) control over your Home Assistant instance. It exposes 50+ tools covering lights, climate, media, locks, covers, fans, vacuums, alarms, scenes, automations, notifications, history, energy monitoring, maintenance, and more. Supports STDIO, HTTP+WS, and HTTP transports. Can be installed via bunx, npx, Docker, or from source. Includes optional speech features (wake word detection and speech-to-text) for local voice control.
Manage your Hevy workout data from AI assistants via MCP.
Firecrawl's official MCP server for web search, scraping, and structured extraction for AI agents
One binary. One grammar. Evidence from the biomedical sources you already trust.
Encrypted, fully offline long-term memory for AI agents
Source revision b1aa766ab6c7 Data synced 2026-10-12 Read the FMRS scoring method