Home Assistant MCP server
io.github.Coolver/home-assistant-mcp·v3.2.12·58 starsVibecode your Home Assistant setup from your IDE: automations, dashboards, themes and configs
58 stars258 downloads/wk
Reviews
Write oneNobody has reviewed Home Assistant yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Home Assistant tools (62, 15 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
ha_add_repository[WRITE] Add a custom add-on repository to Home Assistant. MODIFIES configuration - requires approval. Use to add community repositories with popular add-ons (Zigbee2MQTT, Node-RED, ESPHome, etc).
ha_addon_info[READ-ONLY] Get detailed information about a specific add-on (configuration, state, version, etc). Safe operation - only reads data.
ha_addon_logs[READ-ONLY] Get add-on logs for troubleshooting. Safe operation - only reads data.
ha_analyze_entities_for_dashboard[READ-ONLY] Get complete entity list for AI-driven dashboard generation. Returns entities grouped by domain with attributes. AI will use this data to generate custom dashboard based on user requirements. Safe operation - only reads data.
ha_apply_dashboard[WRITE] Apply generated dashboard configuration to Home Assistant. Creates file, auto-registers in configuration.yaml, and restarts HA. Creates automatic Git backup. MODIFIES configuration - requires approval!
ha_call_service[WRITE] Call a Home Assistant service. MODIFIES system state - requires approval. Examples: number.set_value, light.turn_on, climate.set_temperature, switch.turn_on, etc.
ha_check_config[READ-ONLY] Validate Home Assistant configuration. Safe operation - only checks, does not modify.
ha_check_theme_config[READ-ONLY] Check if themes are configured in configuration.yaml. Safe operation - only reads data.
ha_create_automationwrite action[WRITE] Create new automation in Home Assistant. MODIFIES configuration - requires approval. Provide a meaningful description of what the automation does (e.g., "Control lights based on motion", "Adjust temperature based on schedule").
ha_create_checkpointwrite action[WRITE] Create checkpoint with tag at the start of user request processing. This should be called automatically at the beginning of each user request to save current state before making changes. Creates a commit and tag with timestamp and user request description. Disables auto-commits during request processing.
ha_create_helperwrite action[WRITE] Create a Home Assistant helper via YAML configuration. MODIFIES configuration - requires approval. Helper will be created in YAML file and reloaded automatically. Provide a meaningful description of what the helper is for (e.g., "Enable/disable climate system", "Set target temperature").
ha_create_scriptwrite action[WRITE] Create new script in Home Assistant. MODIFIES configuration - requires approval. Provide a meaningful description of what the script does (e.g., "Start morning routine", "Control climate system").
ha_create_themewrite action[WRITE] Create a new theme in Home Assistant. MODIFIES configuration - requires approval. After creation, call ha_reload_themes or restart HA. Provide a meaningful description of the theme (e.g., "Dark theme with blue accents", "Light theme for daytime use").
ha_delete_automationwrite action[WRITE] Delete automation from Home Assistant. MODIFIES configuration - requires approval.
ha_delete_dashboardwrite action[WRITE] Delete dashboard file and remove from configuration.yaml. Restarts Home Assistant. Creates automatic Git backup. DESTRUCTIVE - requires approval!
ha_delete_filewrite action[WRITE] Delete a file from Home Assistant. DESTRUCTIVE - requires approval!
ha_delete_helperwrite action[WRITE] Delete a Home Assistant helper from YAML configuration. MODIFIES configuration - requires approval.
ha_delete_scriptwrite action[WRITE] Delete script from Home Assistant. MODIFIES configuration - requires approval.
ha_delete_themewrite action[WRITE] Delete a theme from Home Assistant. DESTRUCTIVE - requires approval! After deletion, call ha_reload_themes or restart HA.
ha_end_checkpoint[WRITE] End request processing checkpoint. Re-enables auto-commits. Should be called at the end of user request processing.
ha_get_addon_options[READ-ONLY] Get add-on configuration options. Safe operation - only reads data.
ha_get_entity_state[READ-ONLY] Get entity state and attributes. Safe operation - only reads data.
ha_get_logs[READ-ONLY] Get agent logs to troubleshoot issues. Safe operation - only reads data.
ha_get_theme[READ-ONLY] Get theme content and configuration. Safe operation - only reads data.
ha_git_commit[WRITE] Commit configuration to Git. Creates backup snapshot.
ha_git_diff[READ-ONLY] Show differences between commits. Safe operation - only reads data.
ha_git_history[READ-ONLY] Get Git commit history. Safe operation - only reads data.
ha_git_rollback[WRITE] Rollback configuration to specific commit. DESTRUCTIVE - requires approval!
ha_hacs_install_repository[WRITE] Install integration/theme/plugin from HACS. Requires HACS to be installed. MODIFIES configuration - requires approval!
ha_hacs_list_repositories[READ-ONLY] List available HACS repositories (integrations, themes, plugins). Requires HACS to be installed and configured. If HACS not installed, use ha_hacs_status first and offer installation. Safe operation - only reads data.
ha_hacs_repository_details[READ-ONLY] Get detailed information about a specific HACS repository (stars, authors, versions, etc). Safe operation - only reads data.
ha_hacs_search[READ-ONLY] Search HACS repositories by name, author, or description. If HACS not installed yet, use ha_hacs_status first and offer to install HACS. Safe operation - only reads data.
ha_hacs_status[READ-ONLY] Check if HACS is installed and get version info. ALWAYS call this FIRST when user mentions HACS or asks about custom integrations. If not installed, offer to install via ha_install_hacs. Safe operation - only reads data.
ha_hacs_update_allwrite action[WRITE] Update all installed HACS repositories to latest versions. Home Assistant restart required after updates. MODIFIES configuration - requires approval!
ha_install_addon[WRITE] Install a Home Assistant add-on. MODIFIES system - requires approval. Installation can take several minutes.
ha_install_hacs[WRITE] Install HACS (Home Assistant Community Store). Downloads latest HACS from GitHub, installs to custom_components, and restarts Home Assistant. Opens access to 1000+ integrations. MODIFIES configuration - requires approval!
ha_list_addons[READ-ONLY] List available Home Assistant add-ons (limited list). For complete catalog, use ha_list_store_addons. Safe operation - only reads data.
ha_list_automations[READ-ONLY] List all automations in Home Assistant. Safe operation - only reads data.
ha_list_entities[READ-ONLY] List all entities in Home Assistant. Safe operation - only reads data.
ha_list_files[READ-ONLY] List files and directories in Home Assistant. Safe operation - only reads data.
ha_list_helpers[READ-ONLY] List all helpers in Home Assistant. Safe operation - only reads data.
ha_list_installed_addons[READ-ONLY] List only installed add-ons. Safe operation - only reads data.
ha_list_repositories[READ-ONLY] List all add-on repositories connected to Home Assistant. Shows which sources provide available add-ons. Safe operation - only reads data.
ha_list_scripts[READ-ONLY] List all scripts in Home Assistant. Safe operation - only reads data.
ha_list_store_addons[READ-ONLY] List ALL add-ons from add-on store catalog (complete list from all repositories). Use this to browse available add-ons and make recommendations. Safe operation - only reads data.
ha_list_themes[READ-ONLY] List all available themes in Home Assistant. Safe operation - only reads data.
ha_logbook_entries[READ-ONLY] Fetch Home Assistant logbook entries for analyzing automations, scripts, and other events.
ha_preview_dashboard[READ-ONLY] Preview current Lovelace dashboard configuration. Shows existing ui-lovelace.yaml if configured. Safe operation - only reads data.
ha_read_file[READ-ONLY] Read and display linter errors from the current workspace. You can provide paths to specific files or directories, or omit the argument to get diagnostics for all files. - If a file path is provided, returns diagnostics for that file only - If a directory path is provided, returns diagnostics for all files within that directory - If no path is provided, returns diagnostics for all file
ha_reload_config[WRITE] Reload Home Assistant configuration. APPLIES changes - requires approval!
ha_reload_themes[WRITE] Reload themes in Home Assistant. MODIFIES system state - requires approval. Calls frontend.reload_themes service.
ha_rename_entity[WRITE] Rename an entity_id in Home Assistant via Entity Registry. MODIFIES entity registry - requires approval. After renaming, you may need to reload automations/scripts that reference the entity.
ha_restart[WRITE] FULL restart of Home Assistant. Completely restarts HA Core. Use when configuration changes require full restart (e.g., new dashboards, integrations). HA will be unavailable for 30-60 seconds. DISRUPTIVE - requires approval!
ha_restart_addon[WRITE] Restart an add-on. MODIFIES system - requires approval.
ha_set_addon_options[WRITE] Set add-on configuration options. MODIFIES configuration - requires approval. Add-on may need restart.
ha_start_addon[WRITE] Start an add-on. MODIFIES system - requires approval.
ha_stop_addon[WRITE] Stop a running add-on. MODIFIES system - requires approval.
ha_uninstall_addon[WRITE] Uninstall a Home Assistant add-on. DESTRUCTIVE - requires approval! Removes add-on and its data.
ha_uninstall_hacs[WRITE] Uninstall HACS (Home Assistant Community Store). Removes HACS directory, storage files, and restarts Home Assistant. DESTRUCTIVE - requires approval!
ha_update_addonwrite action[WRITE] Update an add-on to latest version. MODIFIES system - requires approval. Update can take several minutes.
ha_update_themewrite action[WRITE] Update an existing theme in Home Assistant. MODIFIES configuration - requires approval. After update, call ha_reload_themes or restart HA. Provide a meaningful description of what changed (e.g., "Change primary color to blue", "Adjust contrast for better readability").
ha_write_filewrite action[WRITE] Write content to a file in Home Assistant. MODIFIES configuration - requires approval.
Public scan report
scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it
- Code scan17 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 59 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Home Assistant compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 78/100
- higher than 57% of 48,273 servers
- Tools
- 62
- the typical server has 7
- Tools that change things
- 24%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 58
- more than 95% of 28,534 servers
- Downloads a week
- 258
- more than 79% of 11,915 servers with a package
What its tools let an agent do: 47 read · 15 change
Install Home Assistant in Claude Code, Cursor or VS Code
Runs npx -y @coolver/home-assistant-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add home-assistant-mcp -- npx -y @coolver/home-assistant-mcp
What the publisher says
From the Home Assistant repository's README, as published. We do not edit it. Read it on GitHub
Home Assistant Vibecode MCP
⚙️ This MCP server works together with the
Home Assistant Vibecode Agent,
installed as a Home Assistant add-on.
The agent runs on your Home Assistant instance and provides “eyes and hands” for AI IDEs like Cursor, VS Code, Claude Code, or any other MCP-enabled IDE.
Let AI build your Home Assistant automations – or act as your DevOps for the ones you write by hand. Just describe what you need in natural language. 🏠🤖
You describe your goal → AI inspects your Home Assistant → designs a custom solution → and deploys it on-board automatically. 🚀
And if you prefer to handcraft your automations and scripts yourself, the agent can simply act as your DevOps and extra pair of hands: quickly uploading your changes, running tests, and analyzing logs on demand. You stay in control and decide how much you delegate to AI and how deep it should go.
Transform the way you manage your smart home. This add-on enables Cursor, Visual Studio Code (VS Code), or any MCP-enabled IDE to:
- 📝 Analyze your Home Assistant configuration, entities, and devices
- 🏗️ Create intelligent automations, scripts, and complete systems — including Home Assistant helpers that can be fully managed programmatically
- 🎨 Design and customize Lovelace dashboards with full control over cards, layouts, and styling
- 🖌️ Create and tweak themes for a personalized UI
- 🔄 Safely deploy changes with automatic Git-based versioning
- 🔍 Monitor and troubleshoot your setup through log analysis
- 📦 Install and manage HACS integrations and custom repositories
No more manual YAML editing or searching through documentation - just describe what you want in natural language!
Example: "Install smart climate control for my radiators" → AI creates 10+ automations, helpers, sensors, and scripts optimized for YOUR TRVs.
Built on Model Context Protocol and powered by HA Vibecode Agent.
✨ Key Features
🔍 Analyze your setup
✅ Read your full configuration — entities, automations, scripts, helpers ✅ Understand your devices — capabilities, relations, and usage patterns ✅ Learn existing logic — analyze how your current automations and scripts behave
🏗️ Build intelligence
✅ Create complete systems — multiple interconnected automations in seconds ✅ Generate helpers and sensors — tailored to your actual setup and needs ✅ Write optimized scripts — based on real entities, areas, and devices ✅ Refactor existing logic — improve or merge automations instead of starting from scratch
📊 Dashboards & UI
✅ Create and update Lovelace dashboards — fully programmatically ✅ Add, remove, or rearrange cards — stat, graphs, history, custom cards, and more ✅ Control layouts and views — organize rooms, areas, and scenarios ✅ Design and tweak themes — colors, typography, and styles for a personalized UI
🔒 Safe operations
✅ Git-based versioning — every change is tracked with meaningful commit messages ✅ Human-readable commits — AI explains what changed and why ✅ Configuration validation — test before apply to reduce breaking changes ✅ One-click rollback — revert to a previous state if something goes wrong ✅ Activity log — full audit trail of what the agent did and when
📦 Extend with the community
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Home Assistant: common questions
- Is Home Assistant MCP server safe?
- Mostly: it is graded B (78/100). Read the Home Assistant safety report
- How do I install Home Assistant?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Home Assistant need an API key?
- Yes. The registry entry asks for
HA_AGENT_KEY. - Is Home Assistant maintained?
- The last commit was 91 days ago (2026-08-03). The latest release is v3.2.12.
- How does Home Assistant compare with other MCP servers?
- safety score 78/100 (higher than 57% of 48,273 servers); tools 62 (the typical server has 7); tools that change things 24% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.