Home Assistant MCP Server
Home Assistant MCP server enabling AI agents to interact with Home Assistant smart home platform — querying entity states (lights, switches, sensors, climate), controlling devices, executing automations, reading history, and integrating Home Assistant's home automation capabilities into agent-driven smart home control and monitoring workflows.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
HTTPS recommended. Long-Lived Token auth (no scope granularity). Community MCP. Protect token. Configure SSL. Device control affects physical environment — use with appropriate caution.
⚡ Reliability
Best When
An agent needs to control or monitor Home Assistant devices — for smart home automation, voice control integration, or home energy monitoring.
Avoid When
You're not running Home Assistant, or if you need industrial IoT/SCADA integration rather than residential smart home control.
Use Cases
- • Querying sensor readings and device states from home monitoring agents
- • Controlling lights, switches, and thermostats from home automation agents
- • Executing Home Assistant automations from voice assistant agents
- • Reading energy usage and environmental data from efficiency monitoring agents
- • Getting historical sensor data from trend analysis agents
- • Managing smart home schedules from scheduling agents
Not For
- • Teams not running Home Assistant (standalone IoT platforms need different MCPs)
- • Industrial IoT or commercial building management systems
- • Production critical control systems (home automation, not industrial safety)
Interface
Authentication
Home Assistant Long-Lived Access Token from user profile. Token grants access based on HA user permissions. Local or remote HA instance accessible. Nabu Casa cloud access also possible.
Pricing
Home Assistant is open source and completely free to self-host. Nabu Casa cloud subscription is optional for remote access. Community MCP server is open source and free.
Agent Metadata
Known Gotchas
- ⚠ Entity IDs are HA-specific (domain.entity_name format) — must be discovered from HA
- ⚠ Service calls have different payloads per domain — agents must know domain-specific services
- ⚠ Device control has real-world effects — agents must exercise caution with home devices
- ⚠ Home Assistant version affects available entities and services
- ⚠ Local access requires HA to be reachable — remote access needs Nabu Casa or port forwarding
- ⚠ Community MCP server — covers core REST API but not all HA capabilities
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Home Assistant MCP Server.
Scores are editorial opinions as of 2026-03-06.