hass-mcp
MCP ServerFreeMCP server for Home Assistant (REST/WebSocket) control.
Capabilities6 decomposed
home assistant device state querying via mcp protocol
Medium confidenceExposes Home Assistant entity state and metadata through MCP's standardized tool interface, translating REST API calls into structured JSON responses. The server implements MCP's tool schema to allow LLM clients to query device states (lights, switches, sensors, climate) without direct API knowledge, handling authentication via Home Assistant long-lived tokens and managing connection pooling to the Home Assistant instance.
Bridges Home Assistant's REST API directly into MCP's tool-calling framework, allowing LLMs to discover and query smart home state without custom prompt engineering or API documentation
Simpler than building custom Home Assistant integrations because it uses standard MCP protocol that works with any MCP-compatible LLM client (Claude, etc.) without Home Assistant plugin development
home assistant device control via mcp tool execution
Medium confidenceImplements MCP tools for executing Home Assistant service calls (turn_on, turn_off, set_temperature, etc.) with schema validation and error handling. The server translates LLM-generated tool calls into Home Assistant WebSocket service calls, managing request/response correlation and returning execution status back to the LLM with confirmation or error details.
Uses Home Assistant's WebSocket API for bidirectional control rather than REST polling, enabling real-time command execution and status feedback within the MCP tool-calling loop
More responsive than REST-only approaches because WebSocket maintains persistent connection and eliminates polling latency; integrates directly with Home Assistant's native service architecture
mcp tool schema generation from home assistant service definitions
Medium confidenceDynamically introspects Home Assistant's available services and generates MCP-compliant tool schemas with parameter validation, descriptions, and required field constraints. The server queries Home Assistant's service registry on startup and maps service domains/names to MCP tool definitions, enabling LLMs to discover available actions without hardcoded tool lists.
Introspects Home Assistant's service registry at runtime to generate MCP schemas, avoiding hardcoded tool definitions and supporting custom add-ons automatically
More maintainable than static tool definitions because it adapts to Home Assistant configuration changes without code updates; enables support for third-party Home Assistant integrations
websocket connection management with automatic reconnection
Medium confidenceManages persistent WebSocket connections to Home Assistant with exponential backoff reconnection logic, connection state tracking, and event subscription handling. The server maintains a single authenticated WebSocket session, automatically detects disconnections, and re-establishes connections with jittered backoff to avoid thundering herd scenarios.
Implements exponential backoff with jitter for WebSocket reconnection, preventing cascading failures when Home Assistant becomes temporarily unavailable
More robust than simple retry logic because it uses jittered backoff to avoid synchronized reconnection storms; maintains single persistent connection for efficiency
mcp protocol compliance and tool-calling interface
Medium confidenceImplements the Model Context Protocol (MCP) server specification, exposing Home Assistant capabilities through MCP's standardized tool-calling interface. The server handles MCP message framing, tool definition advertisement, and tool execution requests, allowing any MCP-compatible LLM client (Claude, etc.) to discover and invoke Home Assistant actions without custom integration code.
Implements full MCP server specification, allowing Home Assistant to be controlled through any MCP-compatible LLM client without custom integration per LLM provider
More portable than custom Home Assistant integrations because it uses the standard MCP protocol; works with Claude, future LLM providers, and other MCP-compatible tools
authentication and token management for home assistant api access
Medium confidenceHandles Home Assistant authentication using long-lived access tokens, managing token lifecycle and API request signing. The server stores tokens securely (via environment variables or config files), includes tokens in all Home Assistant API requests (both REST and WebSocket), and validates token permissions before executing service calls.
Uses Home Assistant's long-lived token mechanism rather than password-based auth, eliminating need to store or transmit Home Assistant credentials
More secure than password-based approaches because tokens can be revoked independently and have narrower scope; aligns with Home Assistant's recommended authentication pattern
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 hass-mcp, ranked by overlap. Discovered automatically through the match graph.
Home Assistant
** - Interact with Home Assistant to control smart home devices, query states, manage automations, and troubleshoot your smart home setup.
Homey
** - Interact with Homey to control smart home system. Supports devices, flows, and zones. Contains a few goodies for better integrations with LLMs.
Home Assistant MCP Server
Control smart home devices and automations via Home Assistant MCP.
mcp-security-hub
A growing collection of MCP servers bringing offensive security tools to AI assistants. Nmap, Ghidra, Nuclei, SQLMap, Hashcat and more.
mcp-boilerplate
A remote Cloudflare MCP server boilerplate with user authentication and Stripe for paid tools.
@mcp-contracts/cli
CLI tool for capturing and diffing MCP tool schemas
Best For
- ✓LLM application developers building Home Assistant chatbots or voice agents
- ✓Teams integrating Home Assistant with Claude or other MCP-compatible LLMs
- ✓Home automation enthusiasts prototyping natural language control interfaces
- ✓Developers building voice assistants or chatbots for home automation
- ✓Non-technical users wanting to control smart homes via natural language through LLM interfaces
- ✓Home automation teams integrating Home Assistant with AI decision-making systems
- ✓Developers building extensible Home Assistant LLM integrations
- ✓Teams wanting to support custom Home Assistant add-ons without MCP code updates
Known Limitations
- ⚠Read-only for state queries — does not support filtering or complex queries beyond entity ID lookup
- ⚠Requires network connectivity to Home Assistant instance; no local caching of state history
- ⚠MCP protocol overhead adds ~50-200ms per query depending on network latency to Home Assistant
- ⚠No built-in transaction support — partial failures in multi-device commands are not rolled back
- ⚠Service call parameters must match Home Assistant's schema exactly; no automatic type coercion
- ⚠WebSocket connection state is not persisted across MCP server restarts; requires reconnection
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.
Package Details
About
MCP server for Home Assistant (REST/WebSocket) control.
Categories
Alternatives to hass-mcp
Are you the builder of hass-mcp?
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 →