hass-mcp-server
Related Servers
Alternatives to hass-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server and Home Assistant add-on that enables AI assistants to manage smart homes by creating automations, designing dashboards, and interacting with entities. It features native access to Home Assistant APIs, built-in Git versioning for safe rollbacks, and full management of HACS integrations.632MIT
- AlicenseAqualityCmaintenanceA self-hosted MCP server for Home Assistant that exposes full control over entity states, service calls, history, templates, and areas via local stdio, enabling AI assistants to manage your smart home.964 npmMIT
- AlicenseAqualityAmaintenanceA comprehensive MCP server that enables AI assistants to interact with Home Assistant, control smart home devices, query states, execute services, and manage automations via natural language.7731,054 PyPI4,867MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI assistants to control Home Assistant via natural language, including device control, automation management, and system configuration.MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for Home Assistant that lets you control and query your smart home through natural language via MCP clients. Provides tools for entities, devices, services, automations, scripts, history, add-ons, and system info, with read-only access by default and optional configurable write support.1MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that exposes Home Assistant's REST and WebSocket APIs as 182 tools, enabling clients like Claude Code to control lights, climate, media, automations, and more. It also provides a status dashboard and supports running as a Home Assistant app or container.AGPL 3.0
TDQS
Scored across 66 tools
Every tool clearly targets a distinct resource and action, even within similar domains like files, dashboards, or add-ons. Overlapping concepts such as list/get, event/logbook, and upload_file/upload_file_content are differentiated by their descriptions enough to prevent misselection.
The ha_ prefix and mostly verb_noun pattern are consistent and readable. Minor deviations exist where nouns are used alone (ha_addon_info, ha_system_info, ha_file_exists) and where list vs get is used inconsistently for read operations.
At 66 tools, this far exceeds the 50+ threshold for an extreme count. While Home Assistant is a broad platform, this many tools creates an unwieldy MCP surface that is hard for an agent to navigate efficiently.
The toolset covers CRUD for automations, scripts, scenes, helpers, and dashboards, plus files, add-ons, entities, and system operations. Notable gaps include missing area update/delete, backup restore/delete, device get/update, and get-by-id operations for scripts and scenes, though these are mostly workable.