F
licenseNot graded
qualityB
maintenanceEnables Claude to read and control a Home Assistant instance, including authoring schedules, scenes, and automations rather than just toggling devices.
-
homeassistant-mcp
Related Servers
Alternatives to homeassistant-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables interaction with Home Assistant through the REST API, allowing users to query states, call services, and manage entities via natural language.29 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with Home Assistant to control smart home devices, query entity states, and manage automations using natural language. It provides over 90 tools for comprehensive system management, including dashboard configuration, service execution, and automation debugging.MIT
- FlicenseNot gradedqualityCmaintenanceEnables natural-language control of home appliances through Home Assistant, exposing tools to list entities and areas, read states and history, call services, activate scenes, render templates, and confirm sensitive actions via one-time tokens. A built-in safety policy restricts it to appliance-class devices, outright denying gas, valves, locks, alarms, security panels, water heaters, door/window covers, and arbitrary-command domains.-
- AlicenseBqualityDmaintenanceProvides tools for AI assistants to interact with smart home devices through Home Assistant, allowing operations like checking entity states and calling services.399 npm3MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to control and monitor Home Assistant smart home devices through natural language interactions. Supports device control, entity state monitoring, history access, and automation generation with both MCP protocol and standalone HTTP REST API modes.1MIT
TDQS
A3.8/5.0
Scored across 15 tools
Disambiguation5/5
Each tool targets a clearly distinct resource or action, and the descriptions explicitly distinguish similar tools such as ha_set_state vs ha_call_service and ha_get_history vs ha_get_logbook. ha_call_api is also clearly positioned as a fallback rather than an overlapping alternative.
Naming Consistency5/5
All tools use a consistent ha_ prefix followed by snake_case verb_noun naming (e.g. ha_get_state, ha_list_services, ha_call_service, ha_delete_state). The naming convention is predictable throughout the set.
Tool Count5/5
Fifteen tools is well scoped for a Home Assistant API client, covering core read, control, and fallback operations without excessive fragmentation. Each tool has a clear purpose and earns its place.
Completeness4/5
The set covers essential Home Assistant workflows: configuration, states, services, history, logbook, templates, calendars, events, and direct state manipulation. Some dedicated management operations (e.g. automations, scripts, deeper config flows) are not surfaced directly, though ha_call_api provides a workaround.
Maintenance
ActivityMaintained
ResponsivenessNo issues