Home Assistant Mcp
Edit Home Assistant automations, dashboards, themes, and YAML config from your IDE with an agent that talks to your instance through the Vibecode Agent add-on.
Overview
Home Assistant MCP is an MCP server for the Build phase that connects your IDE agent to a Home Assistant Vibecode Agent add-on to edit automations, dashboards, themes, and configs.
What is this MCP server?
- Vibecode automations, dashboards, themes, and configs from the IDE
- npm package @coolver/home-assistant-mcp v3.2.12 with stdio transport
- Requires Home Assistant Vibecode Agent add-on with HA_AGENT_URL and HA_AGENT_KEY
- GitHub-hosted server schema aligned with MCP 2025-10-17
- Targets homelab and smart-home builders who treat HA like a product surface
- Package version 3.2.12
- Transport: stdio via npm identifier @coolver/home-assistant-mcp
- Two required secrets: HA_AGENT_URL and HA_AGENT_KEY
Community signal: 48 GitHub stars.
What problem does it solve?
You iterate Home Assistant YAML and dashboards in the UI while your agent cannot safely apply the same changes in your repo-aligned workflow.
Who is it for?
Homelab owners and smart-home indie builders who already run Home Assistant and want IDE-native, agent-assisted config iteration.
Skip if: Builders without a self-hosted Home Assistant instance or willingness to install the Vibecode Agent add-on.
What do I get? / Deliverables
After the add-on and MCP env vars are set, your agent can propose and apply automations, dashboard, and theme edits against your live instance through stdio MCP.
- Agent-driven edits to automations and scripts
- Dashboard and theme configuration changes
- IDE-synced HA config iteration workflow
Recommended MCP Servers
Journey fit
Hooking a personal or homelab stack into your dev environment is classic Build work—wiring integrations before you rely on them in daily Operate. Integrations fits MCP that bridges Home Assistant APIs and config artifacts into Claude Code or Cursor, distinct from generic frontend or backend app code.
How it compares
Home Assistant integration MCP, not a generic IoT cloud provisioning skill.
Common Questions / FAQ
Who is Home Assistant MCP for?
Solo builders and homelab users who run Home Assistant and want Claude Code, Cursor, or similar agents to edit automations and dashboards via MCP.
When should I use Home Assistant MCP?
Use it in Build when you are integrating and refining HA automations, themes, and dashboards—not as your primary production monitoring stack.
How do I add Home Assistant MCP to my agent?
Install the Home Assistant Vibecode Agent add-on, copy HA_AGENT_URL and HA_AGENT_KEY into your environment, add the npm @coolver/home-assistant-mcp stdio server to your MCP config.