In-depth architectural comparison of the Homeassistant MCP and Home Assistant MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Homeassistant MCP
Home Automation · Local stdio
Quality: 40/100 (Fair) | Auth: API Key required
Home Assistant
Home Automation · Remote HTTP/SSE
Quality: 68/100 (Great) | Auth: OAuth 2.0
Verdict Summary: Choose Homeassistant MCP if you need specialized Home Automation tools running via a local process. Choose Home Assistant if your workspace requires Home Automation integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Homeassistant MCP when:
You need dedicated capabilities in the Home Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: HASS_HOST, HASS_TOKEN, HASS_SOCKET_URL.
Primary tools included: Home Assistant device control, Entity state monitoring, Automation creation and management.
Access Home Assistant data and control devices (lights, switches, thermostats, etc).
Homeway’s remote MCP server gives your favorite AI the power to understand, control, and customize your Home Assistant home from anywhere. Explore your home’s layout, live states, history, and camera snapshots; control devices; build dashboards, automations, scripts, scenes, blueprints, and themes; manage integrations, add-ons, backups, and configuration files; and troubleshoot with logs, templates, and Home Assistant APIs. Free, private, and easy to set up, Homeway puts you in control with granular AI permissions and no public exposure of your Home Assistant server.
Tools & Capabilities Breakdown
Homeassistant MCP Tools (6)
Home Assistant device control
Entity state monitoring
Automation creation and management
Add-on and HACS package management
Server-Sent Events subscriptions
Token-based authentication and rate limiting
Home Assistant Tools (6)
Remote MCP access to Home Assistant
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Homeassistant MCP is categorized under Home Automation and uses a local stdio subprocess. In contrast, Home Assistant belongs to Home Automation using remote streaming HTTP/SSE transport. Select Homeassistant MCP when you need capabilities focused on home automation and Home Assistant when you require tools for home automation.