Best for
- Home Assistant users who want AI-assisted configuration and maintenance
- Users who need automation debugging, history queries, and system-management capabilities
- Users running Home Assistant OS, Supervised, Container, or Core
An unofficial, community-maintained Home Assistant MCP server covering device control, configuration, diagnostics, and system management. It is powerful but can require high-impact permissions; start with the custom component and enable beta file/YAML tools cautiously.
Strongest · Documentation 16/20 Weakest · Reliability 8/20
Test out of dateListed 2026-07-29
Read the FMRS scoring method →Runtime:Python · Docker · Hosted (no local runtime)
HOMEASSISTANT_TOKEN
A Home Assistant long-lived access token created from your HA user profile page; a secret credential.
HOMEASSISTANT_URL
Your Home Assistant instance URL, e.g. http://<ha-host>:8123; needed for stdio/Docker installs.
ENABLE_TOOL_SEARCH
Set to true to enable search-based tool discovery instead of listing the full catalog — useful for small/local models.
TOOL_SEARCH_MAX_RESULTS
Max results returned by ha_search_tools, default 5, range 2–10.
PINNED_TOOLS
Comma-separated tool names that stay always visible instead of being deferred behind search.
ENABLE_BETA_FEATURES
Master flag that must be on before filesystem/YAML beta sub-flags take effect.
HAMCP_ENABLE_FILESYSTEM_TOOLS
Feature flag enabling beta filesystem tools like ha_write_file and ha_read_file.
The preferred method is to install the HA-MCP Custom Component through HACS in Home Assistant, restart Home Assistant, add the HA-MCP Server integration, then copy the connection URL from its Configure screen into the AI client. Other options include the Home Assistant app/add-on, Docker, or PyPI/uvx. Configure only one installation method per client. File and YAML tools require the separate HA-MCP File & YAML Tools entry and the relevant beta feature flags.
After connecting, check that tools like ha_search or ha_get_overview appear in your client's tool list, then ask the AI "Can you see my Home Assistant?" — a returned system overview confirms the connection works.
Once connected, you can ask your AI assistant things like:
No matching tools
Listed from the project's documentation, not tested by this site.
HA-MCP is a comprehensive Model Context Protocol server that lets AI assistants interact with Home Assistant using natural language. It supports smart-home device control, state queries, service calls, and management of automations, scripts, scenes, dashboards, helper entities, areas, backups, and diagnostics. It is community-maintained and licensed under MIT.
Manage your Hevy workout data from AI assistants via MCP.
Firecrawl's official MCP server for web search, scraping, and structured extraction for AI agents
One binary. One grammar. Evidence from the biomedical sources you already trust.
Encrypted, fully offline long-term memory for AI agents
Source revision 874aa48726c0 Data synced 2026-10-19 Read the FMRS scoring method