Top home automation MCP servers

Home automation is a newer MCP category, but ha-mcp already has one of the highest scores in the entire index at 93.13. Home Assistant's existing community is the reason — thousands of developers were already looking for a way to connect AI agents to their smart home setups. MCP gave them the bridge.

ha-mcp: the clear leader

homeassistant-ai/ha-mcp sits at 93.13 — one of the highest scores in the home automation category and well above comparable community-built tools. The signals behind the score are strong across the board: 18 contributors, 1,190 stars, active issue management (204 closed against 36 open), and a March 2026 commit date.

The project is organized under the homeassistant-ai GitHub org rather than a single maintainer's account. That organizational structure contributes to the multi-contributor signal and suggests the project has distributed ownership — lower bus factor risk than a single-person project.

What it does: expose Home Assistant's entity registry, state machine, automation engine, and script runner to AI agents via MCP tools. An agent connected to ha-mcp can read all device states, turn lights on or off, change thermostat setpoints, trigger scenes and scripts, and query automations — all without a human using the HA dashboard. For home automation use cases where you want an agent to respond to natural language commands or monitor conditions, this is the starting point.

IDE integration: vibecode-agent

Coolver/home-assistant-vibecode-agent takes a different angle at 82.05. Rather than focusing on runtime device control, it's built for developers who work on their Home Assistant configuration inside an IDE.

The pitch: connect Cursor, VS Code, or Claude Code to your live Home Assistant instance and have an AI assist with writing and debugging automations, designing Lovelace dashboards, adjusting theme variables, and deploying configuration changes — all without leaving the editor. 482 stars and 6 contributors in a short time suggests the developer audience found it immediately useful.

The distinction between ha-mcp and vibecode-agent matters for use case selection. ha-mcp is for runtime agent control — you want an AI to operate your home. vibecode-agent is for development-time assistance — you want an AI to help you configure it. They're complementary.

OpenHAB: one dedicated server

deswong/Openhab-MCP is the only OpenHAB server in the index. At 57.16, it's a newer project (4 stars, no contributors beyond the author), but the freshness signal is strong — last committed March 13, 2026.

OpenHAB is a less common home automation platform than Home Assistant, but it has a loyal user base — particularly in Germany and enterprise/commercial smart building deployments. The server exposes the full OpenHAB v5+ REST API surface: Items, Things, Rules, Persistence history, and Semantic Tags. If you're running OpenHAB, this is your only current MCP option, and it's more complete than many early-stage tools.

Recommended picks

Best for Home Assistant control

homeassistant-ai/ha-mcp at 93.13. No competition in this category. Start here.

Best for Home Assistant development

Coolver/home-assistant-vibecode-agent at 82.05. Use alongside ha-mcp: one for building automations, one for running them.

Best for OpenHAB

deswong/Openhab-MCP at 57.16. Early-stage but comprehensive. The only option for OpenHAB users.

Go implementation

achetronic/hass-mcp at 52.03. If your deployment environment requires a Go binary over a Python process, this is the only Home Assistant MCP server built in Go. Remote server architecture makes it easy to run as a sidecar.