Hass-MCP
MCP server for Home Assistant: an agent reads device states, controls them and edits smart home dashboards
- 352 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Controls real home devices, including lights, appliances and locks
- Can restart Home Assistant and call any of its services
- Edits dashboards and handles a long-lived access token
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/hass-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Controls real home devices, including lights, appliances and locks
- Can restart Home Assistant and call any of its services
- Edits dashboards and handles a long-lived access token
This is third-party code. Review the repository files before installing.
What it does
The server links an agent to your Home Assistant instance. It reads device and sensor states, searches entities, turns lights and appliances on and off, calls any service and restarts Home Assistant. It offers entity history and long-term statistics, error log reading and live Lovelace dashboard editing over WebSocket with automatic backups. It ships with guided prompts for creating and debugging automations.
Who it is for. For Home Assistant smart home owners who want to control and configure it through an agent.
Good fit when
- You want to ask about device and sensor states at home
- You want to turn appliances on, off or toggle by voice or text
- You want to review automations, history or Home Assistant dashboards
Not a fit when
- You have no Home Assistant instance with a long-lived token
- You cannot trust the client with full control over your home and devices
Example request
What is the bedroom temperature, and turn off the kitchen lightsMCP
- Transport
- stdio, http
- Authentication
- API key
Environment variables
HA_URLrequired- URL of your Home Assistant instance
HA_TOKENrequired, secret- Home Assistant long-lived access token
SSL_CERT_FILE- Path to your own CA root certificate
Limitations
You need a Home Assistant instance with a long-lived token, and to edit Lovelace dashboards the token must belong to an admin and work only with UI storage-mode dashboards. It runs from the voska/hass-mcp Docker image or via uvx with the hass-mcp package; Python 3.13 and uv are required. The http mode exposes full home control over the network without built-in auth, so it must not face the internet without a reverse proxy or VPN.
How to disable. Remove the hass-mcp block from your MCP client config and restart it. If running in Docker, stop and remove the container, and revoke the long-lived token in Home Assistant if needed.
FAQ
Which token is needed?
A long-lived access token from your Home Assistant profile. To edit Lovelace dashboards the token must belong to an admin.
Is http mode safe?
It exposes full home control over the network without built-in auth. Put it behind a reverse proxy, a VPN or a localhost-only binding and do not face it to the internet.
How is Hass-MCP different from Home Assistant voice assistants?
The server links the agent to your Home Assistant: it reads device and sensor state, searches entities, switches lights and appliances, calls any services, restarts Home Assistant and helps with dashboards.
What token does Hass-MCP need?
You need a Home Assistant long-lived access token, created in the user profile. Run uvx hass-mcp. It works with Claude Desktop, Cursor and Claude Code. Risk is high because the agent controls devices in your home.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server for Home Assistant: the agent reads smart-home state and controls devices through your instance
A Node.js MCP server through which an agent controls Home Assistant devices and edits its automations
Vibecode MCP lets Cursor, VS Code and Claude Code write Home Assistant automations and dashboards via an add-on agent
Home Assistant Vibecode Agent
home-assistant-vibecode-agent
A Home Assistant add-on and MCP server: an agent checks the configuration and applies automations. A long-lived token is needed. Not an official project
The Home Assistant integration exposes selected tools to Xiaozhi so its voice agent can control permitted devices.
An MCP server for driving Windows: the agent opens apps, clicks and types, reads window and UI state, and works with files and PowerShell
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Hass-MCP (this card) | no | API key | 352 | |
| kubectl-mcp-server | no | not required | 972 | reads cluster state and diagnoses pod failures |
| Unreal Engine MCP Server | no | not required | 1,033 | Unreal Engine assets, actors and blueprints |
| Android MCP | no | not required | 924 | controls an Android device through ADB |
README in short
The README covers installation via the voska/hass-mcp Docker image and via uvx with the hass-mcp package, plus setup for Claude Desktop, Cursor and Claude Code with the HA_URL and HA_TOKEN variables. It lists tools for entity state and search, entity actions, service calls, restart, history and statistics, the error log and live Lovelace dashboard editing with backups. It separately shows the streamable http transport with a security warning and custom CA setup. It includes guided prompts and resources, licensed under MIT.