# MCP Won Before the Products Shipped – Google, Amazon, Sonos, and Home Assistant on the Same Protocol > Source: > Published: 2026-09-17 11:26:51+00:00 The smart home agent war is being fought on a protocol layer that has already been decided. In six weeks, four major smart home platforms independently adopted the [Model Context Protocol](https://forkast.news/glossary/model-context-protocol-mcp/) (MCP): Amazon Alexa+ (July), Sonos 27 (September, IFA), Home Assistant 2026.9 (September 12), and Google Home (September 16). MCP has become the de facto standard – not by committee, but by convergent independent adoption. The competitive frontier has shifted from “which protocol” to “which subscription tier” and “which agent gets access.” The protocol is free; the access is not. ## Four Platforms, One Protocol The convergence is striking in its speed. Amazon’s Alexa+ integration in July was the first major platform to ship MCP support. Sonos followed at IFA in September with Sonos 27. Home Assistant added native MCP in its 2026.9 release on September 12. Google Home completed the set on September 16 with its own MCP integration. Each platform arrived at the same conclusion independently. No industry consortium mandated MCP. No regulatory body required it. The protocol won through technical merit and ecosystem pressure – the same way HTTP won the early web. ## The Subscription Split While the protocol layer has converged, the access models have diverged sharply. Google Home Premium Advanced costs $20 per month for agent capabilities. Amazon Alexa+ sits at $20 per month. Sonos ships MCP support for free. Home Assistant remains free and open-source. This creates a two-by-two matrix: two subscription models (Google, Amazon) versus two open models (Sonos, Home Assistant). The protocol is identical across all four. The difference is who pays, and what the user gets for that payment. For enterprise builders, this split matters. A developer building an MCP-compatible smart home agent can target all four platforms with the same protocol implementation. But the monetization layer – the subscription gate, the API rate limits, the feature access – varies by platform. The protocol convergence has eliminated the integration cost. The business model divergence has not. ## The Agent Layer The real question is not which platform adopted MCP first. It is what happens when agents begin operating across these platforms simultaneously. An MCP-compatible agent that can control Google Home, Alexa, Sonos, and Home Assistant devices through a single protocol has effectively unified the smart home – at the protocol level. The subscription models create friction points. An agent operating across Google and Amazon platforms must navigate two different billing relationships. An agent operating across Sonos and Home Assistant faces no such friction. The open platforms become the natural habitat for multi-platform agents. ## What to Watch As MCP becomes the universal adapter for smart home agents, the competitive dynamics shift from protocol lock-in to agent quality and subscription value. The platforms that provide the richest MCP tool exposure – the most devices, the most capabilities, the most reliable execution – will attract the best agents. The subscription models will be tested by whether the agent experience justifies the monthly cost. For the smart home industry, MCP convergence is not an endpoint. It is the foundation layer. The real competition begins now: which platform delivers the best agent-native experience on top of the same protocol everyone else is using.