← Back to your news feed
TechnologyPrimary sourceSource analysis

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.

By The Impact of AI Editorial DeskReleased 28 October 2026 at 21:10 GMT3 min full report · 1 min summary2 sources · view evidence
Share
Social links
LinkedInXBlueskyRedditEmail

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.

Keep following the evidence

Join The Impact Brief founding list for selected AI reports, their effect on people and the evidence limits. Read a sample first.

Three AI findings, one useful evidence visual and links to the full reporting. See a sample. Our weekly briefing is prepared on Fridays; unsubscribe at any time.

Choose your topics (optional)

A welcome email follows signup. Unsubscribe at any time.

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

The documented workflow describes platform controls; it does not measure reliability or user understanding. Source: GoogleSource: Google for Developers
A laptop showing graphs of athletic performance data.

Illustrative photo · not a video frame

The Royal Society · 2 min 31 sec · Background explainer

What is artificial intelligence? | The Royal Society

YouTube loads only when you choose; playback starts when you press play.

A short introduction to artificial intelligence from the Royal Society. Start here for basic concepts, then use current reporting to explore what has changed.

Evidence check: Published in 2018, before today’s generative AI tools. Useful for basic concepts, rather than an overview of current capabilities.

Published 2018-11-28. Source checked 14 October 2026. Check captions on the publisher’s video page.

Explore current AI technology

Photo: ThisisEngineering / Unsplash · Licence

Share
Social links
LinkedInXBlueskyRedditEmail

Continue the story

Read next

All reports
Explore the full source and evidence record

What this means for people

  • 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.

Global context

Developers can target countries and languages, but Google has not published the preview's market coverage. Authentication rules, consumer protection and app availability vary across jurisdictions.

What the evidence does not yet show

  • 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

What to watch next

  • Preview eligibility and market coverage
  • Independent security review
  • Task-completion and error rates
  • User confirmation failures
  • Account revocation experience
  • Cross-product data boundaries

Living evidence record

Impact record IAI-1DBV6AV

Explore the full tracker

Evidence stage

Announced

Confidence

Supported

Reporting basis

Source analysis

Independent or research support

Not yet

Record status

Monitoring

Last checked

28 October 2026

Source trail

2 direct sources across 2 source types.

People impact

Documented in this record.

Uncertainty

Limits and next checks are explicit.

Stages describe the evidence available—not whether a technology is good or bad. See the public method.

Related-source reporting disclosure

This record analyses 2 linked source records around the same underlying development. The extra records add method, date or context, but they do not by themselves constitute independent replication of every performance claim or predicted outcome.

Evidence trail

Sources used for this report

Links checked 28 October 2026

Research question, topics and regions

Topics: Connected apps · Model Context Protocol · Gemini · Google Search · Developer platforms · User consent

Regions: United States · Global

This report is labelled source analysis. We summarise and analyse source material in our own words; company statements remain attributed claims until independently supported. Translated summaries preserve the meaning of the original source and link back to it. Read our editorial standards.

Reader commentary

What does this mean where you are?

Tell us what you have seen at work, in your community or in everyday life. A question is welcome too. No account is needed; we review notes before publishing them.

Explore commentary across the portal →

Do not include personal, confidential or unlawful information.

Published reader notes

0

No published reader notes yet. You can start the evidence-led discussion above.

Prefer a private correction or response? Contact the newsroom.