Home Assistant MCP

Name: Home Assistant MCP
Author: Vortitron

作者：Vortitron版本 0.17.3i★ –i在你的电脑上运行

注册名称io.github.Vortitron/home-assistant-mcp

安装

概览

作者提供的说明（英文原文）

Home Assistant and ESPHome for coding agents: states, services, automations, dashboards, flashing.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i起步阶段↓ 686/周 · ★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 开发者工具
你需要填写：HA_TOKEN, VOMEHOME_TOKEN

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： HA_URL, HA_TOKEN, HA_ALLOW_WRITE, VOMEHOME_TOKEN

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "home-assistant": {
      "command": "npx",
      "args": [
        "-y",
        "@vortitron/home-assistant-mcp"
      ],
      "env": {
        "HA_URL": "your-value",
        "HA_TOKEN": "your-value",
        "HA_ALLOW_WRITE": "your-value",
        "VOMEHOME_TOKEN": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add home-assistant --env HA_URL=your-value --env HA_TOKEN=your-value --env HA_ALLOW_WRITE=your-value --env VOMEHOME_TOKEN=your-value -- npx -y @vortitron/home-assistant-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "home-assistant": {
      "command": "npx",
      "args": [
        "-y",
        "@vortitron/home-assistant-mcp"
      ],
      "env": {
        "HA_URL": "your-value",
        "HA_TOKEN": "your-value",
        "HA_ALLOW_WRITE": "your-value",
        "VOMEHOME_TOKEN": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "home-assistant": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@vortitron/home-assistant-mcp"
      ],
      "env": {
        "HA_URL": "your-value",
        "HA_TOKEN": "your-value",
        "HA_ALLOW_WRITE": "your-value",
        "VOMEHOME_TOKEN": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

HA_URL env
Your Home Assistant's address, e.g. http://homeassistant.local:8123 (or use VOMEHOME_TOKEN instead)
HA_TOKEN 机密 env
A Home Assistant long-lived access token
HA_ALLOW_WRITE env
Set to true to allow service calls and edits; reads only without it
VOMEHOME_TOKEN 机密 env
A key from the Vome app's Agent tab, to reach the home through Vome instead of HA_URL and HA_TOKEN

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 Vortitron 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“开发者工具”中的其他服务器比较i

星标数多于此分类中其他 5550 个服务器的 0%
发布到注册中心的时间比此分类中其他 5550 个服务器的 80% 更新
基础检查结果等于或优于此分类中其他 5550 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Home Assistant MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：HA_TOKEN, VOMEHOME_TOKEN

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.17.3）于4天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

作者：github广泛使用★ 3.4万5天前更新

电脑或云端

安装

Desktop Commander

MCP server for terminal commands, file operations, and process management

作者：wonderwhy-er广泛使用↓ 71万/周★ 1万17天前更新

在你的电脑上运行

安装

Cloudflare MCP

Cloudflare MCP servers

作者：cloudflare广泛使用★ 444614个月前更新

在云端运行✓ mcp.cloudflare.com

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

home-assistant-mcp

A Model Context Protocol (MCP) server that lets coding agents — Cursor, VS Code (Copilot), Claude Desktop and anything else that speaks MCP — talk directly to Home Assistant and (optionally) the ESPHome dashboard.

Instead of copy-pasting entity ids, YAML and current values into your agent, the agent can discover entities, read live state, render templates, call services and edit automations itself — and iterate until the code actually works.

In Claude Code, four side panes show what Claude is doing to your home as it happens: the automation it is working on, the ESPHome device it is building, the home's health score and a dashboard that works. One command installs all four (below).

Part of the Vome family and an open-source companion to

VomeHome (managed Home Assistant). It is useful stand-alone for any Home

Assistant user.

Why

A typical "change an automation" loop today looks like: you tell the agent which entities exist, paste their current values, paste the YAML, apply the change, then manually check whether it worked. With this server the agent does all of that:

See — list entities/areas/devices, read exact states and attributes, pull history and the logbook.
Experiment — render Jinja templates against live state, check configuration, read the error log.
Change — call services, create/update/delete/trigger automations, and (for ESPHome) edit, validate, compile and flash device firmware.

All write operations are off by default and gated behind an explicit safety policy (see Safety).

Tools

Home Assistant — read

Tool	Description
`ha_get_config`	Core config: version, location, time zone, loaded components.
`ha_list_entities`	List entities (filter by domain, free-text search, area).
`ha_get_state`	Full state + attributes for one or more entities.
`ha_get_history`	Historical state changes over a time window. Given only a start time, it runs up to now (Home Assistant alone stops 24 hours after the start); `ha_get_logbook` does the same.
`ha_list_services`	Available services (and their fields for a given domain).
`ha_list_areas`	Areas (rooms/zones).
`ha_list_devices`	Device registry (filter by area / search).
`ha_get_entity_registry`	Registry metadata: platform, area, device, disabled/hidden.
`ha_render_template`	Render a Jinja2 template against live state.
`ha_list_helpers`	List stored helpers (input_boolean, input_number, counter, timer, …).
`ha_list_automations`	Automations with entity_id, unique id, state, last-triggered.
`ha_get_automation`	Full automation config (triggers/conditions/actions) for an automation made in the editor. One written in a YAML package or included file is named as such, with what to search for to find its file.
`ha_check_config`	Validate the configuration (Check configuration).
`ha_wait_until_running`	Wait (up to 120 s) for Home Assistant to finish restarting, checking its core state every 5 s. While it restarts, the other tools say "Home Assistant is restarting (core state: …)" or "not answering — it may be restarting" instead of a raw 502, nginx 404 or WebSocket error. When the home is a CHAP pair's main and its standby is running the home (failover), they say that instead, name the standby and how to reach it (`instance_id` on the call, or `vomehome_use_instance`); the CHAP status is asked once per half minute at most, and only for restart-shaped failures.
`ha_get_system_log`	Deduplicated, structured errors — level, logger, source, count, first/last seen. Start here.
`ha_get_error_log`	Tail of the raw Home Assistant error log.
`ha_get_supervisor_log`	Add-on / Core / Supervisor / host logs (HAOS or Supervised).
`ha_list_media_files` / `ha_read_media_file`	Read-only look into `/media`: a saved camera snapshot comes back as an image (needs `ha:files`, and Vome add-on 0.3.66 / integration 0.9.51 on the home).
`ha_camera_image`	A camera's current still, as an image the agent can see. Via VomeHome the key needs Cameras ticked.
`ha_camera_frame`	A camera still decoded and shrunk to a small grid of RGB pixels, for clients that draw pictures in text.
`ha_view_snapshot`	Everything a dashboard view shows in one call: states, rendered templates, history in few points, camera frames. For dashboard clients.
`ha_watch_states`	Wait for state changes instead of polling: the home's Vome component sends them as they happen (through VomeHome). Where no component is connected (a hosted home without the Vome add-on, a direct connection) it reads the states every ~3 s for the same wait and answers in the same shape with `mode: "polling"`; a 401/403 is never papered over.
`ha_get_logbook`	Human-readable logbook entries, filtered by `entity_id`, `contains` (message, name or entity_id), `name` (e.g. `Vome`) and `domain`. At most `limit` (default 500) come back, the newest, with `count_before_limit`, `truncated` and `older_entries_end_time` to read further back. A window longer than a day is read a day at a time, newest first, stopping as soon as `limit` entries match (at most 31 days per call), so Home Assistant is never asked for more than 24 hours at once.
`ha_get_energy_prefs`	The Energy dashboard's setup (grid, solar, battery, gas, water, tracked devices) with the dashboard's own validation.
`ha_list_traces`	Recent automation/script runs and how each one stopped.
`ha_get_trace`	Step-by-step detail for one run, with `failed_at` naming the blocking step.

Home Assistant — write (write-gated)

Write-gating depends on the mode. In direct mode the MCP is the only guard,

so these refuse until HA_ALLOW_WRITE=true. In brokered mode your VomeHome

API key carries the per-instance ha:write / ha:config scopes and the server

enforces them, so the client flags are optional local-only restrictions.

Tool	Description
`ha_call_service`	Call any service (turn_on, set_temperature, …). A service that can return a response (`shell_command`'s stdout/stderr/returncode, `script`, `weather.get_forecasts` …) is asked for it, and it comes back as `service_response`.
`ha_speech_to_text`	Run a WAV (16-bit PCM, at most 30 s) through one of the home's speech-to-text engines (`stt.*`) and get back the words it heard, to test an assistant's hearing without speaking to a device. `audio_path` reads a local file (npx servers only); `audio_base64` sends the bytes (the hosted MCP). Language defaults to the home's own. Engines want 16 kHz mono (`ffmpeg -i in.wav -ar 16000 -ac 1 -sample_fmt s16 out.wav`). A write because some engines (Vome Hearing, cloud ones) charge per request: needs `HA_ALLOW_WRITE` / `ha:write`; not for external homes through VomeHome.
`ha_clear_system_log`	Empty the structured error store (only needs `HA_ALLOW_WRITE`).
`ha_set_log_level`	Change logging for one integration at runtime (only needs `HA_ALLOW_WRITE`).
`ha_set_automation`	Create or update an automation (also needs `HA_ALLOW_CONFIG_WRITE`).
`ha_set_helper`	Create or update a helper — no `configuration.yaml`, no restart.
`ha_read_config_file`	Read a file under the config directory — text by default, or `encoding: 'base64'` for a binary asset (needs `ha:files`).
`ha_write_config_file`	Replace a file under the config directory — text by default, or `encoding: 'base64'` for a binary asset; checks the config and restores the file if it fails (needs `ha:files`).
`ha_upload_file`	Copy a file already on disk (a web page, an image, a package) into the config directory: read from the MCP server's own filesystem, sent as text or base64 as it needs, at most 2 MiB, written and checked like `ha_write_config_file`. Local (npx) servers only — the hosted MCP can't see your files and answers with the equivalent `curl` upload (needs `ha:files`).
`ha_delete_config_file`	Delete one file under the config directory. Never a directory, and never `configuration.yaml`, `secrets.yaml` or Home Assistant's database. Names its target home like a write (needs `ha:files`, and Vome add-on 0.3.55 / integration 0.9.39 on the home).
`ha_edit_config_file`	Change part of a text file in place: exact find-and-replace edits that must each match once, then the same check-and-restore as a write. For a three-line change to a large file (needs `ha:files`).
`ha_list_config_files`	List a directory under the config directory, folders first: `glob` filters by name (`.yaml`) or path (`/.html`), `offset`/`limit` page (default 200), and the reply gives `total_entries`, `total_bytes` (this folder's own files, not subfolders) and `truncated` when the home stopped at its 500-entry cap (needs `ha:files`).
`ha_move_config_file`	Move or rename one file under the config directory, creating folders on the way; never overwrites unless asked. Names its target home like a write (needs `ha:files`, and Vome add-on 0.3.66 / integration 0.9.51).
`ha_delete_helper`	Delete a stored helper. Refuses when the id looks shared with a `configuration.yaml` helper, because Home Assistant would take that entity down with it.
`ha_delete_automation`	Delete an automation (also needs `HA_ALLOW_CONFIG_WRITE`).
`ha_get_script` / `ha_set_script` / `ha_delete_script`	Scripts by id, the same way as automations: put a step several automations share in one script. Writes need `HA_ALLOW_CONFIG_WRITE`.
`ha_update_entity`	Rename, re-id, move, re-icon, disable or hide an entity in the registry (needs `HA_ALLOW_CONFIG_WRITE`).
`ha_update_device`	Rename a device, move it to an area, disable it or set its labels (needs `HA_ALLOW_CONFIG_WRITE`).
`ha_expose_entities`	List or change what Assist, Alexa and Google Assistant can see and control; listing needs only read (changing needs `HA_ALLOW_CONFIG_WRITE`).
`ha_set_energy_prefs`	Change the Energy dashboard's setup; each list passed replaces that list whole, then it is validated (needs `HA_ALLOW_CONFIG_WRITE`).
`ha_get_statistics`	Read long-term statistics (what the Energy dashboard draws) per 5 minutes to month; `largest_changes` lists the biggest buckets, like the Outliers button.
`ha_adjust_statistic`	Correct one 5-minute bucket of a statistic, by new value or by adjustment, as Developer Tools → Statistics does (needs `HA_ALLOW_CONFIG_WRITE`).
`ha_remove_entity`	Remove an orphaned registry entry (needs `HA_ALLOW_CONFIG_WRITE`).
`ha_matter_reinterview`	The Matter device page's Re-interview, for a device whose endpoints changed after a firmware update (needs `HA_ALLOW_CONFIG_WRITE`).
`ha_trigger_automation`	Manually run an automation now.
`ha_reload_automations`	Reload automations without restarting.

Lovelace dashboards (direct HA or VomeHome brokered)

Tool	What it does
`ha_list_dashboards`	List dashboards (`url_path`, title, mode, sidebar).
`ha_get_dashboard`	Read one dashboard's full config (views, cards, …).
`ha_save_dashboard`	Save/replace a dashboard config (needs `HA_ALLOW_CONFIG_WRITE`).
`ha_create_dashboard`	Register a new storage-mode dashboard (needs `HA_ALLOW_CONFIG_WRITE`).

| ha_update_dashboard | Change a dashboard's title, icon, sidebar

只显示了开头部分；其余内容请在仓库中阅读