Google's Home MCP Lets Claude And ChatGPT Drive Your Nest Devices

Google launched Home MCP, a Model Context Protocol server letting Claude, ChatGPT and other AI agents control Nest cameras, thermostats and Matter smart-home devices under user-approved scopes.

Google's Home MCP Lets Claude And ChatGPT Drive Your Nest Devices

Google is opening the door to its smart-home ecosystem for third-party AI agents. On September 16, 2026 it announced Home MCP, a Model Context Protocol server that lets Anthropic's Claude, OpenAI's ChatGPT and other agents drive Nest cameras, thermostats, doorbells and Matter light bulbs through a single documented interface.

What Home MCP actually does

Home MCP exposes Google Home devices as tools that any MCP-compatible agent can call. That means an agent can query a smart-home dashboard, cross-analyse footage from multiple Nest cameras, generate video summaries, deliver a spoken message through Home speakers, and read a device's state history — energy usage over the last month, when the dryer last ran — all as first-class actions. Compatible agents at launch include Claude, ChatGPT, Google Antigravity, Hermes and OpenClaw, plus anything else that speaks MCP.

Google Home smart speakers with MCP support

Guardrails

Google says Home MCP enforces rate limits and blocks the most sensitive actions outright — no agent gets to unlock a smart lock, for example. Users manually create a Google Cloud project, configure their chosen agent, and hand-approve each set of scopes. Early access is limited to Google Home Premium Advanced subscribers in the U.S. and English-language interfaces.

Why it matters

The Model Context Protocol has become the plumbing that lets agents work outside their own apps. InOrbit's OpenRobOps just brought a similar interoperability layer to fleet robotics; Google Home MCP does the same for consumer devices. If the launch sticks, Nest becomes the first hyperscale smart-home platform that treats every AI assistant — not just its own — as a legitimate client, and puts pressure on Alexa and Apple Home to publish comparable interfaces.

The upshot for developers

The developer documentation lives at developers.home.google.com/mcp/home, and Google's own Gemini-facing assistant is not the reference client — anyone building an agent can plug in. The bet is that opening the smart-home surface will make Google Home the default hub for the AI-agent era, rather than a silo the agents route around.

Reporting based on coverage from 9to5Google, TechCrunch, Android Police and Unite.AI.

Category: AI & Technology

Tags: Healthcare Technology Google AI AI Agents Anthropic Claude

Related Articles