Google just shipped an on-device MCP layer for Android, and most developers haven't noticed yet.

What it is: AppFunctions is a Jetpack library that lets Android app developers register their app's actions as agent-callable tools indexed directly by the OS.

The question Google is answering here is structural: who owns the integration layer between AI agents and native apps? AppFunctions makes that layer the OS itself developers declare functions using annotations, the Android platform indexes them, and authorized agents can discover and execute them without any network dependency. It's the mobile equivalent of an MCP server, except the "server" is the device.

What makes it different: The architectural trade-off is explicit in the docs. MCP is platform-agnostic but requires cloud infrastructure. AppFunctions are Android-exclusive but run entirely on-device with zero latency from a network round-trip and direct access to live app state. For developers already building on Android, that trade-off is compelling.

Key features:

Annotate Kotlin functions with @AppFunction the library generates the schema automatically
OS-level indexing means any authorized agent can discover your app's tools without a direct integration
Supports multi-step, cross-app workflows: an agent can chain functions from an email app and a shopping list app in a single user request
Tested across 25 app use cases at device manufacturer level before public announcement
Requires Android 16 or higher

Benefits:

Your app's capabilities become part of the OS-level agent ecosystem without maintaining additional infrastructure
Users can invoke app functionality through natural language without opening your UI
Gemini handles task automation across form factors: phone, watch, car, glasses
Early movers in the EAP will have a head start on the experience before GA

Who it's for: Senior Android engineers and developer platform teams at companies with established Android apps who want to surface app functionality through Gemini and future OS agents.

What stood out to me is the timing. The MCP standard has driven a wave of server-side integrations over the past year. AppFunctions is Google's argument that for mobile, the right place to run that layer is the device, not the cloud. If that position holds, the apps that build AppFunctions first have a structural advantage in agentic discovery.

Note: Experimental preview only. EAP registration is open but access is selective.

I hunt the latest and greatest launches in tech, SaaS and AI, follow to be notified.