Home Assistant Vibecode Agent MCP
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
- 636 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The agent controls the home and automations
- A long-lived access token is needed
- A third-party project with no releases
Install
- Works in
Manual install
Install the add-on next to Home Assistant per the README and connect the @coolver/home-assistant-mcp server. Make a copy of the configuration and show automations to the owner before applying.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent controls the home and automations
- A long-lived access token is needed
- A third-party project with no releases
This is third-party code. Review the repository files before installing.
What it does
Home Assistant Vibecode Agent consists of a Home Assistant add-on (a Docker container next to HA) and an MCP server `@coolver/home-assistant-mcp`. The agent checks the configuration and writes and applies automations. A long-lived Home Assistant access token is needed and a key that the agent creates on first launch. Source: `git clone https://github.com/Coolver/home-assistant-vibecode-agent.git`. MIT license, no GitHub releases. This is not an official Home Assistant project.
Who it is for. For smart home owners on Home Assistant who want to write and check automations with an agent.
Good fit when
- You need to write Home Assistant automations with an agent
- You need a configuration check before applying
- You need an MCP server for Home Assistant
Not a fit when
- You cannot let an agent control the home and automations
- You need an official Home Assistant project
Example request
Check the Home Assistant configuration and suggest an automation turning lights off at 23:00, showing it before applyingMCP
- Transport
- stdio
- Authentication
- API key
Limitations
The agent controls your home: it writes and applies automations and changes configuration, so access is wide. A long-lived access token is needed: issue it only for this task and revoke it afterwards. Make a copy of the configuration first. This is a third-party project and not an official one.
How to disable. Remove the add-on in Home Assistant, the server entry from the client and revoke the long-lived token and the agent key.
FAQ
What does it consist of?
A Home Assistant add-on and the @coolver/home-assistant-mcp MCP server.
What is needed to work?
A long-lived Home Assistant access token and an agent key created on first launch.
Is it an official project?
No, it is a third-party project.
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
MCP server for Home Assistant: an agent reads device states, controls them and edits smart home dashboards
A Home Assistant integration that puts GigaChat, YandexGPT or another LLM behind your smart-home voice assistant
MCP server for Discord: an agent manages channels, roles, messages and moderation through your server bot token
An MCP server for driving Windows: the agent opens apps, clicks and types, reads window and UI state, and works with files and PowerShell
An MCP server for Minecraft: an agent controls a bot character via Mineflayer to build and explore
README in short
The README describes a Home Assistant add-on and an MCP server for checking configuration and automations. MIT license.