Google Home opens up to Claude and other AI agents

Google has done something it has never done before: it has handed rival AI assistants the keys to your smart home. The company's Home developer platform now lists Home MCP in early access, a connector that lets a personal AI agent see the rooms and devices in a home, read their current state and issue commands on a person's behalf. Google's own documentation names Google's Antigravity, the open-source Open Claw and Anthropic's Claude as the sort of agent it has in mind. Until this week, talking to a Google Home meant talking to Google.

What has Google actually opened up?

Home MCP is a server built on the Model Context Protocol, the standard Anthropic published in 2024 and which most of the industry has since adopted for plugging AI models into tools and data. Google's wording on the developer site is unusually plain about the pitch: Home MCP "lets personal agents interact with your smart home safely" and bridges "your smart home with the rest of your life, connecting rooms and devices to a personal agent like Antigravity, Open Claw, and Claude". The programme is labelled early access, and Google has not said which countries are in the first wave.

What can an agent actually do with a house?

Four things, according to Google's documentation. Entity enumeration, which is how an assistant answers "how many lights do I have in my house?" by listing every room and device it can see. Real-time state monitoring, so it can tell you whether the front door is locked or a camera has dropped offline. Device control, described as "parameterized actions and mutations", which is the machinery behind "turn off all the outside lights". And historical analysis, where the agent reads past states and chronological event logs to answer questions such as what happened while you were out.

Is it safe to hand a stranger's assistant the keys?

Google says access runs through a user-authorised OAuth flow, and that the connector is "designed to meet Google's security and privacy standards so agents can't take sensitive actions on your behalf." That sentence is doing a lot of work. Google is promising both granular permission and a hard wall around whatever it considers sensitive, but its documentation does not yet say which actions fall on the wrong side of that wall, and nobody outside Google has tested the boundary. An agent that can read a home's event history is also an agent that knows when nobody is in it.

What is in it for developers?

The second half of the launch is less glamorous and more immediately useful. Home Developer MCP is a companion server aimed at coding tools rather than consumers: it indexes Google Home API references, Matter specifications and OpenThread documentation, and Google says it works with its own Antigravity suite as well as Claude Code, Cursor and GitHub Copilot in VS Code. If you have ever watched a coding assistant confidently invent a Google Home API call, this is aimed squarely at that afternoon.

Why does one connector matter this much?

Because MCP is a small piece of plumbing with an outsized effect. Think of it as a standard socket: once a service exposes one, any agent that knows how to plug in can use it, without two companies building a bespoke integration for each other. That is why this matters well beyond the smart home. A company that spent a decade keeping its assistant, its speakers and its devices in a closed loop is now describing its home ecosystem as an open surface, which is the same opening-up Meta made on messaging when WhatsApp started supporting MCP for business. The practical upshot is that the assistant you prefer may soon be the one dimming the hallway, rather than the one Google ships.

Our opinion

Opening the ecosystem is the right call, and it is a bigger deal than the old "works with Google Home" badge ever was. That badge meant a device could be controlled from a Google app. This means someone else's agent can reason over your home — noticing the pattern in when the lights go on, answering questions you would otherwise have to piece together in an app, and being useful while you are not holding your phone. That is a genuinely better product, and Google deserves credit for not keeping it to itself. The caveat is just as obvious. An agent holding OAuth to your house is a credential worth stealing, and the difference between "turn the lights off" and "unlock the front door" is exactly the line Google has left vague. The interesting question is not whether Home MCP works. It is what Google decides is too sensitive to hand over, and how quickly early access stops being early. Watch that boundary, not the demo.