homelab-codex-ws/services/ha-mcp/requirements.txt

# ha-mcp — dev-station tool, not a deployed service (no image, no compose).
# Install into services/ha-mcp/.venv; see README.md, "Install".
mcp>=2.0
# Also required, and already present system-wide on the dev station /
# control nodes (used by scripts/ha/lib/*): requests, PyYAML,
# websocket-client. The venv is created with --system-site-packages so it
# reuses them instead of shadowing the versions the rest of scripts/ha uses.
pytest  # tests only
feat(ha-mcp): read-only MCP server (faza 2a) Own minimal MCP server exposing the live state of the HA instances in services/home-assistant/instances.yaml to Claude Code over stdio — the phase-2 "MCP read-only" gate in services/home-assistant/DESIGN.md. Operator decision 2026-07-30: build our own rather than adopt hass-mcp, so the tools reuse scripts/ha/lib/{ha_api,ha_ws}.py (one token-handling story for the whole HA toolchain) and can answer from the repo and from instances.yaml, which a generic server cannot. Seven tools, all read-only, default instance `ken`: list_entities, get_state, get_areas, find_entities_by_description, read_automation, list_automations, instance_status. Read-only by construction, not by policy: REST goes through ha_api.Client (get/get_raw_text only — no POST method exists), WebSocket commands are checked against a three-entry *_list allowlist before being sent, and read_automation reads services/home-assistant/config/<instance>/ rather than /api/config. Tests assert all three, including a grep guard that fails if requests.post/call_service ever appears in the package. The write path stays repo + scripts/ha/deploy.sh. Details that follow from how this instance actually behaves: - unavailable is never silent — every entity view carries unavailable + unavailable_since, every list a count. The 2026-07-23 audit traced ~15 silently dead automations to conditions sitting on dead sensors. - chelsty-ha (status: offline in instances.yaml) is answered from the file, never dialed — no 5s timeout for a known-offline LTE site. - areas come from the WS registries (entity area_id > device area_id) with a storage-export fallback; area_source/area_note say which was used and what the offline export cannot resolve. - PL->EN fuzzy matching, since the house is Polish and the entity_ids are transliterated English: "czujnik temperatury salon" -> sensor.thsalon_temperature, each hit explaining why it matched. - 5s timeouts and errors returned as {"error": ...} inside a normal tool result — a missing token or an unreachable instance never crashes the server or hangs the agent. Registered for Claude Code in the repo-root .mcp.json (new file) as `ha`, via services/ha-mcp/run.sh (prefers the venv, falls back to system python3). The mcp SDK lives in services/ha-mcp/.venv — rationale for venv over --break-system-packages is in the README. Tests: 42 offline (no network, no HA, no token) + a live read-only smoke against ken — HA 2026.7.2, 1647 entities, 377 unavailable, 115 automations, 13 areas. 2026-07-30 16:37:38 +02:00			`# ha-mcp — dev-station tool, not a deployed service (no image, no compose).`
			`# Install into services/ha-mcp/.venv; see README.md, "Install".`
			`mcp>=2.0`
			`# Also required, and already present system-wide on the dev station /`
			`# control nodes (used by scripts/ha/lib/*): requests, PyYAML,`
			`# websocket-client. The venv is created with --system-site-packages so it`
			`# reuses them instead of shadowing the versions the rest of scripts/ha uses.`
			`pytest # tests only`