Google is opening up its smart home to AI agents, letting tools like Claude and Open Claw access and control your connected devices and analyze your home’s data using the standardized Model Context Protocol.

Google Home MCP is a new integration that lets third-party AI agents control and monitor your smart home and act on your behalf. It “allows any AI agents that support MCP, including Google Antigravity, Claude, Hermes or Open Claw, to securely work with all of the devices and event history in your Google Home ecosystem,” Taylor Lehman, group product manager at Google Home & Nest, said in a blog post.

According to Lehman, Home MCP integration will connect your AI agent of choice to real-world events, enabling a host of new capabilities. From things like cross-camera analysis — so you could ask your agent what your kid did when they got home from school — to using device state history to figure out how many loads of laundry you did last week or how long the lights were left on. It will also allow your agent to interact with you via voice, for example, by sending an audio message over your Google Home speaker when it has finished a task. You can also have your agent create a custom dashboard to control your Google Home.

This doesn’t replace Google’s new Gemini for Home assistant, which remains Google’s interface for interacting with Google Home through the Home app and Google Nest smart speakers, following the demise of Google Assistant. Instead, MCP integration adds another layer of control, allowing third-party AI agents to interact directly with devices connected to Google Home through their own interfaces.

At launch, availability is limited to Google Home Premium Advanced users in the US ($20/month or $200/year), with access rolling out in the coming weeks. Setup requires creating a Google Cloud project and configuring it to use the Home MCP.

Giving an AI agent access to real-world devices like smart locks, thermostats, and core infrastructure like HVAC systems and appliances raises obvious questions about security, privacy, and safety. Google says Home MCP enforces rate limits and safety protections; for example, it won’t allow an agent to unlock doors. However, depending on your agent, “connecting it to Home MCP can result in unexpected or even undesired behavior,” said Lehman, who recommends reviewing Google’s developer policies and terms of service.

Home Assistant, an open-source smart home platform, has implemented a similar MCP integration that shows what you can do when you give an agent access to your smart home system. I tested this last year to use Claude to vibe-code my smart home, and it easily handled some of the more complex tasks that most interfaces — and users, for that matter — struggle with, including troubleshooting, creating automations, designing a dashboard, and setting up more advanced configurations, all using natural language.

The biggest change here isn’t that Google Home can now turn your lights on and off through your Claude app; it’s that Claude — or your agent of choice — has access to the underlying data and control layer of your home. It’s a step toward building a whole home computer for your smart home that can understand what’s happening in it, reason across its history, and take action on your behalf. And if this last week wasn’t dominated by headlines about how AI will kill us all, I’d be really excited.

Still, there are real advantages to giving an AI agent access to your smart home. It can reason across the data your home generates and act on it in ways traditional smart home systems generally can’t, moving the smart home from command and control toward something more contextual and proactive, closer to actual intelligence. A system that can troubleshoot a device, suggest improvements to automations, and track and identify patterns across your home is much more useful than one that just says “I’m sorry, I can’t do that.” With Home MCP integration, Google is bringing these capabilities into Google Home.

While consumer-facing tools like Claude will be useful for smart home tinkerers, the bigger picture here is Google’s developer play. Over the last couple of years, Google has increasingly positioned itself as the smart home’s infrastructure layer. It launched API access to its smart home in 2024 and more recently made Gemini for Home a full-stack AI offering. All of this points toward a more B2B2C strategy: Google can provide the AI and smart home infrastructure while other companies build consumer-facing services and products on top.

With this week’s announcement, Google has also opened a path for developers to use its agentic Antigravity coding tool to build custom AI agents for the smart home that tap into Google Home device data and control layer. But even if developers use a different agent, as long as they’re using Google Home, it’s a win for Google. This way, Google becomes the smart home infrastructure layer, in much the same way AWS became infrastructure for internet and software businesses.

Whether smart home developers will buy into Google’s promises here is a big question. Based on the number of smart home platforms the company has launched and let die over the years — Android @ Home, Weave, Project Brillo, Works with Nest, Google Assistant — developers will have to decide whether Google has finally settled on a smart home platform it intends to stick with.