Hass MCP Server
Home Assistant device control, automation troubleshooting, and dashboard editing.
Data last scanned today · Reviewed today
Overview
Hass MCP Server bridges your Home Assistant instance with AI assistants, enabling direct querying and control of smart home entities. It provides capabilities to read sensor states, toggle lights and switches, and manage automations through natural language conversations. Beyond basic control, the server supports advanced tasks like real-time Lovelace dashboard editing over WebSocket. It includes features for token-efficient JSON reporting and guided task assistance, allowing users to troubleshoot home configurations or modify UI cards directly via their AI interface.
Our verdict
With a security score of 45/100, this server carries a high risk level. The score reflects that it is a community-maintained project rather than an official vendor release, and critical aspects such as the authentication implementation and read-only mode safety have not been editorially reviewed. It is suitable for enthusiasts comfortable with self-hosting experimental integrations, but should be avoided in environments where strict security boundaries are required.
- Zero direct dependencies minimize the software supply-chain surface
- Active development with commits within the last 30 days
- Includes live dashboard editing via WebSocket API
- Lacks an official maintenance status from Home Assistant
- Authentication mechanism has not undergone security review
- Safety of read-only mode operations remains unverified
Tools
| Tool | Description | Risk |
|---|---|---|
| get_version | Get the Home Assistant version | low |
| get_entity | Get the state of a specific entity with optional field filtering | low |
| entity_action | Perform actions on entities (turn on, off, toggle) | medium |
| list_entities | Get a list of entities with optional domain filtering and search | low |
| search_entities_tool | Search for entities matching a query | low |
| domain_summary_tool | Get a summary of a domain's entities | low |
| list_automations | Get a list of all automations | low |
| call_service_tool | Call any Home Assistant service | medium |
| restart_ha | Restart Home Assistant | high |
| get_history | Get the state history of an entity (last N hours) | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What are the core requirements to set up the Hass-MCP server?
You need a Home Assistant instance with a valid Long-Lived Access Token, and either Docker or Python 3.13+ with uv installed.
›How do I configure network access if Home Assistant runs in Docker on the same machine?
You may need to add --network host to your Docker arguments, or use your machine's IP address instead of host.docker.internal to allow the container to reach the Home Assistant instance.
›Can I use this server with clients other than Claude Desktop?
Yes, it supports Cursor and the Claude Code CLI, as well as environments requiring HTTP transport like MCP gateways, LibreChat, or OpenWebUI.
›Does this server support read and write operations for Home Assistant?
Yes, it allows you to query states, control devices and automations, and even perform live edits to Lovelace dashboards.
›What measures are taken to keep token usage low?
The server is designed to provide lean JSON responses to help minimize token consumption during your interactions.
Alternatives
Changelog
Badge
Maintain this server? Add the live badge to your README.