Feasibility record — 4 October 2026
Historical documentation review. The current software first step and tested limits are in the README and verification. This record is not a fresh platform or account test.
Evidence: official documentation review only; no Grok account, HA installation, or phone was connected. Source dates below are publication/update dates where provided. Recheck at actual onboarding.
| Question | Finding and primary source | Remaining experiment |
|---|---|---|
| Existing Bot extension | Team Bots (updated Oct 2): custom MCP offers Remote HTTPS and Command, with OAuth or Bot credential for remote. Documentation is strongest for Team Bots. | Confirm the existing personal Bot exposes the same setup and can discover tools. Do not create a different developer-API conversation. |
| Process location | Overview (updated Sep 21): persistent cloud computer; account Bots share its filesystem. A local Mac path is unavailable there. Team Bot conversations use owner/teammate/shared cloud computers according to context. | Record actual computer and network reachability; Command installed on cloud requires its own reachable HA URL. |
| Home authentication/hosting | HA MCP (retrieved Oct 4): stateless Streamable HTTP, /api/mcp; selected LLM API, exposed entities, bearer token or OAuth. OAuth uses URL client IDs, not RFC7591 registration. |
Confirm Grok supports HA's URL client ID and callback scheme/domain. No exact Grok callback/client ID is documented in the reviewed material. Remote HTTPS must be authenticated and reachable by cloud. No tunnel created. |
| Mobile | Mobile (updated Sep 21): same Bots/connectors/cloud computer on iOS, iPadOS, Android; advanced setup can require desktop. Push rollout is account dependent. | Record desktop/iOS/Android versions and real tool calls. Documentation parity is not verification. |
| Outside events | Routines (updated Sep 14): supported integrations may trigger routines, e.g. Slack/GitHub. HA MCP docs explicitly exclude notifications and sampling. | Arbitrary HA button/webhook wake into the existing Bot is not established. Polling/event retention in gadget gateway is distinct from Bot wake or mobile push. |
The reviewed Grok pages contain Cursor references. This report preserves their stated cloud/client behavior without treating branding or documentation alone as account-level evidence.
Decision: reuse Home Assistant's MCP server directly for its exposed Assist capabilities. A second server would duplicate authentication, entity exposure, and actions. This repository supplies discovery diagnostics, fixtures, and an onboarding recipe. No adapter is currently required. If real onboarding reveals a gap, capture the exact failure before designing one.
Upstream code reference: integration setup, retrieved Oct 4. dev is moving evidence, not a pinned tested installation. This repository does not vendor HA code.
Limits: entity/vendor capability coverage depends on Assist and the selected API. Listing a tool or receiving an action result is not proof of physical effect. Resource snapshots are observations, not durable event streams. No universal household compatibility, unsolicited Bot messaging, push-button wake, or Grok certification is claimed.