Android MCP Goes Beta: Apps Become Tools for AI Agents
By @sharedot · · 6 pages
- Programming
- Android
- AI Agents
- Mcp
Google declared its AppFunctions API officially in beta on October 31, letting Android apps expose functions as tools for Gemini and other AI agents.
What happened: Google calls AppFunctions 'officially in 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 enabling interface is AppFunctions, a Jetpack library through which an app declares actions like creating a note or adding an expense, with the operating system acting as a registry of the tools available to agents. The app is the Android MCP server and each AppFunction is one of its tools.
It is the same MCP (Model Context Protocol) pattern agents like Claude, ChatGPT and Gemini use to connect to services, now moved from the browser to the phone.
Why it's a surprise: the beta label outpaces the docs
The beta announcement outruns Google's own documentation.
As Pasquale Pillitteri reports, the documentation pages updated between October 22 and 28 still describe AppFunctions as an experimental preview, and the Jetpack library itself remains in alpha, meaning function signatures may still change before production use.
The Gemini integration is in private preview only, and registering for the Early Access Program does not guarantee access.
Per Pillitteri, Google has also not shown that an existing MCP client other than Gemini can invoke these functions, and the only public examples are Samsung Gallery on the Galaxy S26 series and Gemini's Calendar, Notes and Tasks integrations.
How it works and what developers must expose
Developers annotate a Kotlin function with @AppFunction and describe it with a KDoc comment; the KSP compiler generates a schema that Android indexes, and callers need the EXECUTE_APP_FUNCTIONS permission to discover and run functions.
The API requires Android 16 or later and compileSdk 36, while the adb testing commands require Android 17.
Once quality rules apply — by March 1, 2027 at the earliest — apps in categories like messaging, notes, calendar, tasks and shopping will need at least one AppFunctions use case and must pass mandatory integration tests, per the Pasquale Pillitteri report.
Google's guidelines also forbid exposing passwords, financial data or private keys.
The stakes: discovery shifts from Play Store to agents
The same Android Dev Summit week brought a parallel discovery shift: according to The Times of India, Google said the Play Store will start evaluating next year how well apps perform on foldable screens, with well-adapted apps earning prime promotional placement.
Google also rolled out AI-powered developer tools — a Compose adaptive skill that audits compact interfaces and scales them across foldables, tablets and XR headsets, plus automatic desktop-grade controls and tabletop refactoring — per the Times of India report.