Skip to content
Google Home MCP

Google Home MCP

by Google
Released
Repository Docs
Featured Productivity

Summary

Google's official MCP server for the Home ecosystem — let an agent list your homes and devices, read live trait state, run actions and query event history over OAuth.

Features

  • list_homes — discover the homes and structures the account can reach
  • list_home_resources — enumerate devices, areas, traits and accepted command schemas
  • list_home_states — read live device connectivity and trait values
  • run_home_actions — execute parameterised commands on target devices
  • list_home_history — query past state changes and event logs over a time range
  • OAuth against your own Google Cloud project, scoped to the signed-in account
  • Preprod sandbox endpoint for testing before touching real devices

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Google Home MCP" tools will be available.
{
  "mcpServers": {
    "google-home-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://home.googleapis.com/mcp"
      ]
    }
  }
}

Description

Google Home MCP is the official Model Context Protocol server for the Google Home platform, opened in early access on 16 September 2026. It puts a real smart home behind five tools, so an MCP client can discover the structure of a house, read what every device is doing right now, act on it, and look back over what happened.

The tool surface is deliberately small and closes the full loop:

  • list_homes returns the homes and structures the authenticated account can reach.
  • list_home_resources enumerates devices and rooms together with their traits, attributes and the command schemas each device accepts — so the agent learns what is callable rather than guessing.
  • list_home_states reads live connectivity and trait values.
  • run_home_actions executes parameterised commands against target devices.
  • list_home_history queries past state changes and event logs over a time range, which is what makes questions like "was the garage door left open yesterday afternoon?" answerable.

Access is not casual. The server lives at https://home.googleapis.com/mcp and speaks OAuth against your own Google Cloud project: you enable the Home API, configure an external OAuth consent screen, mint a web-application client ID, and register the redirect URI your AI client uses. On top of that, Google gates the server behind an active Google Home Premium Advanced subscription and a home with connected devices. A preprod endpoint (https://preprod-home.sandbox.googleapis.com/mcp) is available for testing.

The practical reading: this is the first time a major smart-home platform has exposed physical actuation to arbitrary agents through a standard protocol, with the account's own OAuth scopes as the boundary. Anyone wiring Claude, Gemini, Antigravity or another MCP client into a house should treat run_home_actions as a genuinely privileged tool and scope it accordingly. Early access, US-only at launch.

Related MCP Servers

See all Google Home MCP alternatives

MCP: Home Assistant MCP Server

by Home Assistant

Home Assistant's built-in MCP Server integration — lets Claude, ChatGPT and other MCP clients see and control exactly the smart-home entities you choose to expose.

Productivity

MCP: Memfault MCP Server

by Memfault (Nordic Semiconductor)

Remote MCP server for Memfault (Nordic Semiconductor) exposing 18 read-only tools over device fleet telemetry — device vitals, timeseries, crash issues, traces, metrics and software versions.

Cloud & Infrastructure

MCP: SerpApi MCP Server

by SerpApi

Official SerpApi MCP server: real-time Google, Bing, YouTube and other search results as structured JSON or token-saving markdown.

Web & Search
Browse all MCP servers →