Google Home MCP

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.