Home Assistant Vibecode MCP
Vibecode MCP lets Cursor, VS Code and Claude Code write Home Assistant automations and dashboards via an add-on agent
- 58 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The agent key gives write access to the Home Assistant configuration: automations, scripts, dashboards and integrations
- A faulty automation can control real devices in the house
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/home-assistant-vibecode-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.
- The agent key gives write access to the Home Assistant configuration: automations, scripts, dashboards and integrations
- A faulty automation can control real devices in the house
This is third-party code. Review the repository files before installing.
What it does
Home Assistant Vibecode MCP is a server that runs on your computer next to the editor and talks to the HA Vibecode Agent installed in Home Assistant as an add-on. The agent lives inside Home Assistant and gives the AI access to the configuration, while the server passes it commands through a controlled API with no SSH. The assistant reads entities, automations and scripts, creates new automations, helpers and sensors, edits Lovelace dashboards and themes, analyzes logs and installs HACS integrations. Changes are deployed with automatic Git versioning, so any edit can be rolled back. The server runs from npm with `npx -y @coolver/home-assistant-mcp@latest`.
Who it is for. Home Assistant owners who build automations and dashboards in dialogue with an AI in Cursor, VS Code or Claude Code.
Good fit when
- Describe smart radiator control and get a set of automations, helpers and sensors for your TRVs
- Rework a Lovelace dashboard by rearranging cards and room layouts
- Analyze the Home Assistant log and find why an automation fails
- Install a HACS integration with one command
Not a fit when
- Home Assistant cannot take an add-on
- The editor runs on a device without Node.js 20
- Automations are written by hand in YAML with no AI involved
Example request
Connect to my Home Assistant, show all climate entities and build automations for the radiatorsMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
HA_AGENT_URLrequired- Address of the HA Vibecode Agent
HA_AGENT_KEYrequired, secret- Access key for the agent
Limitations
Node.js 20 or newer on the computer with the editor and the HA Vibecode Agent add-on in Home Assistant are required, where the agent issues an address and a key. The `HA_AGENT_URL` address and the `HA_AGENT_KEY` key go into the MCP configuration, and the key gives write access to the home configuration. After integration installs and configuration edits Home Assistant may need a restart. The project is run by one author and the server evolves together with the add-on, so agent and server versions must stay consistent.
How to disable. Remove the `home-assistant` entry from the MCP configuration and stop the HA Vibecode Agent add-on in Home Assistant settings.
FAQ
How do I connect the server?
Install the HA Vibecode Agent add-on from `https://github.com/Coolver/home-assistant-vibecode-agent`, open its web UI and copy the configuration from the Cursor or VS Code tab.
How is it different from other Home Assistant MCP servers?
Most run only on a local machine and reach Home Assistant over SSH and REST. Here an agent sits inside Home Assistant and the server talks to it through a controlled API.
Can changes be rolled back?
Yes, edits are deployed with automatic Git versioning, so the previous configuration state can be restored.
What does it do with dashboards and themes?
Creates and changes Lovelace dashboards, adds and rearranges cards, changes layouts and styles, and creates and edits themes.
Which Node.js version is enough?
Version 20 or newer, with LTS 24 recommended. Node.js goes on the computer with the editor and the Home Assistant server does not need it.
Discussion
No questions or reviews yet.
Related
MCP serversHome 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
A Node.js MCP server through which an agent controls Home Assistant devices and edits its automations
MCP server for Home Assistant: an agent reads device states, controls them and edits smart home dashboards
An MCP server for Home Assistant: the agent reads smart-home state and controls devices through your instance
An MCP server for macOS: the agent moves the mouse, types, manages windows and captures the screen when an app has no API
A Claude Code skill that edits and deploys Home Assistant configuration: YAML automations, validation, deploy and Lovelace dashboards
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Home Assistant Vibecode MCP (this card) | no | API key | 58 | |
| homeassistant-mcp | no | API key | 574 | talks to Home Assistant over REST to control devices, while this uses an add-on agent inside Home Assistant and edits configuration with Git versioning |
| Home Assistant Vibecode Agent | no | API key | 655 | this is the add-on installed in Home Assistant, while here is the MCP server for the editor that talks to it |
README in short
The README explains the difference between the agent inside Home Assistant and the MCP server on your computer, lists features and installation steps. A connection test, example prompts and common errors such as `spawn npx ENOENT` follow.