Google Home MCP lets any AI agent control your Nest devices
Early US access for $20/mo Home users wires Claude, Antigravity or any MCP client to Nest cameras and Matter bulbs. Plus: Gemini 3.8 Live voice agents ship.
Copy markdown
The setup: a Cloud project, then any MCP client
Google's Home MCP server exposes your smart home to any agent that speaks MCP — Claude, Antigravity, Hermes, OpenClaw and others. You spin up a Google Cloud project, point it at Home MCP, then hand the config to your agent, which drives the sign-in and permission grant. Early access opened Sept 16 for Home Premium Advanced ($20/mo) subscribers in US English.
What you can actually build with it
Agents can pull camera summaries, monitor home activity, and control 'Works with Google Home' or Matter devices — Nest thermostats, doorbells, light bulbs. That's enough to wire up a natural-language home dashboard, a 'what happened while I was out' camera digest, or scene automations run by your agent instead of the Home app.
The guardrails: rate limits, and no unlocking doors
The server enforces rate limits and blocks sensitive actions — you can't script an agent to unlock a door. Google is gathering feedback through its Smart Home for Developers Community during the early window, with a full setup guide promised in the Home Developer Center.
Elsewhere: Gemini 3.8 Live ships production voice agents
Google added two audio-to-audio models to the Live API: gemini-3.8-live, the new default for low-latency voice agents, and gemini-3.8-live-extended-thinking, which reasons in the background mid-conversation. Both bring interleaved reasoning and async function calling, available now via the Gemini API and AI Studio.
Elsewhere: WSO2 open-sources an agent control plane
WSO2 shipped Agent Manager, an Apache-2.0 control plane (on GitHub) to deploy, govern and observe agents across any framework, with sovereign data placement and policy enforcement. If you're running more than a couple of agents, it's a self-hostable answer to 'agent sprawl.'