Google opened Home MCP servers that let AI agents control smart-home devices
Google has opened early access to two Model Context Protocol servers for Google Home, one for consumer agents like Claude and ChatGPT to control connected devices, and a second for coding agents that indexes Home programs, Matter and OpenThread docs.
Image: TechCrunch
Why it mattersA consumer platform now uses the same protocol as developer tools, so the code an agent writes and the devices that agent controls can be in the same session, with permissions and event history included.
Google said on 16 September that it is rolling out early access to two Model Context Protocol servers under the Google Home Developers programme. One is aimed at consumer AI agents that support MCP, including Claude, ChatGPT, Hermes, OpenClaw and Google Antigravity, and lets them read a home's event history and control connected devices. The second is a Home Developer MCP for coding agents, which indexes Google Home programme documentation, the Matter specification and OpenThread docs so an agent can answer technical questions with context taken from real documentation.
What is inside the consumer server
Google says the Home MCP server exposes device state, event history, camera summaries and command execution to any MCP-capable agent. The company writes on the developer page that the server is in Early Access, and lists device support that covers Google Nest doorbells and thermostats plus every "Works with Google Home" or Matter device connected to the account. TechCrunch reports that a user creates a Google Cloud project, gives the MCP configuration to their agent of choice, and grants permissions through a sign-in flow.
Access is limited at launch. TechCrunch reports that Google is starting the rollout today and continuing "over the coming weeks" to subscribers of Google Home Premium Advanced, a 20 dollar per month tier in the United States that already carries longer event-based video history and daily summaries. Google would not tell TechCrunch when the server would open to lower tiers or to markets outside the United States.
The developer server is separate
The Home Developer MCP is a different endpoint aimed at coding agents rather than at homeowners. Google's page describes it as a way to give an agent "verified technical data" from indexed Home programs, Matter specifications and OpenThread documentation. That places it in the same category as the MCP servers Google already runs for Google Cloud, Google Workspace and its data platforms, but covering the protocols that home devices use.
First MCP server that controls physical devices
Every MCP server Google opens to third-party agents adds to the places where Claude, ChatGPT or a custom agent can act, and this is the first one that reaches physical devices in a home. For a team building against MCP, that is worth tracking for two reasons: the consumer server is a live example of a large vendor exposing per-user event history under a permission grant, and the developer server is a source an in-editor agent can quote from with current information, whatever the model's training cutoff, when the question is about Matter or OpenThread. The Early Access label and the paid-tier requirement mean it is not yet a stable dependency, and Google is soliciting feedback from early users through its Smart Home for Developers community.
Source
- Home MCPs, Google Home Developers, 16 September 2026.
- Coverage in TechCrunch and The Verge.
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.
