Google’s June 30, 2026 announcement says it is rolling out support for custom Model Context Protocol (MCP) connections in Gemini Spark. Observed fact: the post explicitly says users can connect favorite apps directly to build a more tailored assistant. Observed fact: Google separately lists Google Tasks, Google Keep, Canva, Dropbox, Instacart, OpenTable and Zillow Rentals as connected apps, with those integrations rolling out first on web and mobile and later to macOS.
Mechanism: MCP offers a connection path for services outside the named integrations, potentially allowing user-assembled workflows; the announcement does not specify setup, permission, or client details. That could let users assemble workflows around their own services, but the announcement does not describe server requirements, permissions, approval controls, or which clients support custom connections. The practical distinction is between a published catalog of integrations and a user-configurable integration surface.
Why now: Google is broadening Spark across desktop work, connected applications and topic monitoring in one product update; custom MCP is part of that expansion rather than a standalone protocol announcement. First implication: Builders can assess whether existing MCP services can connect to Spark once the capability is available in their account and client.
Evidence boundary: Google says custom MCP support is rolling out but does not specify schedule, geography, subscription tier, client scope, setup details, or a security model; the source does not substantiate Gemini 4, Computer Use or Superprojects claims. The source does not substantiate claims about Gemini 4, Computer Use or Superprojects.
First watch condition: Look for Google’s follow-up documentation or product interface specifying custom MCP availability, setup requirements and permission boundaries. Until then, the announcement establishes a rollout, not universal access or a defined security model.