Google Home MCP is reportedly in early access in the United States, giving compatible external AI agents access to Google Home devices, current states and household event history. The reported access requires a Google Home Premium Advanced subscription priced at $20 per month or $200 per year.
The integration uses the Model Context Protocol (MCP), a standard for connecting AI clients with external tools and data. That makes it more than a way to send one isolated command from a chatbot: an agent can reportedly inspect the connected home, combine information from multiple devices and carry out authorized actions.
What Google Home MCP lets an AI agent do
Reported compatible clients include Google Antigravity, Claude, Hermes and OpenClaw. Once connected, an agent can reportedly:
- Discover devices in a Google Home environment.
- Read current device states and status information.
- Inspect household event history and changes over time.
- Execute authorized commands on connected devices.
- Send an audio message through a Google Home speaker after completing a task.
- Create a customized dashboard for the connected home.
The practical difference is context. An agent could, for example, analyze footage across cameras, count laundry cycles over a week or calculate how long lights remained on. Those jobs require access to information from several devices or to historical events, rather than a single “turn on the lamp” instruction.
Home MCP is not a replacement for Gemini for Home
Home MCP adds an external-agent connection to the Google Home ecosystem. Gemini for Home remains the standard Google assistant interface for Google Home and Nest products, while Home MCP is intended for compatible third-party clients such as Claude or OpenClaw.
| Aspect | Home MCP | Gemini for Home |
| Primary role | Connects compatible external agents to Google Home data and authorized controls | Serves as Google’s native assistant interface for Google Home and Nest products |
| User interface | External clients such as Claude, Google Antigravity, Hermes or OpenClaw | The Google Home app and Nest speakers |
| Relationship to the other service | Additional integration | Existing Google Home assistant experience |
That separation matters for anyone already using Google’s smart-home controls: Home MCP adds another way to work with connected devices and their data without replacing the usual Google Home and Nest interface.
U.S. price and reported setup requirements
The reported initial access is limited to Google Home Premium Advanced subscribers in the United States. The subscription is reported to cost $20 monthly or $200 annually.
Setup reportedly requires a Google Cloud project, additional developer configuration and an MCP-compatible AI client. This is aimed at connecting an agent to a user’s smart-home environment, rather than adding an automatic voice-command feature to the Google Home app.
The reported U.S. early-access rollout began on September 16, 2026.
Permissions and sensitive actions still matter
Connecting an outside agent to household devices expands what that agent can read and control. Taylor Lehman, a group product manager for Google Home & Nest, warned that connecting an agent to Home MCP can lead to unexpected or unwanted behavior.
Google reportedly applies rate limits and safety protections, including blocking door-unlocking actions. The integration can therefore work with authorized smart-home commands without allowing an agent to perform every sensitive action available through a connected lock or another device.
