One connected app can now reach Gemini and Search—but the preview has no outcome data
Google’s platform standardises MCP and Android integrations across its products. Developers can apply for preview, while adoption, consent, reliability and task-success measures have not been published.
The short version
- What happened
- Developers can apply to expose one cloud-hosted MCP server or one Android MCP integration across eligible Google products, including Gemini and Search.
- Who it affects
- Users may be able to complete bookings, purchases or account tasks without leaving Search or Gemini. The same convenience makes clear confirmation, least-privilege access and easy revocation important when tools can act on personal accounts.
- What remains unproven
- Developer preview
Keep in mind
Developer preview
Phased availability
No eligible-developer denominator
No user-adoption count
No task-success or error rates
No consent-comprehension measure
Company sources only
Source analysis · 2 linked sources. Primary analysed source date: 28 October 2026.
Read the full report · 3 min The evidence, methods, implications and limitations
The platform turns one integration into several product surfaces
Google is opening a developer preview for Connected Apps, a platform intended to let one service work in both Gemini and Search. Cloud services can expose tools and authorised data through a hosted Model Context Protocol server; Android apps can use AppFunctions so execution happens on the device.
Developers register in Connected Console, verify their domain, sync tools, choose products, countries and languages, add testers and submit a version for Google review. Published apps can use account context and take actions, with user confirmation required when a tool is marked destructive.[1][2]
A platform launch is not evidence that tasks work well
Google says more than 50 Connected Apps have launched across Search and Gemini and names partners including Adobe, Experian, Peloton and Calm. That establishes product activity, but the announcement does not report how many developers applied, how many users linked accounts or how often actions completed correctly.
For people, the practical test is whether account linking, confirmation and revocation remain understandable when the same service appears across products. Independent security review, task-success and error rates, unwanted-action reports and consent withdrawal data would show whether the common integration reduces friction without expanding mistakes or data exposure.[1][2]
The distinction that matters
How a connected app reaches a user
The developer path has several controls before publication, but outcome evidence begins only after real use.
Build
Expose MCP or Android AppFunctions
One registered connected app
Review
Verify, test, target and submit
Google approval before publication
Use
Link an account and invoke a tool
Success and consent evidence not yet published