Home Assistant
MCP ServerFree** - Interact with Home Assistant to control smart home devices, query states, manage automations, and troubleshoot your smart home setup.
Capabilities8 decomposed
mcp-based smart home device control via natural language
Medium confidenceExposes Home Assistant device control through MCP tools (entity_action, call_service_tool) that translate natural language requests into structured Home Assistant service calls. The FastMCP server acts as a protocol bridge, accepting tool invocations from LLM clients and routing them to Home Assistant's REST API with proper authentication via long-lived access tokens. Supports arbitrary service calls across all Home Assistant domains (lights, climate, switches, etc.) with parameter validation and response formatting optimized for token efficiency.
Implements MCP as a first-class protocol bridge to Home Assistant rather than wrapping REST APIs directly, enabling standardized LLM client integration (Claude, etc.) with schema-based service discovery and automatic parameter validation through Home Assistant's native service registry
Provides tighter LLM integration than direct Home Assistant REST API calls because MCP's tool schema enables Claude and other clients to understand available services without custom prompt engineering, while maintaining Home Assistant as the authoritative device state store
entity state querying and discovery with natural language search
Medium confidenceImplements entity discovery through MCP tools (list_entities, get_entity, entity search) that query Home Assistant's entity registry and state store, returning filtered results based on domain, name, or semantic matching. The search capability uses natural language processing to map user queries (e.g., 'all lights in the bedroom') to entity filters, leveraging Home Assistant's entity metadata (friendly_name, domain, attributes) for intelligent matching. Results are formatted as structured data with current state, attributes, and available actions to minimize token usage in LLM context.
Bridges Home Assistant's entity registry with semantic search by exposing entity metadata through MCP resources (hass://entities/{entity_id}, hass://search/{query}) that LLM clients can query without parsing raw API responses, enabling natural language discovery without custom prompt engineering
More discoverable than raw Home Assistant REST API because MCP resources provide structured entity metadata that LLM clients understand natively, while maintaining Home Assistant's entity registry as the single source of truth for device configuration
automation creation and management with guided workflows
Medium confidenceProvides MCP prompts (create_automation, debug_automation, troubleshoot_entity) that guide LLM clients through multi-step automation workflows using Home Assistant's automation framework. The system exposes automation listing, state queries, and service call capabilities that enable LLMs to both read existing automations and construct new ones by composing triggers, conditions, and actions. Guided prompts structure the conversation to elicit necessary parameters (trigger type, condition logic, action service calls) and validate them against Home Assistant's automation schema before execution.
Uses MCP prompts as structured conversation guides that decompose automation creation into multi-turn workflows, enabling LLMs to gather requirements and validate against Home Assistant's automation schema incrementally rather than requiring full automation specs upfront
More accessible than direct YAML editing because MCP prompts guide users through required parameters step-by-step, while maintaining full compatibility with Home Assistant's native automation engine and allowing advanced users to edit generated YAML directly
historical state analysis and trend detection
Medium confidenceExposes Home Assistant's history API through MCP tools and resources to retrieve historical state data for entities, enabling trend analysis, pattern detection, and usage optimization suggestions. The system queries Home Assistant's state history database (typically SQLite or external database) to return time-series data for sensors, switches, and other stateful entities. LLM clients can analyze this data to identify patterns (peak usage times, recurring failures, anomalies) and suggest automations or optimizations based on observed behavior.
Integrates Home Assistant's state history database with LLM reasoning through MCP resources, enabling natural language queries over time-series data (e.g., 'show me when the living room light was on yesterday') without requiring users to understand SQL or Home Assistant's history schema
Provides more accessible historical analysis than direct Home Assistant REST API because MCP clients can request trends in natural language and receive LLM-synthesized insights, while maintaining Home Assistant's native history storage and retention policies
system diagnostics and troubleshooting with error log access
Medium confidenceExposes Home Assistant system logs and error diagnostics through MCP tools (debug_automation, troubleshoot_entity) that enable LLM clients to diagnose why devices or automations are not functioning. The system retrieves recent error logs, automation trigger history, and entity state change logs from Home Assistant, correlating them to identify root causes (missing integrations, authentication failures, service timeouts, etc.). Troubleshooting prompts guide users through diagnostic workflows by asking targeted questions and analyzing logs to narrow down failure modes.
Combines Home Assistant's error logs with LLM reasoning through MCP prompts to provide guided troubleshooting workflows that correlate log entries with entity state changes and automation triggers, enabling root cause analysis without requiring users to parse raw logs manually
More actionable than raw Home Assistant logs because MCP prompts guide users through diagnostic questions and synthesize log data into specific remediation steps, while maintaining access to Home Assistant's native logging and error reporting
multi-client mcp server orchestration with standardized configuration
Medium confidenceImplements a FastMCP server that exposes Home Assistant capabilities through standardized MCP protocol interfaces (tools, resources, prompts), enabling multiple LLM clients (Claude, ChatGPT, custom agents) to connect via a single configuration. The server uses environment-based configuration (HA_URL, HA_TOKEN) to manage Home Assistant connectivity and exposes a consistent tool/resource/prompt schema that clients discover via MCP handshake. This abstraction decouples client implementations from Home Assistant API details, allowing clients to interact through high-level semantic operations.
Implements MCP as a protocol-level abstraction over Home Assistant's REST API, enabling clients to discover and invoke capabilities through standardized tool/resource/prompt schemas rather than learning Home Assistant's API directly, with FastMCP handling protocol negotiation and request routing
More scalable than embedding Home Assistant integration code in each LLM client because a single MCP server serves multiple clients, while providing better client interoperability than direct REST API integration because MCP's schema-based discovery enables clients to understand available operations without custom prompt engineering
domain-specific entity summaries and overview generation
Medium confidenceGenerates high-level summaries of entity groups by domain (all lights, all sensors, all climate devices) through MCP resources and tools that aggregate entity state and metadata. The system queries Home Assistant's entity registry to group entities by domain, retrieves current state for each entity, and formats results as structured summaries that LLM clients can use for context-aware decision making. Summaries include entity counts, state distributions (e.g., 3 lights on, 2 lights off), and available actions per domain to minimize token usage in LLM context windows.
Aggregates Home Assistant entities by domain and generates structured summaries that LLM clients can use for context without parsing individual entity states, reducing token usage and enabling faster decision-making compared to listing all entities
More efficient than querying individual entities because domain summaries provide aggregated state in a single request, while maintaining Home Assistant's entity registry as the source of truth and enabling clients to drill down into specific entities when needed
long-lived token-based authentication with home assistant rest api
Medium confidenceImplements secure authentication to Home Assistant using long-lived access tokens passed via HA_TOKEN environment variable, which are included in HTTP Authorization headers for all API requests. The system uses standard HTTP Bearer token authentication (Authorization: Bearer {token}) to authenticate requests to Home Assistant's REST API endpoints. Token management is delegated to Home Assistant's user interface — the MCP server does not generate or rotate tokens, only consumes them from environment configuration.
Delegates token management to Home Assistant's native user interface rather than implementing custom token generation, enabling users to revoke or rotate tokens through familiar Home Assistant settings without modifying MCP server configuration
More secure than embedding credentials in configuration files because tokens are stored in environment variables and can be rotated independently, while maintaining Home Assistant's native authentication model and audit logging capabilities
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with Home Assistant, ranked by overlap. Discovered automatically through the match graph.
Home Assistant MCP Server
Control smart home devices and automations via Home Assistant MCP.
Nanoleaf
** - Control Nanoleaf smart lights through MCP - turn on/off, adjust brightness, change colors, set effects, and discover devices
Homey
** - Interact with Homey to control smart home system. Supports devices, flows, and zones. Contains a few goodies for better integrations with LLMs.
hass-mcp
MCP server for Home Assistant (REST/WebSocket) control.
ThingsBoard
** - The ThingsBoard MCP Server provides a natural language interface for LLMs and AI agents to interact with your ThingsBoard IoT platform.
apple-mcp
Collection of apple-native tools for the model context protocol.
Best For
- ✓AI assistant developers building smart home integrations (Claude, ChatGPT plugins)
- ✓Home automation enthusiasts wanting natural language control without coding
- ✓Teams building multi-modal smart home interfaces (voice + chat + mobile)
- ✓LLM agents that need to understand available devices before executing commands
- ✓Smart home dashboards that dynamically populate device lists from Home Assistant
- ✓Troubleshooting workflows that require visibility into all configured entities
- ✓Non-technical smart home users who want to automate routines without learning YAML syntax
- ✓LLM-powered smart home assistants that proactively suggest automations based on user behavior
Known Limitations
- ⚠Requires Home Assistant instance to be network-accessible from MCP server (no local-only deployments without reverse proxy)
- ⚠Service call validation depends on Home Assistant's schema exposure — complex services with nested parameters may require manual prompt engineering
- ⚠No built-in rate limiting or command queuing — rapid successive commands may overwhelm Home Assistant or cause race conditions
- ⚠Authentication relies on long-lived tokens with no rotation mechanism — token compromise grants full Home Assistant access
- ⚠Search relies on entity metadata (friendly_name, domain) — poorly named entities will not be discoverable by natural language
- ⚠No full-text search across entity attributes — only domain, name, and basic attribute filtering supported
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
About
** - Interact with Home Assistant to control smart home devices, query states, manage automations, and troubleshoot your smart home setup.
Categories
Alternatives to Home Assistant
Are you the builder of Home Assistant?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →