Open Ecosystem or Walled Garden? What Google Home's MCP Bet Signals for Platform Strategy

Google just let competing AI assistants — Claude, Hermes, Open Claw, and others — control Google Home devices through an open standard, rather than locking that control to its own Gemini assistant. That's a specific, notable strategic choice worth examining if you're deciding how open to make your own platform's integration points.

Why Openness Can Beat Exclusivity

A platform that locks integration to its own tooling captures more value per user of that specific tool, but caps its total addressable value at whatever share of users choose that tool. A platform that opens via a genuine open standard instead captures value from every user regardless of which AI assistant, app, or tool they personally prefer — trading some per-user exclusivity for a much larger addressable surface.

When This Strategy Makes Sense for Your Own Platform

• You own a genuinely valuable resource (data, device control, a user base) that multiple tools want to integrate with — the resource itself is your moat, not the integration exclusivity
• An open standard already exists or is emerging in your category, meaning refusing to support it risks looking closed rather than differentiated
• Your competitors are likely to adopt the open standard regardless, making early support a credibility signal rather than a first-mover risk
• You can still differentiate on the quality of your own native integration (in Google's case, Gemini) even while supporting open access for others
• The switching cost for users choosing a different AI tool is currently low enough that locking them into your own ecosystem provides only a temporary advantage anyway

When Exclusivity Still Makes Sense

Openness isn't always the right call — if your core value proposition IS the exclusive integration itself (rather than the underlying resource), or if you're in a genuine land-grab phase where exclusivity drives adoption of your own primary product, locking integration down can still be the better near-term strategy. The key question is whether your moat is the resource or the access to it.

The Practical Takeaway

Before defaulting to exclusive integrations for your own platform, ask whether your actual competitive advantage lives in the underlying resource or in controlling who can access it. If it's the resource itself, an open standard can expand your addressable market without sacrificing your core differentiation — a bet Google is explicitly making with Google Home and MCP.