Home Assistant vs MCP Homeassistant
A side-by-side look at the Home Assistant and MCP Homeassistant 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 for home automation work over a hosted endpoint; choose MCP Homeassistant 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?
Choose Home Assistant when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Choose MCP Homeassistant when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
HA_URL, HA_TOKEN. - You want tools like
get_api_status, get_config, get_components.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Home Automation | Home Automation |
| Quality signal | 73/100 · Great | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | HA_URLHA_TOKEN |
| Verified owner | Verified | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 2 views 0 installs 1 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 19 |
| Full listing | View Home Assistant | View MCP Homeassistant |
Tools & capabilities
Home Assistant tools
No tool names declared yet. Check the project README from the listing page.
MCP Homeassistant tools 19
get_api_statusCheck if the API is runningget_configGet HA configurationget_componentsList loaded componentsget_eventsList event types and listener countsget_servicesList available services by domainget_statesGet all entity statesget_stateGet a specific entity stateset_stateUpdate or create an entity statedelete_stateDelete an entity statefire_eventFire a custom eventcall_serviceCall a Home Assistant servicerender_templateRender a Jinja template- +7 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
{
"mcpServers": {
"home-assistant": {
"url": "https://homeway.io/mcp"
}
}
}
MCP Homeassistant
{
"mcpServers": {
"mcp-homeassistant": {
"command": "uvx",
"args": [
"mcp-homeassistant"
],
"env": {
"HA_URL": "YOUR_HA_URL_HERE",
"HA_TOKEN": "YOUR_HA_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Home Assistant is categorized under Home Automation and uses a remote HTTP/SSE transport. MCP Homeassistant belongs to Home Automation and uses a local stdio subprocess. Pick Home Assistant for home automation work and MCP Homeassistant 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 is listed as free. Auth: oauth 2.0. MCP Homeassistant 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 and mcp-homeassistant as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Home Assistant has a quality signal of 73/100 (Great) with 2 views, 0 installs and 0 GitHub stars. MCP Homeassistant has 47/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.