Google opened early access to Home MCP on September 16, 2026. Any agent that speaks the protocol can read device states and event history, then act. Hover a chip to see what that agent is. Hover a row to compare read against write.
| Region | United States |
| Plan | Google Home Premium Advanced — the $20/month tier |
| Devices | Nest doorbells, thermostats, and Works with Google Home / Matter devices |
| Wider rollout | Google would not comment on timing or other markets |
| Capability | Read | Write | What it means in practice |
|---|---|---|---|
| Device state | Yes | Yes | “Is the garage door shut?” becomes a question your agent can answer — and change. |
| Camera summaries | Yes | — | Your agent can review written summaries of what cameras saw. |
| Event history | Yes | — | Searching who came to the door is now a prompt, not a scrubbed timeline. |
| Device control | Yes | Yes | Lights, thermostats and Matter devices — the write access that deserves your caution. |
| Custom dashboards | Yes | Yes | Build your own view over home data instead of using Google's app. |
Setup means creating a Google Cloud project and handing credentials to an agent. Treat that credential like a house key: know which agent holds it, and revoke it when that agent goes. Then decide what may be changed unattended and what needs your approval — an agent that can adjust a lock or a thermostat can also be wrong at 3am.
Sources: TechCrunch, “Your AI agents can now control your Google Home devices,” September 16, 2026; Google Home Developer Center. Full analysis at wolffi.sh/blog/google-home-mcp-ai-agents