radiant python
Hey all 👋 I wanted to float an idea / feature suggestion for Nabu Casa and get a sense if this resonates with others.
With the rise of AI / agent integrations (e.g. ChatGPT Apps SDK, MCP servers, etc.), there’s a growing desire to connect AI tools directly to Home Assistant — for querying state, debugging, automation assistance, etc.
The problem today is that:
- Every HA Cloud user has a unique
*.ui.nabu.casaURL - Most AI app platforms require a single fixed public endpoint per integration
So third-party devs are either forced to:
- Ask users to paste their Nabu Casa URL + long-lived token (bad UX + security risk), or
- Run their own proxy + store credentials (also not great).
Suggestion:
It feels like Nabu Casa is uniquely positioned to solve this cleanly by offering a first-party, cloud-hosted MCP / AI endpoint, e.g.:
https://mcp.nabucasa.com/mcp
This would:
- Authenticate users via their Nabu Casa account,
- Route requests to the correct HA instance internally,
- Enforce permissions centrally,
- And avoid users ever sharing URLs or tokens with third parties.
From a user POV this becomes:
👉 “Connect Home Assistant to ChatGPT / AI tools” → log in → done.
From a platform POV:
- Nabu Casa already runs the remote access proxy + identity layer,
- Already has subscriptions and trust,
- And can define the security / privacy model properly instead of letting a dozen unofficial proxies appear.
I’m not asking for this now, just curious:
- Would others find this useful?
- And does this feel like something that fits naturally into HA Cloud / the Nabu Casa roadmap?
Would love thoughts from users, devs, or the Nabu Casa team 🙏
