MCP ConfigsMay 14, 2026·4 min read

home-assistant-vibecode-agent — MCP Agent for Home Assistant

Home Assistant Vibecode Agent exposes automations, dashboards, configs and HACS via MCP for AI IDEs. Verified 548★; pushed 2026-05-14.

Agent ready

This asset can be read and installed directly by agents

TokRepo exposes a universal CLI command, install contract, metadata JSON, adapter-aware plan, and raw content links so agents can judge fit, risk, and next actions.

Needs Confirmation · 62/100Policy: confirm
Agent surface
Any MCP/CLI agent
Kind
Mcp
Install
Ha Addon|Docker
Trust
Trust: Established
Entrypoint
docker compose -f docker-compose.standalone.yml up -d
Universal CLI install command
npx tokrepo install 30ba089f-82d9-5fd9-8a00-887fb790dab4
Intro

Home Assistant Vibecode Agent exposes automations, dashboards, configs and HACS via MCP for AI IDEs. Verified 548★; pushed 2026-05-14.

Best for: Home Assistant power users who want an AI IDE to create/debug automations and dashboards via MCP

Works with: Home Assistant OS/Supervised (add-on) or HA Container (standalone Docker); connects to MCP-enabled IDEs (per README)

Setup time: 15-35 minutes

Key facts (verified)

  • GitHub: 548 stars · 46 forks · pushed 2026-05-14.
  • License: MIT · owner avatar + repo URL verified via GitHub API.
  • README-backed entrypoint: docker compose -f docker-compose.standalone.yml up -d.

Main

  • Pick the deployment model that matches your HA install: add-on for OS/Supervised; standalone Docker for HA Container setups.

  • Use a Long-Lived Access Token and keep it out of chat logs; store it in .env and rotate it periodically.

  • Start by reviewing generated automations and dashboards before deploying; treat AI edits like PRs for your smart home.

  • If you enable file write access, restrict paths to your HA config directory to avoid accidental destructive edits.

README (excerpt)

HA Vibecode Agent

Version License MCP Package Landing Page

Let 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 agent enables Claude Code, Cursor, Visual Studio Code (VS Code), or any MCP-enabled IDE to:

  • 📝 Analyze your Home Assistant configuration, entities, and devices
  • 🏗️ Create intelligent automations, scripts, and complete systems — including Home Assistant helpers that can be fully managed programmatically
  • 🎨 Design and customize UI dashboards with full control over cards, layouts, and styling
  • 🖌️ Create and tweak themes for a personalized UI
  • 🔄 Safely deploy changes with automatic Git-based versioning
  • 🔍 Monitor and troubleshoot your setup through log analysis
  • 📦 Install and manage HACS integrations and custom repositories

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

Source-backed notes

  • README documents two install options: a Home Assistant add-on, and a standalone Docker Compose mode.
  • README standalone mode uses .env with HA_URL, HA_TOKEN, and HA_CONFIG_PATH, then starts with docker compose -f docker-compose.standalone.yml up -d.
  • README states an API key is generated on first start and can be found in logs or in a file under the HA config path.

FAQ

  • Which install option should I use?: Use add-on for HA OS/Supervised; use standalone Docker for HA Container (per README).
  • Where do I get the token?: README instructs creating a Long-Lived Access Token in the HA UI profile page.
  • How do I debug connection issues?: Check container logs for the API key and confirm your IDE points to the host:8099 endpoint.
🙏

Source & Thanks

Created by Coolver. Licensed under MIT.

Coolver/home-assistant-vibecode-agent — ⭐ 548

Thanks to the upstream maintainers and contributors for publishing this work under an open license.

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets