Provides comprehensive control over Home Assistant instances, including entity management, registry operations, automation debugging, and retrieval of historical statistics and system logs.
Supports monitoring and debugging of the MQTT integration within Home Assistant, enabling searches for related entities and access to integration-specific debug logs.
Hass-MCP-Plus
A complete rewrite of voska/hass-mcp — an MCP server for Home Assistant built for token efficiency, security hardening, and context flooding prevention. Thanks to Matt Voska for the original project.
Features:
24 tools covering entity control, registry management, statistics, logs, and automation debugging
CEL expression filtering for complex entity queries (e.g., "all battery sensors below 20%")
Entity registry management with safe two-phase delete
Long-term statistics with hourly/daily/weekly/monthly aggregation and date range support
Core journal log access with debug-level and integration filtering
Automation trace inspection for debugging failed runs
Configurable output formats (lean/compact/detailed)
Input validation, error sanitization, and context flooding prevention across all calls
Works with Claude Desktop, Claude Code, Cursor, and other MCP clients
Installation
Prerequisites
Home Assistant instance with a Long-Lived Access Token
One of the following:
Docker (recommended)
Python 3.13+ and uv
Environment Variables
Variable | Required | Description |
| Yes | Home Assistant URL (e.g., |
| Yes | Home Assistant Long-Lived Access Token |
| No | Set to |
| No | Timezone (e.g., |
Docker (Recommended)
docker pull rmaher001/hass-mcp-plus:latestVerify the server starts correctly:
docker run -i --rm \
-e HA_URL=http://homeassistant.local:8123 \
-e HA_TOKEN=YOUR_LONG_LIVED_TOKEN \
rmaher001/hass-mcp-plusNote: If Home Assistant is running on the same machine, use
http://host.docker.internal:8123(Docker Desktop on Mac/Windows) or add--network hostand usehttp://localhost:8123.
Python (uv/uvx)
pip install hass-mcp-plusRun the server:
HA_URL=http://homeassistant.local:8123 HA_TOKEN=YOUR_LONG_LIVED_TOKEN uvx hass-mcp-plusClient Configuration
claude mcp add hass-mcp-plus \
-e HA_URL=http://homeassistant.local:8123 \
-e HA_TOKEN=YOUR_LONG_LIVED_TOKEN \
-- docker run -i --rm -e HA_URL -e HA_TOKEN rmaher001/hass-mcp-plusReplace YOUR_LONG_LIVED_TOKEN with your actual token and update HA_URL.
Open Claude Desktop → Settings → Developer → Edit Config
Add to
claude_desktop_config.json:
Using Docker:
{
"mcpServers": {
"hass-mcp-plus": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"HA_URL",
"-e",
"HA_TOKEN",
"rmaher001/hass-mcp-plus"
],
"env": {
"HA_URL": "http://homeassistant.local:8123",
"HA_TOKEN": "YOUR_LONG_LIVED_TOKEN"
}
}
}
}Using uvx:
{
"mcpServers": {
"hass-mcp-plus": {
"command": "uvx",
"args": ["hass-mcp-plus"],
"env": {
"HA_URL": "http://homeassistant.local:8123",
"HA_TOKEN": "YOUR_LONG_LIVED_TOKEN"
}
}
}
}Replace
YOUR_LONG_LIVED_TOKENwith your actual token and updateHA_URLto match your Home Assistant instanceSave and restart Claude Desktop
Go to Cursor Settings → MCP → Add New MCP Server
Fill in the form:
Name:
Hass-MCP-PlusType:
commandCommand:
docker run -i --rm -e HA_URL=http://homeassistant.local:8123 -e HA_TOKEN=YOUR_LONG_LIVED_TOKEN rmaher001/hass-mcp-plus
Replace
YOUR_LONG_LIVED_TOKENwith your actual token and updateHA_URLClick "Add" to save
Usage Examples
Here are some examples of prompts you can use with Claude once Hass-MCP-Plus is set up:
"What's the current state of my living room lights?"
"Turn off all the lights in the kitchen"
"Find all battery sensors below 20%"
"Give me a summary of my climate entities"
"Show me the hourly temperature statistics for the last week"
"Why didn't my motion sensor automation fire last night?"
"List all unavailable or unknown entities"
"Disable the orphaned sensor that no longer exists"
"Show me the debug logs for the MQTT integration"
"Search for entities related to my living room"
Available Tools
Hass-MCP-Plus provides 24 tools for interacting with Home Assistant:
Entity Management
get_entity: Get the state of a specific entity with optional field filteringentity_action: Perform actions on entities (turn on, off, toggle) with domain-specific parameterslist_entities: Get entities with domain filtering, search, and output format options (lean/compact/detailed)search_entities: Search for entities matching a query string across IDs, names, and attributesquery_entities: Filter entities using CEL expressions with numeric comparisons and boolean logicdomain_summary: Get a summary of a domain's entities with state distribution and examplessystem_overview: Get a comprehensive overview of the entire Home Assistant system
Entity Registry
get_entity_registry: Get detailed registry entry for a single entity (platform, device, area, status)list_entity_registry: List all registry entries with optional domain filter (for auditing and bulk management)update_entity: Update entity properties — rename, change icon, assign area, disable/enable, hide/unhideremove_entity: Remove an entity from the registry (requires explicitconfirm=Trueflag)
Automation & Debugging
list_automations: Get all automations with pagination supportlist_automation_traces: Get recent execution traces for a specific automationget_automation_trace: Get detailed trace for a specific automation run (trigger, conditions, actions, errors)get_error_log: Get the Home Assistant error log with integration/level filteringget_core_logs: Get core journal logs (DEBUG/INFO/WARNING/ERROR) with integration/pattern filteringset_log_level: Set log level for any integration (enable debug logging, then read withget_core_logs)
Historical Data
get_history: Get raw state change history with automatic pagination and samplingget_history_range: Get state changes for a specific date/time range with sampling strategiesget_statistics: Get aggregated statistics (mean, min, max) with configurable periods (5min/hour/day/week/month)get_statistics_range: Get long-term statistics for any date range — the best tool for historical analysis
System
get_version: Get the Home Assistant versioncall_service: Call any Home Assistant service (low-level API access)restart_ha: Restart Home Assistant
Development
Running Tests
uv run pytest tests/ -vLicense
Resources
Looking for Admin?
Admins can modify the Dockerfile, update the server description, and track usage metrics. If you are the server author, to access the admin panel.