Allows controlling and querying Home Assistant, including getting entity states, listing all states, and calling any service via the Home Assistant REST API.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@hass-mcp turn on the living room light"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An open-source MCP server for controlling and querying Home Assistant.
Transport: stdio
Auth: Home Assistant long-lived token
API: Home Assistant REST API
Tools exposed:
ha_get_state — get state for an entity
ha_list_states — list all states (can be large)
ha_call_service — call any service
Related MCP server: ha-mcp
pnpm install
pnpm buildexport HASS_URL="http://homeassistant.local:8123"
export HASS_TOKEN="<your long-lived access token>"
pnpm startExample (conceptual):
{
"mcpServers": {
"homeassistant": {
"command": "npx",
"args": ["-y", "hass-mcp"],
"env": {
"HASS_URL": "http://homeassistant.local:8123",
"HASS_TOKEN": "..."
}
}
}
}Treat tokens as secrets.
Prefer running this server on the same LAN as Home Assistant.
If your HA is behind Cloudflare Access, run this MCP server on the LAN side.
MIT
Turn off all lights in an area (by area_id).
Inputs: area_id (required), transition.
Turn on all lights in an area (by area_id).
Inputs: area_id (required), brightness_pct, transition.
Call a Home Assistant service (domain/service) with data payload.
Inputs: domain (required), service (required), data.
Fetch the latest Home Assistant error logs.
Inputs: no named parameters.
Fetch history since an ISO time (optionally for an entity).
Inputs: since (required), end, entity_id, minimal_response.
Fetch logbook entries since an ISO time (optionally for an entity).
Inputs: since (required), end, entity_id.
Get Home Assistant entity state by entity_id.
Inputs: entity_id (required).
Turn off a light by entity_id.
Inputs: entity_id (required).
Turn on a light by entity_id.
Inputs: entity_id (required).
List Home Assistant areas from the area registry.
Inputs: no named parameters.
List Home Assistant devices from the device registry.
Inputs: no named parameters.
List Home Assistant entity registry entries.
Inputs: no named parameters.
List Home Assistant services and their fields.
Inputs: no named parameters.
List Home Assistant entity states (can be large).
Inputs: no named parameters.
Render a Jinja2 template and return the result.
Inputs: template (required).
Update an entity registry entry (e.g., change name, entity_id, or area_id).
Inputs: entity_id (required), new_entity_id, name, area_id.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 16 tools
Each tool has a distinct purpose with clear boundaries. Light control by area vs by entity are separate, state retrieval is split between single and list, and generic service call covers remaining operations without overlap.
All tools follow consistent ha_verb_noun pattern using snake_case, e.g., ha_area_lights_off, ha_get_state, ha_list_areas. No mixing of conventions.
16 tools is well-scoped for a Home Assistant server, covering core operations like state management, entity/area/device queries, history/logs, and template rendering without being overwhelming.
Covers all essential Home Assistant interactions: state queries, listings, light control, service calls, logs, history, and templates. Missing specific tools for common entities like switches or covers, but the generic ha_call_service fills gaps.
A TypeScript MCP server for Home Assistant, enabling programmatic management of entities, automati…
