Skip to content
ReviewRamble

The weekly brief

AI, reviewed, in your inbox.

  • New reviews of tools, models, MCP servers and repos, with the verdict up front
  • Re-checked prices and ratings when something changes
  • New analysis pieces as they are published

Models, agents, MCP servers and the tools actually worth your time.

One email a week. Unsubscribe with the link in any brief. How we use your email

Google Home MCP Server

Google's hosted server lets an agent read, control and automate a Google Home; US-only early access for Premium Advanced subscribers.

Reviewed by ReviewRamble editors · Updated

Setup docs Paid

Share this page:XLinkedInFacebookRedditWhatsAppEmail

Our rating

3.6/5

Google's own way into Google Home, with sensible guardrails, held back by a developer-grade setup, a $20 monthly subscription and US-only early access.

What is Google Home MCP Server?

Google Home MCP Server is Google's own hosted MCP endpoint at home.googleapis.com/mcp, in early access. It has seven tools. Five only read: list_homes, list_home_resources (devices, rooms, traits and command formats), list_home_states, list_home_history (past state changes and events) and list_automations. Two change things: run_home_actions sends commands to devices, and save_automation validates and saves a new automation in your home. It speaks streamable HTTP and signs in with OAuth.

It needs an active Google Home Premium Advanced subscription and a Google Cloud project of your own, with the Home API enabled and an OAuth client you create. Google's September 2026 developer newsletter says early access is rolling out in English to Premium Advanced users in the US. The docs give setup steps for Google Antigravity, Claude (a custom connector used in Cowork) and OpenClaw.

How to install Google Home MCP Server

https://home.googleapis.com/mcp

Is Google Home MCP Server worth it?

This is the only route to Google Home devices and history that Google itself runs, and the setup shows it was built for developers rather than households. Before an agent can switch a light, you create a Google Cloud project, enable the Home API, configure an External OAuth consent screen, create a web-application client with your agent's redirect address and publish the app. Without a website, privacy policy and terms of service you can leave the app in Test mode, but then you must sign in again every 7 days.

Five of the seven tools only read. run_home_actions sends any command a device's traits accept, so lights, plugs, thermostats, speakers and the rest of the home are in reach, and save_automation writes automations that keep running after the conversation ends. Google says the server enforces rate limits and blocks sensitive actions, naming the opening of door locks as one. It does not publish the rate limits or a full list of what is blocked, and it warns that some included traits are experimental and that agents may behave in unexpected or undesired ways.

The server runs in Google's cloud, not on your network. Device states, event history and anything an agent asks about cameras go to whichever model provider the agent uses; the newsletter says agents can summarise camera footage across rooms. Google's Nest privacy commitments say video is shared with third-party apps and services only when someone in the home explicitly allows it, and that video, audio and sensor readings are kept out of ad personalisation. Your OAuth grant is that permission, so what the agent does with the data afterwards falls under its provider's terms. Familiar-face data needs a separate consent from a home manager. Google advises telling everyone in the home, or setting up a separate test home.

The subscription is the larger cost: Premium Advanced is $20 a month or $200 a year in the US, and what it mainly buys is 60 days of event video history and 10 days of 24/7 history. A known bug currently lets Nest Aware Plus subscribers in without it. A household already running Home Assistant gets local control without a subscription from its built-in integration or ha-mcp; this server makes sense when the devices already live in Google Home and you would rather trust Google's guardrails than a community bridge.

Where it earns its place

  • A US household with Nest cameras on Premium Advanced

    Find out what happened at the front door while we were away

    Add the connector in Claude with your own OAuth client and ask for the day's events; list_home_history answers from Google's records. Nothing extra to pay beyond the $20 subscription and the Claude plan.

  • A smart-home developer prototyping an assistant

    Draft automations in plain language before building them properly

    Create a separate test home as Google suggests, let the agent write automations with save_automation and inspect them in the Google Home app. In Test mode the sign-in lapses every 7 days.

  • A homeowner keeping an eye on energy use

    See how long the lights stayed on last week

    Questions like this need only list_home_states and list_home_history. Refuse approval for run_home_actions in the client so the agent cannot change anything while it answers.

Before you commit

Setup
Create a Google Cloud project, enable the Home API, configure an External OAuth consent screen, create a Web application client with your agent's redirect URI (for Claude, https://claude.ai/api/mcp/auth_callback), publish the app, then add https://home.googleapis.com/mcp in the client and sign in.
Integrations
Seven tools: list_homes, list_home_resources, list_home_states, list_home_history, list_automations, run_home_actions and save_automation. Documented clients are Google Antigravity, Claude through a custom connector in Cowork, and OpenClaw through mcp-remote.
Data and privacy
Hosted by Google. The OAuth scope home.platform.v2 covers devices, states, history and automations in every home the account can reach, and that data passes to the agent's model provider. Familiar-face data needs separate consent from a home manager. Revoke access in the Google Home app or your Google Account. Retention of MCP requests is not published.
Cost at scale
No per-call price is published. The cost is Premium Advanced at $20 a month or $200 a year in the US, plus the agent's own subscription.
Limits
Early access in English in the US only. Rate limits are enforced but not published; some traits are experimental and responses can be slow. Test-mode apps need signing in again every 7 days. The agent cannot open door locks.

What’s good

  • Run by Google; no third-party bridge holds your tokens
  • Opening door locks blocked on the server
  • Reads event history and automations, not just current state
  • Access revocable from the Google Home app

What’s not

  • Needs Premium Advanced at $20 a month
  • You build the Google Cloud project and OAuth client yourself
  • US and English only during early access
  • Rate limits and blocked actions not published

Best for

US Google Home Premium Advanced subscribers who are comfortable in the Google Cloud console and want an agent to query history and run devices.

Google Home MCP Server alternatives

Google Home MCP Server: common questions

Is Google Home MCP Server worth it?
Google's own way into Google Home, with sensible guardrails, held back by a developer-grade setup, a $20 monthly subscription and US-only early access. We rate it 3.6 out of 5.
How much does Google Home MCP Server cost?
No separate charge for the server; it requires Google Home Premium Advanced at $20 a month or $200 a year in the US.
What are the downsides of Google Home MCP Server?
Needs Premium Advanced at $20 a month; you build the Google Cloud project and OAuth client yourself; uS and English only during early access; rate limits and blocked actions not published.
Who is Google Home MCP Server best for?
US Google Home Premium Advanced subscribers who are comfortable in the Google Cloud console and want an agent to query history and run devices.
How much does Google Home MCP Server cost for a team or in production?
No per-call price is published. The cost is Premium Advanced at $20 a month or $200 a year in the US, plus the agent's own subscription.
Is Google Home MCP Server safe for company data?
Hosted by Google. The OAuth scope home.platform.v2 covers devices, states, history and automations in every home the account can reach, and that data passes to the agent's model provider. Familiar-face data needs separate consent from a home manager. Revoke access in the Google Home app or your Google Account. Retention of MCP requests is not published.
What are the best Google Home MCP Server alternatives?
The closest alternatives we have reviewed are Home Assistant MCP Server, HA-MCP, Aqara MCP Server and HomeMCPBridge.

Answers checked Nov 16, 2026.