You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -184,19 +184,19 @@ Spend less time configuring, more time enjoying your smart home.
184
184
185
185
---
186
186
187
-
## 🔌 Custom Component (ha_mcp_tools)
187
+
## 🔌 Custom Component (ha_mcp_tools)*(beta)*
188
188
189
189
Some tools require a companion custom component installed in Home Assistant. Standard HA APIs do not expose file system access or YAML config editing. This component provides both.
190
190
191
191
**Tools that require the component:**
192
192
193
193
| Tool | Description |
194
194
|------|-------------|
195
-
|`ha_config_set_yaml`| Safely add, replace, or remove top-level YAML keys in `configuration.yaml` and package files (automatic backup, validation, and config check) |
196
-
|`ha_list_files`| List files in allowed directories (www/, themes/, custom_templates/) |
Copy file name to clipboardExpand all lines: docs/beta.md
+21-3Lines changed: 21 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,17 +7,23 @@ Some ha-mcp tools are gated behind feature flags and available only in the **dev
7
7
| Tool | Toggle / env var | Description |
8
8
|---|---|---|
9
9
|`ha_config_set_yaml`|`enable_yaml_config_editing` (dev add-on) / `ENABLE_YAML_CONFIG_EDITING=true` (env var) | Raw YAML editing of `configuration.yaml` and packages/*.yaml for YAML-only integrations. |
4. Enable the desired toggle (e.g., `enable_yaml_config_editing`, `enable_filesystem_tools`).
24
+
5. Restart the add-on.
19
25
20
-
The stable add-on does not expose beta toggles.
26
+
`enable_yaml_config_editing`, `enable_filesystem_tools`, and `enable_custom_component_integration` are only available in the dev channel add-on. The stable add-on does not expose these beta toggles.
@@ -49,3 +55,15 @@ This tool edits `configuration.yaml` and package files directly, bypassing Home
49
55
**Recommended prerequisites:**
50
56
- Comfort with editing `configuration.yaml` via SSH or File Editor when things go wrong
51
57
- Understanding that dedicated tools (`ha_config_set_helper`, `ha_config_set_automation`, `ha_config_set_script`, `ha_config_set_scene`, etc.) should be preferred for anything they support
These tools provide direct file access to your Home Assistant filesystem and require `HAMCP_ENABLE_FILESYSTEM_TOOLS=true` and the `ha_mcp_tools` custom component installed and active.
62
+
63
+
`HAMCP_ENABLE_CUSTOM_COMPONENT_INTEGRATION=true` is only needed if you want to allow the `ha_install_mcp_tools` installer tool; it is not required for the filesystem tools themselves.
64
+
65
+
**Access is restricted but sensitive.** Only `www/`, `themes/`, and `custom_templates/` are writable. `ha_read_file` additionally allows reading config YAML files, logs, and `custom_components/`. An AI assistant with these tools enabled has meaningful read access to your HA configuration.
66
+
67
+
**No undo.**`ha_delete_file` and `ha_write_file` (with `overwrite=True`) are irreversible. There is no recycle bin or automatic backup for file operations.
68
+
69
+
**Requires the custom component.** If `ha_mcp_tools` is not installed and active, all file tools will return an error with installation instructions.
|`enable_custom_component_integration`*(beta)*| Enables `ha_install_mcp_tools` installer tool for the `ha_mcp_tools` custom component. |`false`|
20
+
21
+
Beta options are hidden under "Show unused optional configuration options" in the add-on Configuration tab. See [beta.md](https://github.com/homeassistant-ai/ha-mcp/blob/master/docs/beta.md) for details.
0 commit comments