home-assistant-vibecode-agent MCP — Use Cases, Install & Live Demo

Why use it

Key features

Natural language automation creation and debugging
Lovelace dashboard design and theme customization via AI
Git-based automatic backups with meaningful commit messages and rollback
HACS integration for installing 1000+ community components
Full HA REST API and WebSocket access with configuration validation

Live Demo

What it looks like in practice

home-assistant-vibecode-agent-2.replay ▶ ready

0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "home-assistant-vibecode-agent-2": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/Coolver/home-assistant-vibecode-agent"
      ]
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "home-assistant-vibecode-agent-2": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/Coolver/home-assistant-vibecode-agent"
      ]
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "home-assistant-vibecode-agent-2": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/Coolver/home-assistant-vibecode-agent"
      ]
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "home-assistant-vibecode-agent-2": {
      "command": "TODO",
      "args": [
        "See README: https://github.com/Coolver/home-assistant-vibecode-agent"
      ]
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "home-assistant-vibecode-agent-2",
      "command": "TODO",
      "args": [
        "See README: https://github.com/Coolver/home-assistant-vibecode-agent"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "home-assistant-vibecode-agent-2": {
      "command": {
        "path": "TODO",
        "args": [
          "See README: https://github.com/Coolver/home-assistant-vibecode-agent"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add home-assistant-vibecode-agent-2 -- TODO 'See README: https://github.com/Coolver/home-assistant-vibecode-agent'

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use home-assistant-vibecode-agent

How to create a Home Assistant automation with natural language

👤 Smart home enthusiasts who prefer describing what they want over writing YAML ⏱ ~10 min beginner

When to use: You want to automate something in your home but don't want to write YAML manually.

Prerequisites

Home Assistant with the add-on installed — Add repository https://github.com/coolver/home-assistant-vibecode-agent and install
MCP client configured — Configure Claude Code or Cursor to connect to the add-on's MCP endpoint

Flow

Describe your automation

Create an automation: when I arrive home (phone GPS enters home zone), turn on the living room lights, set them to 70% brightness, and start playing my Spotify playlist on the kitchen speaker.✓ Copied

→ Automation YAML generated and validated
Deploy and test

Deploy this automation and trigger a test run.✓ Copied

→ Automation deployed with backup created and test results

Outcome: A working Home Assistant automation created from a plain English description.

Pitfalls

Entity names don't match what you described — Ask the agent to list available entities first so you can reference the correct names

Design a custom Lovelace dashboard with AI

👤 Home Assistant users who want better dashboards without learning Lovelace YAML ⏱ ~20 min intermediate

When to use: You want a beautiful, functional dashboard but find the manual editor limiting.

Prerequisites

Vibecode agent running and connected — Install add-on and configure MCP client

Flow

Describe the dashboard

Design a dashboard for my bedroom: show temperature/humidity from the sensor, light controls with brightness sliders, a media player card for the Sonos, and a graph of temperature over the last 24 hours.✓ Copied

→ Lovelace YAML generated with all requested cards
Iterate on design

Move the media player to the top and add a dark theme that matches my bedroom colors.✓ Copied

→ Updated dashboard with reordered cards and custom theme

Outcome: A polished Lovelace dashboard deployed to Home Assistant.

Pitfalls

Custom cards require HACS installation — Ask the agent to install required HACS components before adding custom cards

Combinations

Pair with other MCPs for X10 leverage

home-assistant-vibecode-agent-2 + filesystem

Export and backup Home Assistant configurations to local files

Export all my automations and dashboard configs to ~/ha-backup/ for version control.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call
create_automation	description or YAML	Create or modify Home Assistant automations
update_dashboard	dashboard config	Create or update Lovelace dashboards
list_entities	domain?: str	List available Home Assistant entities
call_service	domain: str, service: str, data?: obj	Call a Home Assistant service (turn on lights, play media, etc.)
install_hacs	component: str	Install a HACS community component

Cost & Limits

What this costs to run

API quota: N/A — communicates with local Home Assistant instance
Tokens per call: 200–1000 tokens per operation
Monetary: Free — open source add-on
Tip: List entities first to reduce trial-and-error when creating automations.

Security

Permissions, secrets, blast radius

Minimum scopes: Home Assistant long-lived access token

Credential storage: HA access token configured in the add-on settings

Data egress: Communicates with your local Home Assistant instance only. HACS downloads from GitHub.

This add-on has full access to your Home Assistant API. It can control all devices, modify configurations, and install components.
Always verify automation YAML before deploying — bad automations can trigger devices unexpectedly.
Git backup provides rollback, but test changes on non-critical devices first.

Troubleshooting

Common errors and fixes

Add-on can't connect to Home Assistant

Verify the long-lived access token is correct and hasn't expired. Check the add-on logs for connection errors.

Verify: Check Home Assistant → Settings → Add-ons for the agent's status

Automation validation fails

The generated YAML may reference entities that don't exist. List entities first to verify names.

Verify: list_entities to see all available entity IDs

HACS component not installing

Ensure HACS itself is installed in Home Assistant first. Check that the component name is correct.

Verify: Verify HACS is accessible from Home Assistant sidebar

Alternatives

home-assistant-vibecode-agent vs others

Alternative	When to use it instead	Tradeoff
Home Assistant REST API directly	You want direct API access without the MCP layer	More control but no AI-assisted YAML generation or validation

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills