Google Opens Home APIs to Claude, ChatGPT With New MCP Server

Google has started letting outside AI assistants operate its smart home products. The company opened early access to a new Model Context Protocol server for Google Home, a bridge that lets agents such as Claude and ChatGPT read device states, pull camera summaries, and issue control commands in plain language. The move pushes Google Home from a walled app ecosystem toward a service that any capable model can call.

The server is built on MCP, the open specification Anthropic introduced in late 2024 and has since pushed as a common connector between models and external data. Under the arrangement, an AI agent authenticates against a user's Google account and then queries Home for the devices and activity it has permission to see. Commands flow back through the same channel, so a prompt like dimming a specific lamp or checking whether a door was left open resolves against real hardware rather than a scripted routine.

What agents can reach matters as much as the protocol. Google says the early build covers connected device control, camera summary review, and broader smart home activity, which means an assistant could answer questions about what happened on a porch camera overnight without the user opening the Home app. That activity data has historically been locked inside Google's own interfaces, and third parties have had to work through limited integrations or the Matter standard for basic device control.

Early access is limited, and Google has not published a general availability date or named which agent vendors are in the first cohort. The company also has not detailed how permissions are scoped, how long an agent retains what it reads, or whether users can revoke a single model's access without unlinking the whole account. Those gaps will draw scrutiny, since a misrouted command now touches locks, cameras, and thermostats rather than a chat window.

The launch lands in a widening contest over who sits between users and their devices. Amazon has spent years tying Alexa to its own hardware, Apple has kept HomeKit closed and leaned on Siri, and both have been slower to hand control to rival models. By adopting MCP, Google is effectively betting that being the default home backend for every assistant is worth more than keeping the front door to itself.

The test is whether developers and assistant makers treat the server as a first-class integration or a checkbox. Watch for the first named partners, the permission model Google ships alongside general access, and whether rival platforms respond with their own agent-facing APIs. If they do, the smart home stops being a set of apps and becomes infrastructure that models plug into.