Google Home MCP: Any AI Agent Can Now Run Your House
Google opened Google Home's MCP server on September 16, 2026, letting Claude, ChatGPT, and other agents control your devices. Here's the setup.
On September 16, 2026, Google opened early access to Home MCP — a Model Context Protocol server that lets any MCP-capable AI agent read and control your Google Home devices. If your agent speaks MCP, your lights, thermostat, doorbell and camera history are now things it can act on instead of just talk about.
This is the most consumer-facing MCP release so far. Until now the protocol mostly reached developers and enterprise data; here it lands on the devices in your hallway, and the roll-out is gated in a way worth understanding before you get excited.
What Home MCP actually gives an agent
TechCrunch reported that the server lets agents work with smart home devices and access event history. In practice, that means an agent can:
- Review your camera summaries and monitor smart home activity
- Control connected devices — lights, thermostats, and anything "Works with Google Home" or Matter
- Build custom smart home dashboards from the same data
The device coverage is broad rather than exotic: Google Nest doorbells and thermostats, plus third-party Matter devices such as light bulbs.
Who can use it, and who is locked out
This is the part headlines skip. Access is not open to everyone who owns a Nest device.
| Question | Answer |
|---|---|
| Which agents work? | Any MCP-capable agent — Claude, ChatGPT, Hermes, OpenClaw and Google Antigravity were named at launch |
| Which accounts? | Subscribers to Google Home Premium Advanced in the US |
| Which tier is that? | The $20/month tier with longer event-based video history, descriptive notifications and video-history search |
| Wider rollout? | Google would not comment on if or when it expands to other tiers or markets |
| Still rolling out? | Yes — access began September 16 and continues over the coming weeks |
So if you are on a free Google Home account or a lower tier, this is a preview of something you cannot use yet. Google has not said when that changes.
How to set it up
The setup is developer-shaped, which is the honest trade-off for a first release. According to TechCrunch, you:
- Create a Google Cloud project and configure it to use Home MCP.
- Give the MCP configuration details to your agent of choice and ask it to set it up.
- Sign in and grant permissions when the agent prompts you.
- Test with something harmless first — reading a device state — before you let it change anything.
Google says a setup guide is offered in the Google Home Developer Center, and it is soliciting feedback from early adopters through its Smart Home for Developers community.
The honest caveats
An agent that can change your thermostat is an agent that can be wrong at 3am. Home MCP grants read and write access. A model that misreads an instruction can adjust a lock, a temperature or a schedule. Before you connect anything, decide what the agent may do unattended and what needs your approval — the same discipline we describe in get your AI agent to ask before acting.
MCP access is a new door into your home network. You are creating a Google Cloud project and configuring credentials for an agent to use. Treat that credential like a house key: know which agent holds it, and revoke it when you stop using that agent. Our walkthrough of MCP and what it exposes covers the permission model.
Your camera history is sensitive data. An agent that can search your event history can also summarize it into a chat log. Deciding where that conversation lives — cloud or your own machine — is a real privacy decision, and it is exactly the fork we compared in local-first vs cloud AI assistant.
Which agents can drive Google Home through Home MCP, and what each step of setup unlocks
Where this is heading
Home MCP is not really a smart home story. It is another data point in the year's clearest pattern: anything with an API is becoming something an agent can drive. Google already supports MCP across Cloud, developer tools and Workspace; the smart home is the first place it touches ordinary people directly. If you want a local agent doing the same job without a subscription, our local agent on your smart home guide is the other route.
If you would rather run an agent that owns this kind of control on your own machine, start at wolffi.sh/start#control — permissions and connectors first, then the fun part.
The takeaway
Home MCP makes your house addressable by any agent that speaks the protocol, which is genuinely useful and genuinely consequential at the same time. If you qualify — US, Premium Advanced tier — set it up this month, but start read-only and give it a device you can live without. If you do not qualify, the important takeaway is unchanged: the protocol won, and the same integration will reach the rest of your devices soon enough. Decide what you are comfortable letting an agent touch before the switch is in front of you.
