Google Connected Apps Platform: Apps Inside Search and Gemini

November 3, 2026. On 28 October 2026 Google opened a preview of its Connected Apps Platform, which lets a business put its own service inside Google Search and the Gemini app. A user links an account once, then checks data or takes an action in that service from the conversation. The route in is a cloud-hosted MCP server, or Android MCP through the AppFunctions APIs, registered and submitted for review in the new Google Connected Console. Google says access opens in phases, and TechCrunch reports the preview is open to US developers who join a waitlist.

What Google launched on 28 October

Google's announcement, by Chips Mistry of Search and Mai Lowe of the Gemini app, and its developer overview describe five pieces:

1. Two ways in. "Developers integrate with a cloud-hosted MCP server or Android MCP using the AppFunctions APIs." The MCP route uses OAuth 2.1 so Gemini can act "on behalf of users".
2. One console. The Google Connected Console handles tool registration, testing, usage analysis, review and publishing, with self-service onboarding during the preview.
3. A choice of surfaces. "Before review, developers choose whether it will go live in Search, the Gemini app, or both."
4. Reporting and branding. Once an app is live, developers "can track traffic, latency, and error rates" and keep "verified logos and authenticated accounts".
5. Phased access. Google will "add more developers, markets, and Google products over the coming months". It counts more than 50 Connected Apps across Search and Gemini; Adobe, Experian, Localiza and Peloton are live in Gemini and come to Search "in the coming weeks", and Calm is launching on both.

The rules that matter before you build

Google's platform policies set limits on what a connected app can be:

1. No ads. Partners "must not serve any third party advertising content or promotional material through their integrations", though your own brand elements are allowed.
2. No agent relays. An app "must not act as a proxy for, connect to, or facilitate communication with other AI agents that can perform actions autonomously."
3. Confirmation for risky actions. Tools that delete data, change access controls or "execute financial transactions" need the destructiveHint annotation or a required human confirmation.
4. No dynamic tool lists. Tools "must not expose dynamic discovery functions (e.g., list_tools, get_schema) or generic runtime dispatchers".
5. Enforcement. Google can reject an app at submission, suspend or remove it, or terminate the developer account.

Google has not published a fee, review times or how Search chooses between competing apps in the pages we read.

What it means for operators

TechCrunch compared it to SEO, calling it possibly "one of the initial steps for businesses that want their services to be more visible to users on the agentic web". Our view: this route suits businesses with something to connect, such as bookings, orders, accounts or quotes; a brochure site has no live account data or action to expose.

If you already run a customer portal or booking system, we would apply for the preview, start with one or two read-only tools, plan OAuth 2.1 sign-in from the start, and mark anything that writes data for confirmation. If you do not, being cited in AI answers is the other route; see our AI search optimization service. For an MCP server build, see hire an AI engineer. Related: Google's shared AI training control in robots.txt, ads in Google AI Mode and tracking AI traffic in GA4.