Home Assistant MCP vs Rachio MCP
A side-by-side look at the Home Assistant MCP and Rachio MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
H
Home Assistant MCPHome Automation · Local subprocess (stdio)Home Assistant and ESPHome for coding agents: states, services, automations, dashboards, flashing.56GoodAuth: not declaredVerdict: choose Home Assistant MCP for home automation work as a local process; choose Rachio MCP for home automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
HChoose Home Assistant MCP when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
ha_get_config, ha_list_entities, ha_get_state.
Choose Rachio MCP when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
RACHIO_ACCESS_TOKEN. - You want tools like
list_devices, get_device, list_zones.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | H Home Assistant MCP | |
|---|---|---|
| Category | Home Automation | Home Automation |
| Quality signal | 56/100 · Good | 52/100 · Good |
| 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 | RACHIO_ACCESS_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 7 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 80 | 24 |
| Full listing | View Home Assistant MCP | View Rachio MCP |
Tools & capabilities
Home Assistant MCP tools 80
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).- +68 more on the listing page
Rachio MCP tools 24
list_devicesEvery device on the account — controllers, sensors, weather stationsget_deviceFull details + live state for a single devicelist_zonesZones configured on a controller, with agronomic metadataget_zoneFull detail for a single zoneget_calendarScheduled runs + skip events for a date rangeget_run_historyObserved recent/past zone-run telemetry plus calendar contextget_active_alertsUnresolved alerts on a device or zoneget_weatherObserved + forecast weather readings for a locationlist_schedulesFilter by device, location, zone, or schedule idget_scheduleSingle schedule + its locations/devicespreview_scheduleDry-run** — returns the Schedule that `create_schedule` would produce, including the server-generated human-readable summary. Never persistscreate_scheduleCreate a new schedule- +12 more on the listing page
Ready-to-paste client configs
Paste 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.
Home Assistant MCP
{
"mcpServers": {
"home-assistant-mcp-2": {
"command": "npx",
"args": [
"-y",
"@vortitron/home-assistant-mcp"
]
}
}
}
Rachio MCP
{
"mcpServers": {
"rachio-mcp": {
"command": "uvx",
"args": [
"--from",
"rachio-mcp",
"rachio-mcp-token"
],
"env": {
"RACHIO_ACCESS_TOKEN": "YOUR_RACHIO_ACCESS_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Home Assistant MCP is categorized under Home Automation and uses a local stdio subprocess. Rachio MCP belongs to Home Automation and uses a local stdio subprocess. Pick Home Assistant MCP for home automation work and Rachio MCP for home automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Home Assistant MCP has no declared pricing — check the project's own site. Rachio MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add home-assistant-mcp-2 and rachio-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Home Assistant MCP has a quality signal of 56/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Rachio MCP has 52/100 (Good) with 1 views, 0 installs and 7 GitHub stars.