Smart home owners will soon be able to control devices connected to Google Home through an AI agent. On Wednesday, Google rolled out early access to its Model Context Protocol (MCP) servers for the Google Home ecosystem. This allows AI agents that support MCP (such as Claude, Hermes, OpenClaw, ChatGPT, and Google Antigravity) to securely interact with smart home devices and access event history.
With this update, users will be able to use natural language commands to get an overview of their cameras, monitor smart home activity, control connected devices, build their own custom smart home dashboards, and more.
To set up the connection, users must create a Google Cloud project and configure it to use the Home MCP. Next, provide the MCP configuration details to the agent of your choice and ask them to set it up. The agent will then ask you to sign in and grant permissions. (Setup guides are also available at the Google Home Developer Center.)
The system supports any device in the Google Home ecosystem, including Google Nest doorbells and “Works with Google Home” (or Matter) devices such as thermostats and light bulbs.
Google already supports MCP in other areas of its business, including Google Cloud, Data Platform, Developer Tools, and Google Workspace. Support for Google Home is targeted more directly at consumers experimenting with AI agents designed to handle everyday tasks.
The company says access to MCP will roll out to paying Google Home Premium Advanced subscribers in the U.S. starting today and will continue over the coming weeks. This is a more expensive $20/month subscription tier that offers features such as a longer event-based video history, descriptive notifications and detailed alerts, tools to search your video history, and daily summaries.
Google has not commented on whether or when MCP will be rolled out more broadly, including to other subscription tiers and markets.
Google is also soliciting feedback from early adopters during this period through its smart home community for developers.
A previous version of this post incorrectly stated the start of the rollout. Today is Wednesday, not Tuesday.
If you make a purchase through links in our articles, we may earn a small commission. This does not affect editorial independence.
