# homeassistant-ai/ha-mcp

Source: [GitHub](https://github.com/homeassistant-ai/ha-mcp)  
Feed7 permalink: https://feed7.dev/p/ha-mcp-0lusv8w  
Published: Unknown  
Trust: Needs Review (needs_review)

## Why Included

HA-MCP’s in-process Home Assistant integration supports MCP clients across installation types. Its setup requires choosing one server method and deciding how clients can connect.

## Source Summary

HA-MCP recommends its Home Assistant integration, which runs the server in-process and supports OS, Supervised, Container, and Core installations. It requires **Home Assistant 2026.8.0 or newer**; the built-in Marketplace is available from **2026.11**. In **v7.3.0**, the YAML-setting tool moved to beta.

## Practical Implication

For an agent workflow, choose one server install and configure that URL in the client. Remote webhook and local network access start disabled; the docs suggest starting remote access with a secret URL, or keeping it off for local-only use. The optional file and YAML editing tools are off by default.

## Agent-Ready Context

HA-MCP recommends its Home Assistant integration, which runs the server in-process and supports OS, Supervised, Container, and Core installations. It requires **Home Assistant 2026.8.0 or newer**; the built-in Marketplace is available from **2026.11**. In **v7.3.0**, the YAML-setting tool moved to beta.

For an agent workflow, choose one server install and configure that URL in the client. Remote webhook and local network access start disabled; the docs suggest starting remote access with a secret URL, or keeping it off for local-only use. The optional file and YAML editing tools are off by default.

The project warns that running multiple install methods for the same server can cause client hangs, and that stdio has known transport issues; it recommends HTTP for real setups. The secret URL acts as a credential, so the setup guidance offers a separate, local-only administrator account as a safer choice than using your own account.

## Connected Context

Feed7 judgment across 1045 accumulated Signals:

HA-MCP’s setup guidance makes deployment and access boundaries central to using an MCP tool reliably: select one server installation, prefer HTTP for real setups, and keep remote access and editing tools constrained. The candidates provide comparisons for local stateful tools and per-user authorization, but do not establish that those deployment choices transfer directly to Home Assistant.

- [pascalorg/editor](https://feed7.dev/p/editor-1ffbppp) — Both expose persistent local systems through MCP; Pascal’s one-client constraint and version drift reinforce that deployment and client compatibility are practical parts of tool setup.
- [Vercel Connect now supports TanStack AI](https://feed7.dev/p/vercel-connect-tanstack-ai-1owhrob) — HA-MCP’s secret URL and local-only account guidance address access credentials, while Vercel Connect describes a per-user OAuth consent and refresh boundary for remote MCP.
- [Everyone Gets A Software Company — Benjamin Guo, Zo Computer](https://feed7.dev/p/everyone-gets-a-software-company-benjamin-guo-zo-computer-1go8feh) — Zo’s persistent workspace illustrates the broader trade-off of co-locating tools and state; HA-MCP’s disabled-by-default remote and editing capabilities keep that exposure more bounded.

## Context Map

- Layer: tools
- Domains: None
- Topics: mcp, tool-use, coding-agents

## Uncertainty

- The project warns that running multiple install methods for the same server can cause client hangs, and that stdio has known transport issues; it recommends HTTP for real setups. The secret URL acts as a credential, so the setup guidance offers a separate, local-only administrator account as a safer choice than using your own account.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.
