The protocol war is over. In six weeks, four major smart home platforms independently adopted the Model Context Protocol (MCP) — Sonos 27 at IFA, Home Assistant 2026.9, and Google Home, joining Amazon Alexa+, which shipped in July. No consortium mandated it. No regulator required it. MCP won the same way HTTP won the early web — through convergent independent adoption.
But convergence at the protocol layer has created a fork at the business layer. Two paths now run from the same starting point, and they head in opposite directions.
The Toll Booth
Google Home’s MCP integration launched September 16 as early access, US-only. To use it, you need a Google Home Premium Advanced subscription — $20 per month or $200 per year. Amazon Alexa+ sits at $19.99 per month, though Prime members get it bundled. Both architectures are cloud-mediated: your agent’s requests route through the platform’s servers, not your own.
Google’s implementation makes the mediation especially visible. You don’t just flip a switch. You create a Google Cloud project, configure OAuth credentials, and connect your chosen agent — Claude, ChatGPT, Hermes, OpenClaw, Google’s own Antigravity, or any MCP-compatible client — through Google’s authentication backend. Every interaction passes through Google’s infrastructure. The protocol is open. The access is gated.
What does the subscription actually buy? Not protocol access — that’s free. You’re paying for cloud infrastructure that mediates the connection, enforces rate limits, and applies safety controls. Google explicitly forbids agents from unlocking doors. Whether that’s a sensible guardrail or a platform overreach depends on your perspective, but the structural point stands: the platform, not the user, decides what the agent can touch.
The Ownership Bet
On the other side, a different philosophy is taking physical form. Home Assistant, which expanded its MCP support in the 2026.9 release, remains the reference implementation for local-first agent architecture. It’s free, open-source, and runs on your own hardware. Agent logic stays local via Ollama or llama.cpp. Your data doesn’t leave the house unless you explicitly opt into a cloud backend. Community extensions like MCP Assist report roughly 95 percent token reduction through dynamic entity discovery — local efficiency the cloud model can’t match.
At IFA 2026, the hardware followed the philosophy. Ugreen launched its HomeAgent line: the HA100 at $899 (early-bird Kickstarter), scaling to the $9,999 MasterAgent MA100 with an Nvidia Jetson Thor T5000. Anker’s Eufy MindBase offered a similar pitch — on-device AI, Matter support, up to 48TB local storage — though pricing remains unannounced. Midea’s SMART MASTER, unveiled September 5, pushed further: five specialized AI agents, 140-language support, and a physical robot companion built on its EAGLES architecture.
The math here is worth sitting with. At $20 per month, Google Home Premium Advanced costs $240 per year. The Ugreen HA100 at $899 breaks even in roughly 44 months — about three years and eight months. After that, local-first is free. The MA100 at $9,999 is a different market entirely — roughly 41 years of cloud subscriptions — aimed at users who value total isolation over simple cost savings. But the consumer-grade entry point is already within reach of a serious smart home buyer’s annual budget.
The tradeoff is real: local-first requires more setup, more troubleshooting, and more technical confidence. You become your own system administrator. But you also become the one who decides what your agent can see, say, and do.
The Gate Inside the Gate
Here’s what makes the Google Cloud project requirement worth watching. MCP is an open standard — any agent can speak it. But to talk to your Google Home devices, that agent must first authenticate through Google’s OAuth backend. The platform doesn’t just host your devices; it hosts the permission layer between your agent and your devices. Even OpenClaw, the most privacy-focused local agent framework, has to pass through Google’s infrastructure to reach a Nest thermostat.
This is the subtle difference between an open protocol and an open market. The protocol lets anyone participate. The infrastructure determines who can actually reach the consumer.
Two Bets, One Living Room
These two paths aren’t going to merge. The cloud gatekeepers are betting that convenience, ecosystem depth, and managed safety will justify a perpetual subscription. The local-first builders are betting that privacy, ownership, and a one-time hardware cost will feel like the better deal once the subscription tax adds up.
MCP convergence didn’t settle this argument — it clarified it. The protocol is the same on both sides. The question is whether you want to rent the gate or own the wall.