A side-by-side look at the Home Assistant MCP and Homey MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Home Assistant MCP for home automation work as a local process; choose Homey MCP for home automation as a local process. You can also run both side by side in one mcpServers block.
ha_get_config, ha_list_entities, ha_get_state.list_devices, get_device, search_devices.Rows where the two servers differ are marked.
| Spec | H Home Assistant MCP | |
|---|---|---|
| Category | Home Automation | Home Automation |
| Quality signal | 56/100 · Good | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 80 | 60 |
| Full listing | View Home Assistant MCP | View Homey MCP |
ha_get_configCore config: version, location, time zone, loaded components.ha_list_entitiesList entities (filter by domain, free-text search, area).ha_get_stateFull state + attributes for one or more entities.ha_get_historyHistorical state changes over a time window. Given only a start time, it runs up to now (Home Assistant alone stops 24 hours after the start); `ha_get_logbook` does the same.ha_list_servicesAvailable services (and their fields for a given domain).ha_list_areasAreas (rooms/zones).ha_list_devicesDevice registry (filter by area / search).ha_get_entity_registryRegistry metadata: platform, area, device, disabled/hidden.ha_render_templateRender a Jinja2 template against live state.ha_list_helpersList stored helpers (input_boolean, input_number, counter, timer, …).ha_list_automationsAutomations with entity_id, unique id, state, last-triggered.ha_get_automationFull automation config (triggers/conditions/actions).list_devicesList devices with live capability values, filter by zone or classget_deviceGet full device details and all capability values by IDsearch_devicesSearch devices by name, class, or capabilityset_device_capabilityControl a device (onoff, dim, target_temperature, volume_set, etc.)rename_deviceRename a devicemove_device_to_zoneMove a device to a different zone (room)create_zoneCreate a new zone, optionally nested under a parentlist_zonesList all zones (rooms/areas) with their hierarchylist_flowsList simple and advanced flows with enabled/broken statustrigger_flowRun a flow immediatelyset_flow_enabledEnable or disable a flowget_flowGet a standard WHEN/AND/THEN flow definition by IDPaste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"home-assistant-mcp-2": {
"command": "npx",
"args": [
"-y",
"@vortitron/home-assistant-mcp"
]
}
}
}
{
"mcpServers": {
"homey-mcp": {
"command": "npx",
"args": [
"-y",
"homey"
]
}
}
}