forked from homeassistant-ai/ha-mcp
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathen.yaml
More file actions
43 lines (43 loc) · 2.06 KB
/
Copy pathen.yaml
File metadata and controls
43 lines (43 loc) · 2.06 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
---
configuration:
backup_hint:
name: Backup hint
description: Controls when backup reminders are shown before risky operations.
secret_path:
name: Secret path override
description: |
Optional custom HTTP path for the MCP server. Leave empty to use the auto-generated secure path.
enable_skills:
name: Enable skills
description: >-
Serve bundled Home Assistant best-practice skills as MCP resources.
Skills provide automation patterns, helper selection guides, and device
control best practices. Clients must explicitly request them.
enable_skills_as_tools:
name: Enable skills as tools
description: >-
Expose skills via list_resources/read_resource tools for MCP clients
that don't support resources natively. Adds 3 extra tools.
enable_tool_search:
name: Enable tool search
description: >-
Replace the full tool catalog with search-based discovery. Reduces
idle context from ~46K to ~5K tokens. Use this if using an LLM without
deferred tools or with smaller context windows. Tools are found via
ha_search_tools and executed via categorized proxies (read/write/delete).
Requires restart to take effect.
enable_yaml_config_editing:
name: Enable YAML config editing
description: >-
The only ha-mcp tool gated behind a toggle, disabled by default.
Intended for operators comfortable editing configuration.yaml
directly — a broken edit can prevent Home Assistant from starting,
and recovery may require SSH access to restore from the automatic
backup. AI assistants also sometimes select this tool when a
dedicated tool (automations, scripts, scenes, helpers, template
sensors) would be correct. Allows AI assistants to add, replace,
or remove top-level keys in configuration.yaml and packages/*.yaml.
Only whitelisted keys are allowed (e.g., template, sensor,
command_line, mqtt); core keys like homeassistant, http, and
recorder are blocked. A backup is created before every edit.
Requires restart to take effect.