M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
H

Home Assistant MCP Server

Community
Vibe-code your Home Assistant setup from your IDE: automations, dashboards, themes and configs.
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #362 of 438
Stars
★ 58 Popular
Transport
stdio (local process)
Runtime
Node.js 20.0.0+ · Docker
Credentials
API key / credential required
License
MIT
Last commit
Tools
7
39FMRS · D

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.

Strongest · Setup experience 12/20 Weakest · Reliability 4/20

Reliability
4/20
Security and permissions
6/20
Maintenance
8/20
Documentation
9/20
Setup experience
12/20
Why each score
Reliability 4/20
Evidence: the manifest declares the npm package @coolver/home-assistant-mcp version 3.2.31 with stdio transport and required environment variables; the README describes features such as analysis, automation creation, dashboards, themes and deployment. Deduction: no source code, CI or tests were provided, so the MCP init handshake and the actual tool list cannot be verified; error handling and the external agent dependency are not reproducible. Under the static calibration, reliability cannot exceed 12, so a conservative score of 4 is given.
Security and permissions 6/20
Evidence: HA_AGENT_KEY is marked as a secret in the manifest and the README warns not to commit mcp.json; the architecture talks to a local agent over REST on port 8099 and mentions Git versioning and rollback. Deduction: no least-privilege model or explicit confirmation for write/deploy/delete operations is shown; the README describes AI auto-deploying changes to Home Assistant, which creates remote side effects by default; HTTP transport and key-rotation details are unverified. No red-line was triggered because the examples contain no real tokens, but the score remains low at 6.
Maintenance 8/20
Evidence: the repository is not archived, the MIT license is declared, the version is 3.2.31 and a CHANGELOG.md is listed in the README. Deduction: no commit history, release frequency, dependency updates, issue-response or security-advisory evidence is available; maintenance activity can only be inferred from current metadata, and governance and versioning practices are unclear. Score: 8.
Documentation 9/20
Evidence: the README provides prerequisites, quick start, an environment-variable table, an mcpServers configuration example, troubleshooting, architecture and security notes. Deduction: tool parameters, usage limits and cost information are missing; the related-projects links are inconsistent (cursor-agent vs. vibecode-agent); and the README itself is untrusted evidence that cannot substitute for verification of actual behavior. Score: 9.
Setup experience 12/20
Evidence: the README covers Node.js installation, HA Vibecode Agent add-on installation, MCP configuration inside an IDE and a connection test, plus a concrete mcpServers JSON example. Deduction: setup depends on another add-on's Web UI, manual key copying and environment variables; no CI or committed tests prove the end-to-end flow. Per static calibration, setup cannot exceed 15, so a conservative score of 12 is given.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessReads local filesWrites / deletes local filesUses the network

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.

Setup

Before you start

Runtime：Node.js 20.0.0+ · Docker

HA_AGENT_URL required URL of the HA Vibecode Agent add-on (generated after installing the add-on), default http://homeassistant.local:8099.
HA_AGENT_KEY requiredsecret Access key auto-generated by the HA Vibecode Agent add-on on first start; view or regenerate it in the add-on's Web UI.
  1. 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"
      }
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "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"
      }
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add home-assistant -e 'HA_AGENT_URL=http://<home-assistant-host>:8099' -e HA_AGENT_KEY=your_api_key_here -- npx -y @coolver/home-assistant-mcp@latest

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

In your AI editor send: 'Connect to my Home Assistant and show me: 1. List of all my climate entities 2. Current status of the HA Vibecode Agent'. If entities and agent status are returned, the MCP connection works.

Troubleshooting

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

Things to try

Once connected, you can ask your AI assistant things like:

  • Connect to my Home Assistant and show all my climate entities plus the current status of the HA Vibecode Agent
  • Install smart climate control for my radiators
  • Create a Lovelace dashboard for my living room with history graph cards
  • Install a HACS integration and deploy the config changes

Tools 7

read config read-only
Read the entire Home Assistant configuration, including entities, automations, scripts, and helpers.
analyze entities read-only
Analyze device capabilities, relations, and usage patterns.
create automations writes
Create and optimize automations, scripts, and complete systems based on real entities, areas, and devices.
design dashboards writes
Create and update Lovelace dashboards programmatically, controlling cards, layouts, and views.
tweak themes writes
Create and modify themes to personalize the user interface.
deploy changes writes
Safely deploy changes with Git-based versioning and rollback support.
install HACS integrations writes
Install and manage HACS integrations and custom repositories.

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 Desktop
Cursor
VS Code

Listed from the project's documentation, not tested by this site.

Overview

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.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision cf772dd8ec94 Data synced 2026-10-12 Read the FMRS scoring method