Google opens a Home MCP server so Claude, ChatGPT and other agents can run smart-home devices

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 grounded context.

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 ground an agent in "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 pointed at the home ecosystem's own protocols.

First MCP server that touches physical devices

Every MCP server Google opens to third-party agents lengthens the list of surfaces 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 on two fronts: 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 without a training-cutoff excuse when the question is about Matter or OpenThread. The Early Access label and the paid-tier gate 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.