ai-toolstutorialshow-togoogledeveloper

How to Connect Your App to Gemini and Search

Step-by-step guide to the Connected Apps Platform for integrating services into Gemini and Google Search using MCP or Android AppFunctions.

November 1, 2026 Yum News

Google’s Connected Apps Platform, launched in preview on October 28, 2026, gives developers one place to bring their services into the Gemini app and Google Search. Users link an app once. After that, Gemini or AI Mode in Search can access authorized data and trigger actions when relevant.

This replaces one-off partnerships. You integrate with a remote MCP server or Android MCP via AppFunctions, register in Google Connected Console, test, and submit for review. You choose whether the app appears in Search, the Gemini app, or both.

More than 50 Connected Apps already exist across productivity, fitness, ticketing, and other categories. Partners such as Adobe, Peloton, and Calm show the model in action. Access opens in phases for U.S. developers first.

Why the Platform Matters

Connected Apps sit where users already work. A person can ask Gemini to build a playlist, check an order status, or book a class without switching apps. For developers, one integration reaches high-intent users on both surfaces.

The platform standardizes on the Model Context Protocol. You expose tools with clear schemas. Google handles discovery, authentication flow, and presentation. You control branding, including verified logos, and receive traffic, latency, and error metrics once live.

Person using a smartphone with multiple app interfaces

Choose Your Integration Path

Two complementary routes exist.

Remote MCP server is the recommended default. Host an MCP server on a public HTTPS endpoint. It works across Android, iOS, and web. Reuse existing APIs or an MCP server you already run. Add UI metadata if you want interactive widgets.

Android MCP uses the Jetpack AppFunctions library. Tools execute on the user’s device. This fits actions that need local context, current app state, or offline capability. Gemini on Android can call them directly.

If your app already exposes AppFunctions, the Android path is a natural extension. See our guide on adding AppFunctions to your Android app for implementation details.

Prerequisites

For the remote MCP path you need:

A public HTTPS MCP endpoint using Streamable HTTP transport.
OAuth 2.1 with PKCE for user authorization. Support Authorization Server Metadata for discovery.
Domain verification via a file at https://yourdomain/.well-known/google-connected-apps returning HTTP 200.
App metadata: name, short description, 512 imes512 icon, at least three capabilities, example questions, terms, and privacy policy URLs.

For Android MCP, implement AppFunctions and link the connected app to your Play listing in the console.

Apply for preview access through the interest form linked from developers.google.com/connected-apps.

Build and Test Your MCP Server

Define tools with clear system instructions, typed schemas, and safety annotations. Mark read-only tools and those that modify data. Deploy to a public HTTPS endpoint.

Test in Gemini Developer Mode. The interface shows tool schemas, an event log, and environment simulation for date, time, and location. Confirm authentication and tool calls behave as expected before console registration.

Developer working on a laptop with code on screen

Register in Google Connected Console

Once preview access is granted:

Sign in to Google Connected Console.
Create a connected app and accept the terms if required.
Enter the app name (used for @ mentions) and select a category. Category cannot be changed later.
Choose connection type: MCP server or Android MCP.
Configure the endpoint, authentication details, and public-facing card information.
Discover and sync tools.
Set up testers and a preview environment.
Submit for Google review.

After approval you control when the app publishes. Track usage metrics inside the console.

Security and User Experience Tips

Require explicit user confirmation for any action that changes data or spends money. Keep tool descriptions precise so Gemini selects the right one. Return only the data needed for the request.

Use OAuth 2.1 with PKCE. Support the required metadata endpoints so discovery works without manual configuration. For Android MCP, follow AppFunctions security practices and avoid exposing sensitive credentials.

Test the full user flow: account linking, tool invocation, and error handling. Monitor latency because slow tools degrade the conversational experience.

What Happens After Launch

Users discover the app through Gemini or Search settings and link their account. Once linked, the service becomes available in relevant conversations. Google may expand supported surfaces and markets over the coming months.

Existing partners will appear in Search in the weeks after the October 28 announcement. New submissions go through the same review process.

Conclusion

The Connected Apps Platform lowers the barrier to reaching users inside Gemini and Search. Start with a remote MCP server if you need cross-platform reach, or Android MCP if local execution matters. Apply for the preview, implement the protocol, register in the console, and submit for review.

Focus on a small set of high-value tools first. Clear schemas and solid authentication make the difference between a reliable integration and one that rarely gets selected.