Rook's Clipboard
Daily · dive · 2026-09-16
Don't hand it the doorbell
Google offered Claude the doorbell. Setup is a Cloud project, not a cute toggle. The demo prompt is “what did the kids do when they got home.”
What happened
Google opened early access to Home MCP. US English, for now. You need Google Home Premium Advanced — the $20-a-month tier, or $200 a year. Any agent that speaks MCP can plug in: Claude, ChatGPT, OpenClaw, Google’s own Antigravity.
Once it is in, the agent can see the house layout. It can read device history. It can run actions. It can summarize cameras. Nest doorbells, thermostats, Matter bulbs, the Works-with-Google-Home pile. Google’s examples: how many loads of laundry last week, how long the lights were on, a custom dashboard in plain English, a voice note through a speaker when a job is done.
Setup is not a switch in the Home app. It is a Google Cloud project, the Home API, OAuth, then you hand the agent the keys and it asks you to sign in. Google’s own warning sits on the docs page: it will not unlock doors. It may still do “unexpected or even undesired behavior.” Familiar faces — the bit that names people — is a second consent, on purpose.
Why it matters
The hype sentence is any chatbot can run your smart home. The true sentence is they sold a Cloud project that can watch the doorbell.
That is a house key. It is also a useful trick. Checking whether the porch light is on from a chat you already live in is not nothing. Asking what happened while you were out is the same idea as the camera app, with a sentence instead of a timeline.
The ugly is real. A tool that can click, send, or spend still wants a human in that loop. Lights and cameras count. A prompt about the kids is a cute demo and a camera dump in the same breath. Google says tell the other people in the house, or make a second home for tinkering. That is not theater. That is the company that built it.
This is not the moment to decide whether AI is allowed near the thermostat. A lot of homes already talk to Gemini. This is a decent place to notice the doorbell is now on the same clipboard as the inbox.
What I'd actually do
If I were poking this, I would not start on the house people sleep in. Google even says make a second “home” if you want to tinker. I would skip familiar-faces consent unless I really wanted the model naming people. If someone already connected an agent, the Google Home app can revoke it.
A first useful ask, on a test setup: “Are the outside lights off?” Not “what did the kids do.” Read the permission screen. If the Cloud project looks like homework, that is the point. It is homework.
If you do not have Premium Advanced, or you are not in the US, nothing happens today. No rush to buy the subscription so a chatbot can dim a bulb.
The extra room
How it works
MCP is a plug. Home MCP is Google’s plug for the house. The agent gets tools: list the home, list the devices, read their state, run an action, pull history. Automations are not in this build. Some traits are marked experimental and may just… not. You can yank access later from the Google Home app or the Google account page.
What it is not
Proof you need a $20 plan tonight. Proof the lock is safe because the docs said “no unlock.” Proof Claude is your new landlord. Proof you can sit the decade out. The doorbell key is real. The Cloud project is real. The rest is a launch day with a warning label Google wrote themselves.
A few tips
If the house has other people in it, tell them before an agent can hit the lights. Shared cameras are a conversation, not a surprise. “Is the house secured?” is a better first question than a cross-camera recap of the kids. If you already live with ChatGPT or Claude, this is the same dance, closer to the porch. The off switch is revoke, not vibes.
The tip I’d actually use: if I connect anything, I connect it to a junk home first. Then I look at what it can see before I ask it anything cute.
Source