GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Beschreibung vom Entwickler (englisches Original)
Home Assistant and ESPHome for coding agents: states, services, automations, dashboards, flashing.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
HA_URL, HA_TOKEN, HA_ALLOW_WRITE, VOMEHOME_TOKENAls geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"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"
}
}
}
}Führe das in deinem Terminal aus
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-mcpTrag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"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"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"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"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
HA_URL envHA_ALLOW_WRITE envDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto Vortitron bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Das musst du eintragen: HA_TOKEN, VOMEHOME_TOKEN
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.17.3) kam vor 3 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Node.js auf deinem Computer.
In derselben Kategorie: GitHub, Desktop Commander, Cloudflare MCP
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
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.
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:
All write operations are off by default and gated behind an explicit safety policy (see Safety).
| 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. |
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:configscopes 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. |
| 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
Nur der Anfang wird gezeigt; den Rest findest du im Repo