Google now lets Premium Advanced subscribers point Claude at their Home device graph

A household needs two things: a US billing address on Google Home Premium Advanced, and an agent that already calls Model Context Protocol tools ^[4][1]. Google started the rollout on Wednesday and called it early access, so bugs and limitations are expected ^[4].

Google's announcement, as quoted by CNET, said that any agent supporting Model Context Protocol tool calls can now interact with all of the devices and event history in the Google Home ecosystem ^[2]. Devices and history, ecosystem-wide. Google had already used MCP this way to let people add agents to Workspace ^[12].

Twelve months of Premium Advanced comes to $240 ^[17]. What that buys is a route into devices the household already owns and an event log it already generated ^[5]. Google did not describe this as retiring Gemini for Home, which it still ships as the voice assistant and controller for the same devices ^[1][5].

CNET's reviewer reported two separate faults with Gemini for Home: it does not always understand complex commands as intended, and it sometimes fails to operate devices that are connected and ready ^[14]. Those want different fixes. A different model can parse the sentence. The second fault sits below the agent, in the device integration itself, which every MCP client will call the same way, so a household that switches to Claude and still has a light that will not come on has changed the caller.

SwitchBot is building proprietary hubs so its own hardware talks natively to OpenClaw, and Homey sells universal hubs for mixed devices ^[9][10]. Both are doing per-agent hardware work, still under way. On the Google side, CNET describes the third-party agent as an extra layer of control on top of Google Home's existing device support and automations ^[11].

For whoever has to answer for this on Friday, the question is whether last month's failures happened before the device was called or after. A new agent may help with the ones that happened before; for the ones that happened after, MCP changes nothing. The second question is who owns the custom dashboard Google is offering in place of its own interface ^[6]. CNET's reviewer, who has used builds like it, wrote that they are "still a bit clunky, get things wrong, don't always do what they say and are difficult to troubleshoot thanks to the vibe coding involved" ^[15]. Google is directing early-access feedback to its smart home developers' help channel ^[16]. A Google representative did not immediately respond to CNET's request for comment ^[13].