Latest in AI
Google Connected Apps Platform: MCP Integration, Preview Access and How It Works
Google is opening a shared developer path into Gemini and Search, with app review and reliable actions becoming part of the distribution work.
Google announced a preview of its Connected Apps Platform on October 28. Developers can prepare one integration for Gemini and Search, choose where it appears, and manage submission through a shared console. The important change is a broader developer distribution path, rather than the first arrival of third-party apps.
What Google Connected Apps Platform adds
The announcement describes a phased preview. Google Connected Console handles registration, testing and submission, then offers traffic, latency and error-rate monitoring after publication. Developers choose Search, the Gemini app, or both before review.
Google also says Adobe, Experian, Localiza and Peloton integrations are live in Gemini and will reach Search in the coming weeks. Calm is planned for both. Those future rollouts should not be confused with apps already available in each product.
For a founder, an integration becomes another product surface to maintain. Someone asking an assistant to complete a task may never visit the landing page that normally explains the service. The app's tool descriptions, account connection and returned results now carry more of that explanation.
MCP server or Android AppFunctions?
The platform overview describes two complementary paths. A remote Model Context Protocol server exposes authorized data and actions across supported Google products. Android AppFunctions expose native app capabilities, including actions that need local device context.
The MCP developer guide recommends the remote-server route for foundational cross-platform features. It can reuse existing web APIs or an MCP server and work across Android, iOS and web. AppFunctions suit deeper Android-specific behavior rather than replacing that route for every app.
For example, a service that manages bookings might expose availability and reservation actions remotely. A feature that depends on the current state of its Android app may need the native path. Developers should choose around where the capability lives, not merely which protocol sounds newer.
How developers prepare an integration
Google's guide lays out a build, test, deploy and register workflow. Tools need clear schemas and descriptions, plus annotations distinguishing read-only operations from destructive actions. Operations requiring confirmation can be marked in Connected Console.
The server is tested locally with MCP Inspector, then hosted on a public HTTPS endpoint. Google permits the developer's preferred hosting infrastructure. Gemini Developer Mode provides debugging views before the app is submitted for review and publication.
This creates a practical quality bar beyond having an endpoint that returns JSON. A useful test suite should include ambiguous requests, expired authorization, missing records and retries after a timeout. For a booking action, the dangerous failure is a duplicate reservation, not an unattractive response.
Successful tool execution and successful user intent are different checks. A server can return a valid result for the wrong date or account. Those cases deserve explicit tests before more distribution makes them harder to notice.
Preview access and user availability
Developers can request access through the platform's preview application. This is phased access, not a promise that every submitted app can immediately go live. The primary announcement does not provide a universal expansion date.
User eligibility also varies by integration. Google's Connected Apps requirements table separates account type, age, region, language and supported experience. Peloton, for example, is listed for personal accounts aged 18 or older in the US, in English. A platform spanning two Google products does not make every partner app available everywhere.
The distribution opportunity is real, but it comes with operational responsibility. Teams should watch whether users can connect an account, complete the intended action and recover safely when something fails. Those are more useful early signals than assuming that app submission will automatically produce traffic or revenue.
I'm Paras. I work at the intersection of AI, engineering and distribution.
I help technical founders explain new integrations and product capabilities through clear launch stories and founder-led content.