$ loading_
Manage files, entities, templates, and diagnostics for Home Assistant development.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "ha-dev-tools-mcp" yet — see the docs or source repo.
Check the current state of sensor.living_room_temperature in Home Assistant and test whether this Jinja template outputs correctly: {{ states('sensor.living_room_temperature') | float > 26 }}. If there is an issue, explain why.Returns the current entity state, template rendering result, and any error causes or fix suggestions.
Call the Home Assistant light.turn_on service for entity light.bedroom and report the result; if it fails, use logs to explain possible reasons.
Provides the service call result, relevant log clues, and recommended next troubleshooting steps.
Review automation.yaml in the Home Assistant config directory for syntax or structural issues, then summarize the current system version, runtime environment, and key diagnostic details.
Outputs configuration review results, explanations of potential issues, and a summary of system and environment details.
Let AI fully control and query Home Assistant through a local MCP server.
Connect AI assistants to Home Assistant for device control and automation.
Use one interface for search, code execution, files, and database queries.
Connect AI to Home Assistant to discover and control smart home devices.
Secure file and directory operations for autonomous AI development workflows.
Access file, system, math, and text utilities through one simple CLI MCP server.