Skip to content
OddBrief
Tech2 minTraced to the primary source

Google opens Home devices to third-party AI agents via MCP

Google began early access to a Model Context Protocol server for Google Home, letting MCP-capable agents such as Claude control smart-home devices and read event history. The rollout starts for U.S. Google Home Premium Advanced subscribers at $20 a month and will continue over coming weeks.

AI-assisted, human-reviewed

Official Google Nest graphic showing Gemini for Home voice assistant on a Nest speakerTech
Google

Key facts

Protocol
Early access Google Home MCP server for any MCP-supporting agent (e.g. Claude, Hermes, OpenClaw, ChatGPT, Google Antigravity)
Capabilities
Natural-language control of devices, camera summaries, activity monitoring, custom dashboards; Nest and Works with Google Home / Matter devices
Access
U.S. Google Home Premium Advanced ($20/mo); rolling out from Sep 16 over coming weeks
Setup
Users create a Google Cloud project, configure Home MCP, hand details to their agent, then sign in and grant permissions

Third-party AI agents can now reach into Google Home. On September 16, 2026, TechCrunch reported that Google started early access to a Model Context Protocol server for its Google Home ecosystem. Any AI agent that supports MCP, including Claude, Hermes, OpenClaw, ChatGPT, and Google Antigravity, can securely work with a user’s smart-home devices and access event history. The company is aiming the feature at consumers who already experiment with agents for everyday tasks, not only at cloud developers.

What Home MCP unlocks

Once connected, people can use natural language to review camera summaries, monitor smart-home activity, control connected devices, and build custom smart-home dashboards, according to TechCrunch’s account of Google’s rollout. The system is meant to support any device in the Google Home ecosystem. That includes Google Nest doorbells and thermostats, as well as “Works with Google Home” or Matter devices such as light bulbs. Google would not say whether or when MCP would expand to other subscription tiers or markets.

Setup is not a one-tap toggle. Users need to create a Google Cloud project and configure it to use Home MCP. They then give the MCP configuration details to their agent of choice and ask the agent to set it up. The agent prompts them to sign in and grant permissions. Google also plans a setup guide in the Google Home Developer Center. During early access, the company is soliciting feedback through its Smart Home for Developers Community.

Why it matters for agent apps

The odd part is not that Google added another smart-home skill. It is that Google is exposing Home through the same open agent protocol it already uses elsewhere, so Claude or another MCP client can drive Nest cameras and Matter bulbs without living inside the Google Assistant brand. That makes the living room another surface where competing agents can act, as long as the user pays for Premium Advanced and is willing to wire a Cloud project.

For now, the experiment stays inside a paid U.S. tier and a developer-flavored setup path. Broader availability remains unconfirmed. If the early cohort finds the permissions flow workable, Home MCP could turn “ask my agent to lock the doors” into a cross-vendor habit rather than a Google-only one. Google already uses MCP in other parts of its business, including Google Cloud and data platforms, developer tools, and Google Workspace. Home support is different because it targets households rather than enterprise workflows. An earlier version of TechCrunch’s story misstated the start day; the corrected report says access began Wednesday, September 16, and continues over the coming weeks.

Who gets it and how setup works

Access is limited. Google said the MCP will roll out to subscribers who pay for Google Home Premium Advanced in the United States. That tier costs $20 per month and already includes longer event-based video history, descriptive notifications, detailed alerts, tools to search video history, daily summaries, and related features.

Sources

Related reading