Google Home MCP just went into early access, and honestly, it’s the most interesting thing Google has shipped for agent builders this month. As of 16 September 2026 — per Google’s official announcement “Introducing Home MCP: enabling your agent to interact with your home” on the Google Home & Nest Community blog — AI agents like Claude, OpenClaw and Google Antigravity can now monitor, query and control your actual house. I’ve been through Google’s developer documentation line by line, and here’s the full picture.
Short answer
- Google Home MCP is an official MCP server (endpoint
home.googleapis.com/mcp) that lets AI agents list, monitor and control Google Home devices, announced 16 September 2026. - Early access: rolling out in English to US users with a Google Home Premium Advanced subscription, per Google’s announcement.
- Agents get five tool groups: homes, resources, live states, actions and history — full list below from Google’s developer docs.
- Safety rails are built in: rate limits, and sensitive actions like unlocking doors are prohibited outright.
- Setup needs a Google Cloud project with the Home API enabled and OAuth credentials — it’s a 20-minute job, walked through below.
What is Google Home MCP?
MCP (Model Context Protocol) is the open standard that lets AI agents call external tools. Google Home MCP is Google’s official MCP server for the smart home: point a compatible agent at https://home.googleapis.com/mcp (SSE transport, OAuth scope home.platform.v2, per Google’s developer documentation) and that agent can see and operate everything in your Google Home ecosystem — Nest cameras, thermostats, doorbells, plus Works with Google Home and Matter devices.
Google’s announcement frames it simply: any agent that supports calling MCP tools can interact with all devices and event history in the ecosystem. The named examples across Google’s documentation and announcement are Google Antigravity, Claude Cowork, OpenClaw and Hermes. In practice that means you can ask your agent to summarise camera activity across rooms, check whether devices are online, flip devices on a schedule it reasons about, or build you a dashboard of what’s happening at home — in plain English.
The five tools agents actually get
Google’s developer documentation lists five capability groups, and knowing the tool names helps you debug your agent’s behaviour:
| Tool | What it does |
|---|---|
list_homes |
Retrieves the homes and structures your account can access |
list_home_resources |
Lists devices, area layouts, traits, attributes and command schemas |
list_home_states |
Checks real-time connectivity and trait states |
run_home_actions |
Executes parameterised commands on target devices |
list_home_history |
Queries past state changes and event logs over time ranges |
The history tool is the sleeper here. Live control is a party trick; an agent that can query weeks of event logs and answer “has the back door camera seen anything unusual on weekday afternoons?” is a genuinely new capability class.
🔥 Want this set up without the guesswork? You’ve seen what Google Home MCP unlocks — now imagine having your whole agent stack (MCP servers, skills, automations) configured with someone who’s already built it. That’s exactly what we cover inside the AI Profit Boardroom — 3,700+ members, four live calls per week, daily tutorials, done-for-you templates and a 30-day roadmap. Or if you’d rather talk it through 1-on-1, book a free SEO strategy session and I’ll show you where it fits your site.
How to set up google home mcp
Straight from Google’s developer documentation, here’s the setup flow. Prerequisites first: an active smart home in Google Home with connected devices, an active Google Home Premium Advanced subscription, access to a Google Cloud project, and an MCP-compatible client.
- Create a Google Cloud project (or reuse one) in the Cloud console.
- Enable the Home API under APIs & Services → Enabled APIs & services.
- Configure the OAuth consent screen — External audience, app name and contact email filled in.
- Create OAuth client credentials of type Web application, adding the redirect URI for your client — for example
https://claude.ai/api/mcp/auth_callbackfor Claude,https://antigravity.google/oauth-callbackfor Antigravity, or your local URI for OpenClaw. - Publish the app, then add the server (
https://home.googleapis.com/mcp) in your agent’s MCP settings and complete the OAuth flow.
If you’ve wired up MCP servers before — like the ones I covered in how to use WebMCP and Claude Code managed MCP servers — this will feel familiar. If you haven’t, the OAuth consent screen is the only fiddly part.
Safety limits, and what Google deliberately blocks
Handing an AI agent the keys to your house is exactly as spicy as it sounds, so it matters that Google shipped guardrails on day one. Per the developer documentation: Home MCP enforces rate limits and safety protections, and sensitive actions such as unlocking doors are prohibited outright. Access is revocable at any time from the Google Home app or your My Accounts page, and Google explicitly recommends telling the people you live with that an agent has access.
Known limitations in this first release, again per Google’s docs: agents can’t create or manage automations yet, some experimental traits may misbehave, and latency optimisation is ongoing. Early access means early access — treat it as a capable beta, not a finished product.
What google home mcp means for agent builders
Step back from the smart-home novelty and look at the pattern: within one week, Google put an MCP server in front of its home ecosystem while OpenAI opened agent-based ad units. The agent layer is becoming the interface, and MCP is winning as the standard wiring. If you build automations, dashboards or client tools, “can it speak MCP” just became a purchasing criterion.
For my audience — people building AI-powered businesses — the practical wins are: agent-built home/office dashboards without writing an app, camera and event summarisation as a service for property managers, and a live playground for learning MCP tool-calling on real hardware you own. This is exactly the kind of build we walk through together inside the AI Profit Boardroom, and if you’re wondering how agent skills translate into revenue for your business, book a free SEO strategy session and I’ll map it with you.
The bottom line on google home mcp
Google Home MCP is early access done right: a real MCP server (home.googleapis.com/mcp) with five well-defined tools, sane guardrails (no door unlocking, rate limits, one-tap revocation), launched 16 September 2026 for US Premium Advanced subscribers in English, per Google’s official announcement and developer documentation. The setup is a 20-minute OAuth dance, and the payoff is any MCP-capable agent — Claude, OpenClaw, Antigravity, Hermes — operating your actual home.
If you’re already deep in the agent ecosystem, connect it this weekend. If you’re new to MCP, start with my WebMCP guide, then graduate to this. Either way, the direction of travel is unmistakable: agents are getting hands.
FAQ: google home mcp
Is Google Home MCP free?
The MCP server itself has no separate fee, but Google’s official documentation lists an active Google Home Premium Advanced subscription as a prerequisite, plus a Google Cloud project for the OAuth setup. So it’s bundled with Google’s top-tier Home subscription rather than free-standing.
Which AI agents work with Google Home MCP?
Any agent that can call MCP tools. Google’s own documentation names Google Antigravity, Claude Cowork and OpenClaw as examples, and the launch announcement also mentions Hermes.
Can an agent unlock my door through Google Home MCP?
No. Google’s documentation states Home MCP enforces rate limits and safety protections, explicitly prohibiting sensitive actions like unlocking doors.
How do I revoke an agent’s access?
Per Google’s documentation, access can be revoked at any time from the Google Home app or your Google My Accounts page.
Does Google Home MCP work outside the US?
The early access launched on 16 September 2026 rolling out in English to US users on Premium Advanced, per Google’s announcement. Wider availability hasn’t been published yet.
Can agents create automations with Google Home MCP?
Not yet. Google’s documentation lists automation creation and management as a known limitation of the current release, alongside some experimental traits and ongoing latency work.
Related reading
Ready to put Google Home MCP and a full AI agent stack to work? Inside the AI Profit Boardroom you get the exact systems 3,700+ members use — four live calls per week, daily tutorials, done-for-you templates and a 30-day roadmap. And if you want a personal plan for your site, book a free SEO strategy session and we’ll map it out together.
About the author
Julian Goldie is an SEO agency owner with 394K+ YouTube subscribers, a 100% job-success score on Upwork, 75K+ community members across his groups, 10+ years in SEO, and a best-selling SEO book to his name. He runs the Goldie Agency (book a call for a custom quote) and shares daily AI SEO tutorials on YouTube.
Want to learn AI SEO alongside 3,700+ members? Join the AI Profit Boardroom — four live calls per week, daily tutorials, done-for-you templates and a 30-day roadmap. Prefer 1-on-1 help? Book a free SEO strategy session.
Last updated September 2026. This is the living guide to google home mcp — it gets updated as the tools change.
