Google Home opens its MCP server to any AI agent
Google Home just opened its MCP server, which means any MCP-compatible AI agent — Claude, ChatGPT, OpenClaw, Google's own Antigravity — can now read your home's event history, control your devices, and build its own dashboards for them. The rollout landed as early access this week for Google Home Premium Advanced subscribers in the US, and the setup guide is already live in Google's Home developer docs. Google would not say when or whether the integration reaches other subscription tiers or markets.
What the agent actually gets is broader than turning lights on. The Home MCP server exposes tools that let a model inspect home structure, query real-time device state, pull historical events, and issue control commands. In practice that means cross-camera analysis — asking your agent what your kid did when they got home from school — or digging through device state history to count how many loads of laundry ran last week. Devices can also answer back through the system: an agent that finishes a long task can push an audio message out of a Google Home speaker, and it can assemble a custom dashboard to run the house from.
Setup is not plug-and-play, and that is the interesting part. You create your own Google Cloud project, enable the Home API, configure an OAuth client, then hand the MCP configuration to your agent and walk through a consent flow that grants it access to a specific home structure. Familiar-faces data — the identity layer behind Nest camera alerts — requires a second, separate consent. Access is per-home and revocable, which is the right shape for a permission model; whether agents honor it cleanly once they hold the keys is the open question.
That question is not hypothetical. MCP has been the fastest-spreading agent standard of the year, and the hard problems have been identity and provenance: proving which agent asked for what, on whose behalf, with what scopes — the plumbing problem we wrote about in August. Google is now pushing that untested permission layer into a device class where a bad tool call opens a front door lock instead of deleting a draft. The upside is real: a system that reasons across cameras, thermostats and appliances is meaningfully more useful than one that answers "I'm sorry, I can't do that." The cost is that your home's activity log becomes an input to a model whose provider you chose, with its own retention and training policies — none of which Google controls.
Worth knowing if you have not met the protocol yet: our explainer on what MCP actually is covers the client-server split in plain English, and it is the right primer before you hand a cloud project's OAuth credentials to an agent.
What to watch: whether Google widens Home MCP beyond Premium Advanced, and whether it publishes audit tooling for what agents did in your house — a scoped, logged, revocable trail is the difference between an assistant and an unknown roommate.
Would you give an AI agent write access to your smart home, or is the read-only version the only sane default? Tell us in the comments.
Sources: The Verge · TechCrunch · Google Home Developers — Home MCP server · Techmeme
