by Coolver
Home Assistant MCP server agent. Enable Claude Code, Cursor, VS Code or any MCP-enabled IDE to help you vibe-code and manage Home Assistant: create and debug automations, design dashboards, tweak themes, modify configs, and deploy changes using natural language
# Add to your Claude Code skills
git clone https://github.com/Coolver/home-assistant-vibecode-agentLet AI build your Home Assistant automations โ or act as your DevOps for the ones you write by hand. Just describe what you need in natural language. ๐ ๐ค
You describe your goal โ AI inspects your Home Assistant โ designs a custom solution โ and deploys it on-board automatically. ๐
And if you prefer to handcraft your automations and scripts yourself, the agent can simply act as your DevOps and extra pair of hands: quickly uploading your changes, running tests, and analyzing logs on demand. You stay in control and decide how much you delegate to AI and how deep it should go.
Transform the way you manage your smart home. This add-on enables Cursor, Visual Studio Code (VS Code), or any MCP-enabled IDE to:
No comments yet. Be the first to share your thoughts!
No more manual YAML editing or searching through documentation - just describe what you want in natural language!
Real example: User says "Install smart climate control" โ AI analyzes 7 TRVs, creates 10 automations + 9 helpers + 10 sensors + 5 scripts, deploys everything, and it just works!
https://github.com/user-attachments/assets/0df48019-06c0-48dd-82ad-c7fe0734ddb3
Full YouTube Demo:
HA Vibecode Agent is a Home Assistant add-on that exposes a safe on-board REST API and toolset, allowing AI assistants (Cursor, VS Code, Claude, Continue, and any MCP-enabled IDE) to work with your Home Assistant instead of just generating YAML in the dark.
โ
Read your full configuration โ entities, automations, scripts, helpers
โ
Understand your devices โ capabilities, relations, and usage patterns
โ
Learn existing logic โ analyze how your current automations and scripts behave
โ
Create complete systems โ multiple interconnected automations in seconds
โ
Generate helpers and sensors โ tailored to your actual setup and needs
โ
Write optimized scripts โ based on real entities, areas, and devices
โ
Refactor existing logic โ improve or merge automations instead of starting from scratch
โ
Create and update Lovelace dashboards โ fully programmatically
โ
Add, remove, or rearrange cards โ stat, graphs, history, custom cards, and more
โ
Control layouts and views โ organize rooms, areas, and scenarios
โ
Design and tweak themes โ colors, typography, and styles for a personalized UI
โ
Git-based versioning โ every change is tracked with meaningful commit messages
โ
Human-readable commits โ AI explains what changed and why
โ
Configuration validation โ test before apply to reduce breaking changes
โ
One-click rollback โ revert to a previous state if something goes wrong
โ
Activity log โ full audit trail of what the agent did and when
โ
Install and configure HACS โ unlock 1000+ community integrations
โ
Search repositories โ themes, plugins, custom components, dashboards
โ
Install integrations โ one-command setup for new HACS components
โ
Keep things fresh โ update all HACS repositories from a single place
Result:
You describe your goal โ AI inspects your Home Assistant โ designs a custom solution โ and deploys it on-board automatically. ๐
Most MCP integrations Iโve seen for Cursor, VS Code or Claude work only on your local machine and talk to Home Assistant over SSH and sometimes the REST API.
For serious Home Assistant work, thatโs not really enough:
Home Assistant is not just a bunch of YAML files. It exposes multiple internal APIs, and some of the most important ones are only available from inside HA itself over the WebSocket API.
When you access HA only via SSH, the AI usually has to generate and upload a helper script on every request, then execute it blindly on the host. Since that script can be different every time, each request is a bit of a black box โ more like playing Russian roulette than doing reliable automation.
Because of that, I chose a different architecture.
This project is split into two modules:
Home Assistant Agent (this module) โ runs inside Home Assistant (as an add-on), has native access to all relevant APIs, files and services, and exposes a safe, well-defined interface for external tools.
Home Assistant MCP server โ runs on your computer alongside your AI IDE (Cursor, VS Code, etc.) and talks to the Agent over a controlled API instead of SSH hacks (installation steps below)
This design makes working with Home Assistant faster, more predictable, safer and repeatable. Your AI IDE gets exactly the actions and data it needs โ through a stable API โ instead of constantly inventing ad-hoc scripts and hoping they behave correctly.
/config)Example AI interactions:
Complete add-on lifecycle management โ install, configure, and control services!
Complete HACS integration via WebSocket โ browse 1000+ custom integrations!
Open your Home Assistant UI (usually http://homeassistant.local:8123):
https://github.com/coolver/home-assistant-vibecode-agentStill in Home Assistant UI:
You'll see this interface:
Click the Cursor or VS Code tab (depending on which IDE you want to use with Home Assistant) and follow the setup instructions. Youโll need to install and configure Cursor or VS Code so they can connect to the HA Agent via the MCP protocol.
Thatโs it โ youโre ready to start working with your Home Assistant scripts, automations and dashboards using AI. If you find this project useful and want to support its development, **please consider giving it a [GitHub Star](https://github.com/Coolv