← Back to directory

Home Assistant MCP Server

Community

Vibe-code your Home Assistant setup from your IDE: automations, dashboards, themes and configs.

GitHub source repository ↗

★ 56 Stars Category · Dev Tools Popular Source revision cf772dd8ec94

39FMRS · D

Reliability

4/20

Security and permissions

6/20

Maintenance

8/20

Documentation

9/20

Setup experience

12/20

This MCP server offers a unique approach to managing Home Assistant by providing a controlled API integration via a companion agent. It is well-suited for developers looking for AI-assisted automation, but it requires an additional agent add-on. Key risks include key management and reliance on AI-generated configuration changes.

Read the FMRS scoring method →

This MCP server works together with the Home Assistant Vibecode Agent, an add-on that runs inside Home Assistant and provides native access to internal APIs, files, and services. The MCP server runs on your local machine and bridges your AI IDE (Cursor, VS Code, Claude Code, etc.) to the agent via a REST API. It enables natural language management of Home Assistant, including analyzing configurations, creating automations, designing Lovelace dashboards, customizing themes, and deploying changes with Git-based versioning.

Tools

read config

Read the entire Home Assistant configuration, including entities, automations, scripts, and helpers.

analyze entities

Analyze device capabilities, relations, and usage patterns.

create automations

Create and optimize automations, scripts, and complete systems based on real entities, areas, and devices.

design dashboards

Create and update Lovelace dashboards programmatically, controlling cards, layouts, and views.

tweak themes

Create and modify themes to personalize the user interface.

deploy changes

Safely deploy changes with Git-based versioning and rollback support.

install HACS integrations

Install and manage HACS integrations and custom repositories.

Setup

Install and start the HA Vibecode Agent add-on (v2.0.0+) in Home Assistant. 2. Obtain the Agent Key from the add-on's Web UI. 3. Configure your AI editor's MCP client with command 'npx -y @coolver/home-assistant-mcp@latest' and set the environment variables HA_AGENT_URL and HA_AGENT_KEY. 4. Restart your AI editor and test the connection.

claude_desktop_config.json

{
  "mcpServers": {
    "home-assistant": {
      "command": "npx",
      "args": [
        "-y",
        "@coolver/home-assistant-mcp@latest"
      ],
      "env": {
        "HA_AGENT_URL": "http://<home-assistant-host>:8099",
        "HA_AGENT_KEY": "your_api_key_here"
      }
    }
  }
}

Generate and validate client config

Fit and risk

Best for

Developers who want to manage Home Assistant from AI-powered IDEs like Cursor, VS Code, or Claude Code.
Users who want to build and iterate on automations or dashboards using AI while retaining manual control.
Those who need robust, predictable API access to Home Assistant rather than SSH or ad-hoc scripts.

Not for

Users who do not want to install the HA Vibecode Agent add-on or do not want extra custom components inside Home Assistant.
Users who need direct REST API or WebSocket access to Home Assistant without the intermediary agent.
Beginners who are not comfortable installing Node.js locally or using MCP protocol.

Required permissions

Requires access to the local file system (to run Node.js and npx).
Requires network access to the Home Assistant agent's port (usually 8099).
Requires environment variables HA_AGENT_URL and HA_AGENT_KEY for authentication.
The agent itself uses Home Assistant's SUPERVISOR_TOKEN to access internal APIs.

Risks and side effects

Storing the Agent Key in mcp.json may be leaked if committed to git.
AI-generated actions may modify or delete configurations, potentially causing data loss, though Git versioning mitigates this.
Relies on a custom agent running inside Home Assistant, which could introduce security vulnerabilities if exposed.
May inadvertently affect production environments if not configured carefully.

Troubleshooting

Check that Node.js is installed (v20.0.0 or higher).
Verify that the HA Vibecode Agent add-on is installed and running in Home Assistant.
Validate the HA_AGENT_URL and HA_AGENT_KEY environment variables.
Try accessing the agent's /api/health endpoint in a browser or with curl.
If 'spawn npx ENOENT' error occurs, ensure Node.js is in your system PATH.

Use cases

Create complex smart home automations using natural language, e.g., 'Install smart climate control for my radiators'.

Design or modify Lovelace dashboards directly from your IDE without manual YAML editing.

Review and analyze existing configurations for optimization based on actual entities and patterns.

Safely deploy changes with automatic Git versioning and rollback if something goes wrong.

Supported clients

Claude DesktopFull support

CursorFull support

VS CodeFull support

Related MCP servers

Compare with other MCP servers