Provides tools for interacting with a Home Assistant instance, including entities, areas, devices, services, automations, scripts, history, add-ons, and system.
Click on "Install 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., "@mcp-ha Which lights were left on in the house?"
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.
This Home Assistant add-on exposes an MCP (Model Context Protocol) server. In practice: you connect Claude, Gemini or any other MCP client to your instance, and you talk to your home.
"Which lights were left on?", "Why didn't the heating automation trigger last night?", "Plot my energy usage for the week."
Documentation: devitek.github.io/mcp-ha (English and French)
Domain | Tools |
Entities, areas, devices | fuzzy search, paginated lists, full details |
Services | catalog per domain, search, guarded call (opt-in) |
Automations | list, state, last trigger, full configuration |
Scripts | list, running state |
History | state changes, long-term statistics, logbook |
Add-ons | list and details (read) |
System | Jinja template rendering, HA config, error log |
16 tools in total, designed to save the LLM context window: compact, paginated and capped responses, with notes that steer the assistant towards more precise queries.
Related MCP server: hass-mcp
It exists and works, but it goes through the Assist API: only entities exposed to Assist, no history, no registries, no add-ons, no automation configs. This add-on gives direct, granular access. Both can coexist.
Requirements: Home Assistant OS or Supervised (the add-on needs the Supervisor).
Add this repository to your add-on repositories:
Or manually: Settings, Add-ons, Add-on store, three-dot menu, Repositories, then paste https://github.com/Devitek/mcp-ha.
Install "MCP Home Assistant" and start it.
Open the add-on Configuration tab: an API token was generated and saved there on first start (it is also printed in the add-on log).
Claude Code:
claude mcp add --transport http home-assistant \
http://HA_IP:9583/mcp \
--header "Authorization: Bearer YOUR_TOKEN"Claude Desktop and Gemini CLI: see the clients guide on the documentation site.
Read only by default. The service-call tool does not even exist for the client unless you enable allow_write.
Defense in depth when writes are enabled: denylist of dangerous services (HA shutdown, shell_command...), glob allow/deny lists for entities, dry_run mode, JSON audit trail of every attempt in the log.
LAN only. No TLS, no OAuth: do not expose port 9583 to the internet.
The full threat model is in SECURITY.md.
Documentation site: installation, configuration, clients, tool reference, architecture (English and French)
Add-on documentation: the page shown in the HA interface
Contributing guide: dev setup, conventions, releases
Repository issues: the project knowledge base, every design decision and pitfall is tracked there with the décision and écueil labels (in French)
This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Personal assistant MCP server with search, execute, packages, jobs, secrets, and integrations.
A TypeScript MCP server for Home Assistant, enabling programmatic management of entities, automati…
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Devitek/mcp-ha'
If you have feedback or need assistance with the MCP directory API, please join our Discord server