home-assistant-vibecode-agent MCP — Casos de uso, Instalar & Demo en vivo

Por qué usarlo

Características clave

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

Demo en vivo

Cómo se ve en la práctica

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

0/0

Instalar

Elige tu cliente

~/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"
      ]
    }
  }
}

Abre Claude Desktop → Settings → Developer → Edit Config. Reinicia después de guardar.

~/.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 usa el mismo esquema mcpServers que Claude Desktop. La configuración del proyecto prevalece sobre la 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"
      ]
    }
  }
}

Haz clic en el icono MCP Servers de la barra lateral de Cline y luego en "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"
      ]
    }
  }
}

Mismo formato que Claude Desktop. Reinicia Windsurf para aplicar.

~/.continue/config.json

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

Continue usa un array de objetos de servidor en lugar de un mapa.

~/.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"
        ]
      }
    }
  }
}

Añádelo a context_servers. Zed recarga en caliente al guardar.

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

Un solo comando. Verifica con claude mcp list. Quita con claude mcp remove.

Casos de uso

Usos del mundo real: 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

Cuándo usarlo: You want to automate something in your home but don't want to write YAML manually.

Requisitos previos

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

Flujo

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.✓ Copiado

→ Automation YAML generated and validated
Deploy and test

Deploy this automation and trigger a test run.✓ Copiado

→ Automation deployed with backup created and test results

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

Errores comunes

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

Cuándo usarlo: You want a beautiful, functional dashboard but find the manual editor limiting.

Requisitos previos

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

Flujo

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.✓ Copiado

→ 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.✓ Copiado

→ Updated dashboard with reordered cards and custom theme

Resultado: A polished Lovelace dashboard deployed to Home Assistant.

Errores comunes

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

Combinaciones

Combínalo con otros MCPs para multiplicar por 10

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.✓ Copiado

Herramientas

Lo que expone este MCP

Herramienta	Entradas	Cuándo llamar
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

Coste y límites

Lo que cuesta ejecutarlo

Cuota de API: N/A — communicates with local Home Assistant instance
Tokens por llamada: 200–1000 tokens per operation
Monetario: Free — open source add-on
Consejo: List entities first to reduce trial-and-error when creating automations.

Seguridad

Permisos, secretos, alcance

Ámbitos mínimos: Home Assistant long-lived access token

Almacenamiento de credenciales: HA access token configured in the add-on settings

Salida de datos: 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.

Resolución de problemas

Errores comunes y soluciones

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.

Verificar: 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.

Verificar: 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.

Verificar: Verify HACS is accessible from Home Assistant sidebar

Alternativas

home-assistant-vibecode-agent vs otros

Alternativa	Cuándo usarla	Contrapartida
Home Assistant REST API directly	You want direct API access without the MCP layer	More control but no AI-assisted YAML generation or validation

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills