Google Puts Android MCP in Beta: Apps Talk to AI Agents

Google's AppFunctions API is now officially in beta, letting Android apps expose functions as tools that Gemini and other AI agents can call directly.

@sharedot

Google Puts Android MCP in Beta: Apps Talk to AI Agents

By @sharedot · · 6 pages

  • Programming
  • Android Mcp
  • Appfunctions
  • AI Agents
  • Gemini

Google's AppFunctions API is now officially in beta, letting Android apps expose functions as tools that Gemini and other AI agents can call directly.

What happened: AppFunctions goes officially beta

On October 31, 2026, the Google for Developers India account announced that Android MCP — the ability of an Android app to offer its functions as tools to AI agents — is "officially in beta."

The underlying interface, AppFunctions, is a platform API shipped with a Jetpack library: a developer annotates a Kotlin function with @AppFunction, documents it with a KDoc comment, and the KSP compiler generates a schema the OS indexes.

Any caller holding the EXECUTE_APP_FUNCTIONS permission — Gemini, another app, or a custom agent — can discover and run it from Android 16 onward. Google's own framing puts it bluntly: the app is the Android MCP server, and each AppFunction is one of its tools.

Why it's surprising: beta label outpaces the docs

The surprise is how uneven the rollout looks.

As Pasquale Pillitteri reports, the word "beta" appears only in the Google for Developers India post, while official documentation pages updated between October 22 and 28 still describe an experimental preview and the Jetpack library remains in alpha at version 1.0.0-alpha10.

The Gemini integration sits in a private preview gated behind the Early Access Program — registering at goo.gle › eap af does not guarantee access — meaning an app shipping AppFunctions today may have no assistant able to call it.

Google also stops short of saying existing MCP clients can invoke these functions, leaving compatibility with agents other than Gemini unproven.

The evidence so far is thin

Per the reporting, Matthew McCullough, Google's vice president of Product Management, wrote on the Android Developers blog in February 2026 about the "early, beta stages" and pointed to Samsung Gallery with Gemini on the Galaxy S26 series — the sample request was "show me pictures of my cat."

9to5Google noted the same day that Gemini was already using AppFunctions for Calendar, Notes and Tasks integrations. At Google I/O 2026 in May, AppFunctions was listed as an experimental preview, and Android 17 (API 37) expanded its capabilities in June.

There are still no figures on how many apps or users actually rely on it, and developers must wait for Android 17 to use the adb shell cmd app_function commands for testing.

What comes next: mandatory adoption and new stakes

The stakes rise in March.

According to Pasquale Pillitteri, Google's Apps Experience Program guidelines defer enforcement to the later of March 1, 2027 and three months after self-service registration opens; after that, apps in messaging, notes, calendar, tasks, health, shopping, travel, food, creativity, media and system tools must use AppFunctions for at least one relevant use case and pass mandatory integration tests.

Quality guidelines demand verb-plus-resource function names, forbid exposing passwords, financial data or private keys, and warn against parameter names like full_context that hoover up too much data.

For companies, every exposed function is a new door to the customer — but the user may never open the app.

It also lands as Google pushes developers harder on form factors: The Times of India reports that from next year the Play Store will evaluate how well apps and games perform on foldables, with adapted apps earning prime promotional placement.

Sources

  1. pasqualepillitteri.it › Google launches Android MCP in beta so apps can talk to AI agents
  2. timesofindia.indiatimes.com › Google is changing the way developers optimise apps for foldables: What it means for users

More on Programming