HA-MCP — Watchlist | MCP100 Index

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track Home Assistant API and beta-tool changes that affect home automation actions

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Connecting AI clients to Home Assistant state and service actions.

What we know

HA-MCP connects AI clients to Home Assistant so they can inspect home state and invoke exposed Home Assistant services. Optional file/YAML tools are available.

Maintenance / activity evidence

Observed Oct 5, 2026 (UTC)chore(internal): sync ratchet baselines after merge [skip ci]

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Can read home state and invoke exposed services; optional file/YAML tools can extend access. Writes: Invoke Home Assistant services; Optional file/YAML modification depending on enabled tools.
Deployment-specific Home Assistant authentication.
Sensitive access: Home automation state, Devices, Potential local configuration files

Home Assistant service access can control physical devices; optional file/YAML tooling further expands local authority.

Security source · repository notice ↗Security source · policy file ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

4,959 repository stars · 229.7k package downloads / 30 days

Stars observed Oct 6, 2026. Downloads observed Oct 6, 2026.

All limitations / Review context

Has the beta status or tool permission model for Home Assistant changed?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

Home Assistant service access can control physical devices; optional file/YAML tooling further expands local authority.
Can read home state and invoke exposed services; optional file/YAML tools can extend access.
Deployment-specific Home Assistant authentication.
Home state and service payloads pass between the AI client and Home Assistant.
Reviewed write actions: Invoke Home Assistant services; Optional file/YAML modification depending on enabled tools
Sensitive access: Home automation state, Devices, Potential local configuration files
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No independent runtime, installation, or comprehensive security audit was performed.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
This repository is not under the official Home Assistant organization.
File/YAML tools are opt-in and materially expand access.
The project documents known stdio limitations.

Original activity observations

2026-10-05T15:21:35Z: chore(internal): sync ratchet baselines after merge [skip ci]

Technical identity

github.com/homeassistant-ai/ha-mcp

Exact implementation source: https://github.com/homeassistant-ai/ha-mcp ↗
Reviewed resource type: MCP Server
Repository identity: homeassistant-ai/ha-mcp
Package identity: pypi:ha-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
homeassistant-ai/ha-mcp
Recorded repository material and project history.
Evidence source ↗
pypi.org/project/ha-mcp/
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 13, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher-specific setup path. Follow prerequisites, then register or connect to your MCP host.
Connection / UI instruction · Publisher instructions · Review before use
```
In HACS add custom integration repository https://github.com/homeassistant-ai/ha-mcp-integration, install HA-MCP Custom Component.
```
Configure / authenticate
Publisher instructions
Restart Home Assistant, Settings > Devices & Services > Add Integration > HA-MCP Custom Component > HA-MCP Server.
Check connection
Suggested check
Use host MCP connector tool discovery and ask if it can see your Home Assistant; do not toggle devices as a test.
Remove / uninstall / revoke
MCP100 setup guide
Remove HA-MCP connector from MCP client and remove the HA-MCP integration in Home Assistant if no longer wanted.
MCP100 client-scope guidance: each CLI removal example targets only its named client and exact registered entry. Package names, Desktop/Cursor configuration keys and Codex/Claude registration names may differ; use the entry you actually registered. Client removal does not revoke provider credentials.
claude mcp remove ha-mcp

Official Documentation & Sources

What it does

HA-MCP connects AI clients to Home Assistant so they can inspect home state and invoke exposed Home Assistant services. Optional file/YAML tools are available.

Capability: Productivity & Collaboration
Resource type: MCP Server
Best fit: Connecting AI clients to Home Assistant state and service actions.

Representative uses

Read Home Assistant state
Invoke Home Assistant services
Use optional file/YAML tools
Connect through HTTP or local deployment

Limitations

This repository is not under the official Home Assistant organization.
File/YAML tools are opt-in and materially expand access.
The project documents known stdio limitations.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Deployment-specific Home Assistant authentication.
Permissions: Can read home state and invoke exposed services; optional file/YAML tools can extend access.
Data handling: Home state and service payloads pass between the AI client and Home Assistant.
Cost: free
Risk and cautions: Home Assistant service access can control physical devices; optional file/YAML tooling further expands local authority.

Access scope and cautions

Write actions: Invoke Home Assistant services Optional file/YAML modification depending on enabled tools
Sensitive access: Home automation state Devices Potential local configuration files
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Read Home Assistant state; Invoke Home Assistant services; Use optional file/YAML tools; Connect through HTTP or local deployment.

What authentication is documented?

Home Assistant/deployment-specific.

Can it modify data or perform write operations?

Documented write actions include: Invoke Home Assistant services; Optional file/YAML modification depending on enabled tools. Recorded permission boundary: Can read home state and invoke exposed services; optional file/YAML tools can extend access.

What data-handling boundary should I consider?

Home state and service payloads pass between the AI client and Home Assistant. Recorded sensitive-access context: Home automation state; Devices; Potential local configuration files.

What limitations and risks should I check before use?

Home Assistant service access can control physical devices; optional file/YAML tooling further expands local authority. This repository is not under the official Home Assistant organization. File/YAML tools are opt-in and materially expand access. The project documents known stdio limitations. No independent runtime, installation, or comprehensive security audit was performed.

Is this an official MCP?

homeassistant-ai is listed as Community implementation in MCP100’s current evidence.