
This article is part of The MCP Guide. For the month in review, see our State of MCP reports.
Google's Connected Apps Platform is a new way to put your service inside the Gemini app and Google Search, and it runs on the Model Context Protocol (MCP). On 28 October 2026, Google launched a preview that lets developers connect a cloud-hosted MCP server, or an Android app through AppFunctions, then register, test and submit it in one console.
For a business with an MCP server, this is a second large distribution channel next to ChatGPT's plugin directory. Access is limited for now, so the practical step today is to get your server ready and apply.
Checked against: Google's announcement, the Connected Apps developer docs and TechCrunch's report on 2 November 2026. eSEOspace has not used the Connected Console.
Key Takeaways
- Google calls the platform "a unified way for more app developers to bring their capabilities directly into Gemini and Search."
- You integrate through a remote MCP server or through Android MCP using the AppFunctions APIs.
- Developers register, test and submit apps in the Google Connected Console, and choose Search, the Gemini app or both before review.
- Access opens in phases; TechCrunch reports a public preview for US developers who join a waitlist.
- Google's MCP guide asks for tool annotations on every tool and OAuth with PKCE for user sign-in.
What Google announced
The Google post, by Chips Mistry and Mai Lowe, group product managers for Search and the Gemini app, describes four parts:
- One integration for two surfaces. You build once and pick whether the app goes live in Search, the Gemini app or both.
- Two ways to connect. A cloud-hosted MCP server, or Android MCP using AppFunctions.
- One console. The Google Connected Console handles registration, testing and submission.
- Post-launch data. Developers can track traffic, latency and error rates, and keep control of brand details such as verified logos and authenticated accounts.
Google says it has launched more than 50 Connected Apps across Search and Gemini. Adobe, Experian, Localiza and Peloton are live in Gemini, with Search support "in the coming weeks." A Calm integration is coming to both.
On access, Google says: "We're opening access in phases, and will add more developers, markets, and Google products over the coming months." TechCrunch adds that the platform is "in public preview for U.S. developers who sign up for the waitlist." Google's own post does not name a country limit, so treat the US detail as reported, not official.
Why it matters for businesses
Until now, the main way to get an MCP server in front of Gemini users was one user at a time. The consumer Gemini app lets eligible US users add a custom app by URL, as our ChatGPT vs Gemini comparison explains. Connected Apps flips that: you submit once and, after review, people find your app inside Google's products.
The Search angle is what stands out. ChatGPT's plugin directory reaches ChatGPT and Codex users. Google's platform puts MCP-based apps inside Google Search as well. For marketing teams, that makes a well-described MCP server part of search visibility, which ties into our work on marketing an MCP server.
How the build process works
Google's MCP server developer guide lays out four phases.
| Phase | What you do | Notes from Google's guide |
|---|---|---|
| 1. Build | Develop a remote MCP server | "Declare explicit protocol annotations for every tool" |
| 2. Validate | Test locally with MCP Inspector | npx @modelcontextprotocol/inspector |
| 3. Deploy and test | Host on a public HTTPS endpoint, test in Gemini Developer Mode | Event Log, Tool Schemas and Authentication tabs |
| 4. Register | Configure the app in the Google Connected Console | Request access through the interest form first |
Tool annotations are required
Google asks you to mark read-only tools with readOnlyHint and state-changing or destructive tools with destructiveHint. You can also flag operations that need user confirmation in the console. If your server lacks annotations, add them before you apply. Our guide to MCP tool annotations explains each hint.
Interactive UI is optional
The guide says tool outputs can point to a UI resource with meta={"ui": {"resourceUri": "ui://..."}}. That is the MCP Apps extension, rendered "in secure sandboxed iframes." A text-only server still works.
Sign-in uses OAuth with PKCE
Google's OAuth guide says the platform uses the authorization code grant. PKCE with S256 is mandatory for OAuth 2.1. A few details stand out:
- Client registration. Google reads a
registration_endpointfor Dynamic Client Registration, or you enter a client ID and secret by hand. A server that supports Client ID Metadata Documents still needs aregistration_endpointfor now. That differs from the MCP spec, which marks Dynamic Client Registration as deprecated in 2026-07-28. - Redirect URIs. You must allowlist Google's
oauth-redirectURLs on googleusercontent.com. - Refresh tokens. Google asks servers to return the same refresh token on refresh rather than a rotated one, to support persistent linking.
- Scopes. Keep default scopes to the minimum your user journeys need.
If your server already follows the MCP authorization spec, plan time for these Google-specific points. Our MCP OAuth guide covers the general flow.
The Android path: AppFunctions
The second integration route is on-device. Android's AppFunctions page says the API lets apps "behave like on device MCP servers," with tools that run locally on Android 16 or higher. Android also says Gemini integration is in a private preview with trusted testers, and only a limited number of apps can reach the full pipeline. Read our AppFunctions vs MCP comparison before choosing this route.
What is still unknown
Several points were not documented on the pages we opened on 2 November 2026:
- Review criteria and how long review takes.
- Whether there are fees or revenue sharing.
- Which countries beyond the US will get access, and when.
- Usage limits, latency targets or minimum MCP spec version.
Google links a separate Connected Apps policy page. Read it before you apply, and do not promise a launch date to stakeholders until Google confirms access.
How to prepare now
- Confirm your server is remote and on HTTPS. Local stdio servers do not qualify for the cloud route.
- Add tool annotations to every tool, and keep destructive tools few.
- Check your OAuth setup against Google's guide, especially the
registration_endpointand refresh token rules. - Test with MCP Inspector, then in Gemini Developer Mode once you have access.
- Write clear tool and app descriptions. They decide when Gemini picks your tool.
- Apply for the preview through the link on developers.google.com/connected-apps.
Next step
If you want your service in Gemini, Search, ChatGPT and Claude, the same well-built MCP server can serve all four. Our MCP development team builds and hardens servers for these directories, and our MCP marketing team handles listings and descriptions.
More in the MCP Guide
Latest research: State of MCP: October 2026
Frequently asked questions
What is Google's Connected Apps Platform?
It is a preview program, launched 28 October 2026, that lets developers bring their services into the Gemini app and Google Search. Developers connect a remote MCP server or an Android app using AppFunctions, then register and submit it in the Google Connected Console.
Is the Connected Apps Platform open to everyone?
Not yet. Google says access is opening in phases, and developers apply for the preview. TechCrunch reports it is for US developers who join a waitlist. Google has not given a date for broad availability.
Do I need an MCP server to use it?
For web services, yes: the cloud route uses a remote MCP server on a public HTTPS endpoint. Android apps can instead use AppFunctions, which Google calls Android MCP. Both are described in Google's developer docs.
Can my app appear in Google Search, not just Gemini?
Yes, if Google approves it. Before review, you choose Search, the Gemini app or both. Apps already in Gemini, such as Adobe and Peloton, are coming to Search in the following weeks, according to Google.
Does Google require Dynamic Client Registration?
Google's OAuth guide reads a registration_endpoint, or lets you enter a client ID and secret manually. It says servers that support Client ID Metadata Documents still need a registration_endpoint for now, even though the MCP spec deprecated Dynamic Client Registration.











