01
Overview
Google Home MCP gives compatible AI agents permissioned access to Google Home devices, states and history. Because those tools can affect a physical environment, setup is more than copying a server URL into an AI client: it involves a Google Cloud project, Home API configuration, OAuth authorization, selecting the home and reviewing what the agent can access.
This guide describes the launch-state setup architecture without inventing beta UI labels that may change during Early Access.
02
Before you start
Google Home MCP entered Early Access on September 16, 2026. The initial rollout is for Google Home Premium Advanced subscribers in the United States and continues over several weeks. You also need an existing Google Home environment and an MCP-capable agent/client.
If Home MCP is not available to your account yet, rollout eligibility may be the reason even if every other prerequisite is satisfied.
03
Step 1: Prepare your Google Home environment
Confirm that the devices you want the agent to work with are already visible and functioning in Google Home. Home MCP works through the Google Home ecosystem; it does not independently pair or replace the underlying device platform.
Google's launch coverage includes Nest and compatible Works with Google Home or Matter devices. The commands available to the agent depend on the device traits exposed through Google Home and Google's safety rules.
04
Step 2: Create or choose a Google Cloud project
Google's setup flow requires a Google Cloud project configured for Home MCP. Treat this project as the administrative boundary for the integration rather than casually reusing unrelated production credentials.
Follow the current Google Home Developer Center instructions for enabling the required Home API access because Early Access configuration details can change.
05
Step 3: Configure OAuth
Home MCP uses user authorization rather than handing an agent permanent unrestricted household access. Configure the OAuth client/redirect details required by your chosen MCP client and Google's current documentation.
Do not paste secrets into public prompts, repositories or screenshots. Store client credentials using the secret/configuration mechanism recommended by the client you are using.
06
Step 4: Add the MCP configuration to your agent
Provide the Home MCP configuration to a compatible client. Google and launch reporting name environments such as Antigravity, Claude Cowork and OpenClaw as examples.
Protocol support alone is not proof that a particular client version supports Google's complete authorization flow, so verify the client's current MCP documentation before troubleshooting the Google side.
07
Step 5: Sign in, select a home and grant permissions
The authorization flow asks the user to authenticate and choose the home the agent may access. Review the permissions instead of treating the OAuth screen as a routine click-through.
If other people share the home, Google recommends informing them that the connected agent may control devices and access home data. For development, a separate test home can reduce the consequences of an incorrect tool call.
08
Step 6: Test read-only discovery first
Before asking the agent to control anything, test discovery. Google's MCP exposes tools such as list_homes, list_home_resources and list_home_states for discovering structures/resources and inspecting live states.
A safe first validation is to ask the agent to list the accessible home, rooms and a non-sensitive device state. Confirm that the returned environment is the one you intended to authorize.
09
Step 7: Test a low-risk supported action
After discovery works, test run_home_actions with a low-consequence device such as a light rather than starting with security-sensitive hardware.
Google applies rate limits and safety protections. Its documentation specifically says Home MCP prohibits sensitive actions such as unlocking doors. Do not try to route around those restrictions through another automation layer.
10
Step 8: Test history only where needed
list_home_history lets an agent query past state changes and event logs. Historical access can reveal more about household routines than a single current-state query, so grant and use it only where it serves the workflow.
Camera and identity-related data can carry additional privacy considerations and consent requirements. Recheck Google's current policies before building workflows around sensitive history.
11
Step 9: Know how to revoke access
Google says the agent's Home MCP access can be revoked through the Google Home app or Google Account controls. Test that operational path before relying on the integration long-term.
Revocation should be part of the deployment plan, not something discovered after an agent behaves unexpectedly.
12
Troubleshooting: Home MCP is not showing
First check eligibility: the initial Early Access is limited to U.S. Google Home Premium Advanced subscribers and is rolling out over several weeks. Then verify that the required Google Cloud/Home API setup is complete, your OAuth redirect/configuration matches the current client, and the client actually supports the required MCP authorization flow.
Do not assume an absent feature means a configuration error while staged rollout is still active.
13
Safety checklist
Use a separate test home when practical. Start with read-only discovery. Test low-risk devices before broader actions. Keep OAuth credentials out of prompts and repositories. Review permissions carefully. Inform household members. Do not attempt to bypass blocked sensitive actions. Know how to revoke access before giving the agent recurring tasks.
14
What Home MCP does not guarantee
MCP standardizes tool discovery and invocation; it does not guarantee that an AI agent will interpret every instruction correctly. Google explicitly warns that connecting an agent can result in unexpected or undesired behavior.
Likewise, the Home MCP launch does not mean every MCP client, every Google Home device, every country or every subscription tier is supported. Treat current eligibility and capabilities as Early Access state.
15
FAQ
Do I need Google Cloud to use Home MCP?
Yes. Google's launch setup requires creating/configuring a Google Cloud project for Home MCP.
Do I need Google Home Premium Advanced?
For the initial U.S. Early Access, yes according to Google's rollout and launch reporting.
Can I connect Claude Cowork to Google Home?
Claude Cowork is one of the example MCP-capable environments named in launch coverage. Follow current Claude Cowork and Google Home MCP documentation for the exact connection flow.
Why can't my agent unlock a smart lock?
Google explicitly prohibits sensitive Home MCP actions such as unlocking doors as a safety protection.
Can I remove the agent later?
Yes. Google says Home MCP access can be revoked through Google Home or Google Account controls.
16
Verification note
The workflow above follows Google's official Home MCP capability and safety documentation plus launch reporting about eligibility and setup. Exact Cloud Console screens, OAuth fields and client configuration syntax can change during Early Access, so those details should be reverified immediately before publication rather than frozen into an inaccurate click-by-click tutorial.
Sources
Primary and supporting sources
Use the linked documentation to check current pricing, access and product behaviour. The dates above describe this article; they do not guarantee that every vendor claim remains current.