Google Home MCP Hands Rival AI Agents the Keys to Nest Devices
Google has opened a Model Context Protocol endpoint for its smart home, letting outside AI agents read and write across Nest cameras and doorbells, Nest thermostats, Matter bulbs and the wider Works with Google Home catalogue. Early access to Google Home MCP began on September 16, 2026, restricted to US subscribers of Google Home Premium Advanced, the $20-a-month tier that also sells for $200 a year. Five agents are named as compatible at launch: Anthropic's Claude, OpenAI's ChatGPT, the open-source Hermes and OpenClaw, and Google's own Antigravity platform.
Connecting one is not a switch inside the Google Home app. Each agent needs its own Google Cloud project and a Google account OAuth consent screen, which means a household authorizes every model individually and can pull that access back later.
What Google Home MCP Actually Exposes
Google's server publishes a fixed set of tools that any compatible MCP client can call:
- Discovering the homes and devices attached to an account
- Reading real-time device states
- Running supported device actions
- Retrieving event history
- Generating summaries from camera footage
Agents can also use a Google Home speaker or display as their voice output, and developers can build their own dashboards on top of the data instead of living inside Google's app. An authorized agent sees which rooms exist, what state each device is in, and what happened in the house over time.
Google describes the endpoint as a first step toward agent-driven homes rather than a finished consumer product. In practice, a household already paying for Claude Pro could ask that model whether a package arrived, request a summary of what happened on the driveway camera overnight, or switch off lights in a room named in plain language, without opening the Google Home app at all.
The Paywall and the Setup
| Parameter | Detail |
|---|---|
| Launch | Early access from September 16, 2026 |
| Eligibility | Google Home Premium Advanced subscribers, United States, English |
| Price | $20 per month or $200 per year |
| Agents named | Claude, ChatGPT, Hermes, OpenClaw, Google Antigravity |
| Setup | Separate Google Cloud project plus Google account OAuth consent per agent |
| Device reach | Nest cameras and doorbells, Nest thermostats, Matter devices, Works with Google Home products |
| Default voice | Gemini for Home, unchanged in the app and on Nest speakers and displays |
Availability is early access in English, and Google has not said when the capability reaches other subscription tiers or countries. The $20 figure is also the industry's default: ChatGPT Plus, Claude Pro, Perplexity Pro and Google AI Pro all sit at that number. Adding Home MCP to the tier gives Google a second reason for the same charge, which is the doorway any assistant must pass through.
Gemini Keeps the Microphone
Gemini for Home stays the default voice experience in the Google Home app and on Nest speakers and displays, and Google has offered no way to change that. The MCP layer is additive and developer-facing. A household can hand Claude the thermostat and the doorbell while still hearing Gemini answer a spoken question in the kitchen, which keeps the most-used surface under Google's control even after a rival takes over the automation.
Who Owns the Agentic Home
Openness is the framing; routing is the mechanism. Whoever operates the MCP server observes every device state change and every event that passes through it, defines the OAuth scopes that bound what an agent may touch, and holds the billing relationship with the household. A user can swap Claude for ChatGPT and the endpoint stays the same. So does the $20 invoice, which Google collects whether the model answering the doorbell belongs to Gemini or to a competitor.
The money stacks in Google's favour twice. ChatGPT Plus and Claude Pro both sit near $20 a month, so a household that wants a rival agent running its home pays roughly $40 across two subscriptions, one of which Google controls. The tier also works as a filter, because the people willing to configure a Cloud project are the ones already paying for a frontier model.
There is an irony in the plumbing. MCP began as an open standard from Anthropic, Claude's parent, and Google has now adopted a competitor's interface for the layer that connects agents to the physical world. Standardising on someone else's protocol is a concession, and it also makes Google the party that decides which version of that protocol the home speaks.
Where the Safety Line Sits
Google points to the consent screen as the control surface, and that is where the real limits live. Each agent receives only the scopes it is granted, event history access can be withheld, and camera data carries restrictions. The risk profile of a smart-home agent therefore depends less on which lab trained the model than on how broadly a household clicks through the authorization flow, and on what a year of occupancy history is worth to whoever ends up holding it.
The Regulatory Shadow
The European Commission's binding decisions under the Digital Markets Act, issued on July 16, 2026, require Google to give rival assistants equally effective access to 11 Android capabilities, with compliance expected by July 2027. Those orders cover phones rather than home hubs. Home MCP opens a product the DMA does not yet reach, on terms Google writes itself, which is a cheaper way to meet the direction of travel than waiting for a specification decision to force the shape of it.
The Verdict
For a US household already paying for Premium Advanced and already subscribed to Claude Pro or ChatGPT Plus, Home MCP is the first feature that makes the $20 tier do something Gemini cannot do alone. Everyone else gets a preview behind a paywall and a Cloud console. The change that would matter most, replacing Gemini at the microphone, is the one Google left out.
Why This Matters
For a company that kept its assistant stack closed, exposing the full device and event layer to Claude and ChatGPT is a reversal that sets the terms of the agentic home before rivals or regulators do. The subscription, the event history and the authorization screen stay with Google even when the model does not, and that template is what competing smart-home platforms will be measured against. Households, meanwhile, are being asked to treat an OAuth scope as the security perimeter of their home.
Photo by Curtis Berry on Unsplash
Related Articles
- Google Home Gains Gemini 3.1 Integration and New Ask Home Search Tool
- Google Home Speaker Unveiled with Integrated Gemini AI Features
- Coding Agent Race This Week: Open Weights, Breaking Releases, Tooling Shifts
✔Human Verified
Researched and cross-referenced against primary sources by the Bytevyte editorial team. This article was generated with the assistance of artificial intelligence and reviewed by the Bytevyte editorial team.