Google opens Connected Apps Platform preview for MCP tools inside Search and Gemini

On October 28, 2026, Google launched a phased preview of its Connected Apps Platform. Developers can expose an existing service through a cloud-hosted Model Context Protocol (MCP) server or Android AppFunctions, test it, and submit it for review through Google Connected Console. A developer can choose Search, the Gemini app or both; approved connected apps can show authenticated service data and perform authorised actions for users who link them. Google says it has more than 50 connected apps across its products, but developer acceptance and user distribution are not guaranteed. The developer guide calls for OAuth 2.1, tool safety annotations and HTTPS deployment. Google's policy bans third-party advertising within connected app tools and prohibits mere unauthorised pass-through wrappers of another platform's API.

For indie SaaS builders and API-first products, Search and Gemini may become another way customers invoke a service without visiting its site. A small business with a genuinely useful workflow can build one MCP integration and potentially reach both surfaces, but it still needs approved access, user consent and reliable execution. This is a platform integration channel, not a new SEO ranking trick: discovery, approval, distribution, revenue-sharing and conversion impact remain unproven. The policy also affects business models: connected apps cannot simply inject ads or disguise third-party API wrappers.

Google's announcement and developer documentation describe a unified workflow for building, testing and submitting a Connected App. Developers can choose Search, Gemini or both; Google Connected Console handles registration, testers, authentication and review. The platform is in preview and opening in phases, with no general availability date. Third-party reporting describes the current developer beta as US-focused, so do not assume worldwide onboarding.

Google recommends a remotely hosted MCP server for cross-platform integrations, with Android AppFunctions as an alternative for local mobile actions. The MCP guide asks developers to publish explicit tool schemas and descriptions, mark read-only and destructive actions, and optionally bind tools to interactive UI resources. Developers validate with MCP Inspector, host over HTTPS and test live execution in Gemini Developer Mode before submitting.

Google's developer guide says a connected app can be explicitly invoked by mentioning its name or using @, and remains available in relevant session context. Users link their account and grant permissions. A successfully approved app does not guarantee every Search user sees it, and Google's announcement supplies no ranking formula, placement guarantee, traffic baseline or conversion results. Treat claims of an automatic new SEO channel with caution.

The platform policy requires useful, reliable standalone functionality, minimal data collection, transparent permissions and appropriate user controls. It prohibits third-party promotional material or ads within connected app responses, deceptive tool descriptions, hidden functions and wrappers that primarily pass through another provider's APIs without rights. The documentation calls for OAuth 2.1 and safe annotations; developers should still enforce their own server-side authorization and confirmation for consequential actions.

Choose a real workflow customers already perform through an authenticated API, define a narrow MCP tool surface, validate error handling and permissions, and apply for preview access. Instrument tool calls, latency, failures and the effect on completed tasks. Do not promise distribution, leads or revenue until Google accepts the integration and actual usage data exists.