Google Home adds an MCP server, gated at $20 a month

Google opened early access to a Model Context Protocol server for Google Home on September 16, 2026. It lets an outside AI agent control the lights, locks and thermostats in a house. TechCrunch reports that it is limited to Google Home Premium Advanced subscribers in the United States, a tier that costs $20 a month.

MCP is the Model Context Protocol, a standard way for an AI agent to call an outside service. A server for Google Home therefore hands the smart home to whatever agent the user points at it.

What the server exposes

The capability list is broad. TechCrunch reports that an agent can control connected devices and reach event history, and that a user can review camera summaries and watch smart home activity. Engadget adds that agents can work across rooms and build custom dashboards.

The device side is the whole Google Home ecosystem rather than a subset: Nest doorbells, thermostats, Matter-compatible devices and anything carrying the "Works with Google Home" label, per TechCrunch.

Both reports name the agents. TechCrunch lists Claude, ChatGPT, Hermes, OpenClaw and Google Antigravity. Engadget names Antigravity, Claude, Hermes and Open Claw, without ChatGPT. The overlap is the safe reading, and the difference is worth checking against Google's own list before you promise a client anything.

What it costs and how you turn it on

The setup is not a toggle in an app. It runs through Google Cloud.

Item	What the reports say
Requirement	Google Home Premium Advanced, $20 a month or $200 a year
Region	United States at the start, per TechCrunch
Timing	Early access rolling out over the coming weeks
Setup	Create a Google Cloud project, configure Home MCP, hand the details to your agent, sign in, grant permissions
Docs	A setup guide in the Google Home Developer Center

That sequence tells you who this is really for. Creating a Cloud project and pasting connection details into an agent is a developer's workflow, not a homeowner's. Treat the paid tier as the price of a development environment rather than a consumer upsell.

What this means for developers

Read the permission model before you build on it. Neither report states what scopes the server requests, whether authorization is per-device or account-wide, or what Google's policy is for camera footage and the summaries built from it. Those three answers decide whether this is safe to put in front of anyone else's home. None of them appear in the coverage, so read the Developer Center documentation first.

Engadget raises the protocol-level caveat, and it is the right one. It notes that MCP has known security problems, including no enforced authentication, and that breaches have followed its adoption. An agent holding a live door lock is a different risk class from an agent holding a calendar. This site has covered how MCP traffic is already something networks try to detect and block, which is the other half of the same problem.

Design for the subscription lapsing. The server is tied to a paid tier, so your integration gains a failure mode unrelated to your code or the user's network. A card expires, and the agent loses the house. Decide now whether that degrades quietly or alarms loudly.

Finally, watch what "early access" means in practice. Both reports describe a rollout over weeks rather than a switch that is already on, and only one names a country. If you are planning work around this, verify your own account can actually reach the server before you schedule anything.