home-assistant-vibecode-agent

HA Vibecode Agent MCP integration provides a controlled bridge between your AI IDE (Cursor, VS Code, Claude, or any MCP-enabled IDE) and your Home Assistant instance. The MCP server component runs on your computer and communicates with the Home Assistant Agent running inside Home Assistant as an add-on. This separation gives the AI access to a stable, well-defined API surface and the full REST/WebSocket capabilities of Home Assistant, enabling programmatic reading of configuration, entities, and devices, as well as automated creation of automations, scripts, helpers, and Lovelace dashboards. Tools available through the MCP server include: reading and listing entities, services, configurations, and Lovelace dashboards; creating and updating automations, scripts, helpers, and sensors; managing themes and dashboards; and performing safe file and repository operations with versioning and rollback support. In practice, you can describe your goal in natural language, and the agent will draft the necessary automations and UI changes, validate configurations, commit changes with meaningful messages, and allow one-click rollback if needed.

Prerequisites:

• A computer where you run your MCP server (outside Home Assistant) with Node.js and npm installed.
• Access to the MCP ecosystem and the ability to install npm packages globally or run via npx.

Installation steps:

1. Install Node.js and npm from https://nodejs.org/.
2. Install the MCP package globally (or use npx when running):
   • Global install (optional): npm install -g @coolver/home-assistant-mcp
3. Run the MCP server using the MCP package (via npx or a local install):
   • Using npx (recommended): npx -y @coolver/home-assistant-mcp
   • If installed locally: npx -y @coolver/home-assistant-mcp
4. Ensure the Home Assistant Agent add-on is running in your Home Assistant instance and that the MCP server can reach it through the configured API endpoint.
5. In your MCP IDE, add a new MCP server configuration pointing to the command specified by the mcp_config (see the generated JSON) and connect.

Optional: consult the repository documentation for any environment-specific tweaks or extra configuration flags, such as custom API endpoints or authentication tokens if required by your setup.

Notes and tips:

• The HA Vibecode Agent provides a safe on-board REST API and a rich toolset to interact with Home Assistant from external IDEs. It supports reading configurations, listing entities, calling services, validating configurations, and safe file operations within /config.
• Use Git-based versioning for all changes to allow meaningful commit messages and easy rollbacks. AI-generated messages should explain what changed and why.
• Before applying significant changes, use the validation features to catch misconfigurations and enable a one-click rollback if something goes wrong.
• If you customize environment variables, ensure they are set correctly in your MCP server configuration. Typical variables might include API endpoints, authentication tokens, or debug flags, depending on your deployment.
• Ensure network accessibility between your MCP server host and the Home Assistant instance (the add-on) to avoid connectivity issues.
• When upgrading the MCP package, review changelogs for breaking changes related to API surface or required configuration.