"Android MCP" now means two different things. Google uses the name for AppFunctions: your Android app declares functions, and Gemini or another authorized assistant calls them on the device, on Android 16 or later. The other meaning is an Android MCP server such as Mobilebox: any MCP client (Claude Code, Cursor, Codex, ChatGPT) gets a cloud Android phone and uses any app through its screen, at $0.01 a phone-minute.

Sources reviewed on November 21, 2026: Google’s AppFunctions overview, the Apps Experience Program guideline Android MCP, Create and manage Connected Apps and the Connected Apps Platform. Each Google fact below quotes those pages.

Google’s Android MCP: AppFunctions

AppFunctions is an Android platform API with a Jetpack library. Google says it lets apps "behave like on-device MCP servers": you annotate a Kotlin function with @AppFunctionDeclaration, its KDoc becomes the description an agent reads, and the library generates a schema the OS indexes. A notes app might expose createNote, a calendar app createCalendarEvent.

  • Who calls them: an app can call its own functions. Calling another app’s functions needs the EXECUTE_APP_FUNCTIONS permission, which Android grants only to authorized system assistants such as Gemini.
  • Where they run: on devices with Android 16 or later. AppFunctions is an experimental preview and the API may change.
  • Gemini access: apply for the Connected Apps Platform developer preview, create an Android MCP connected app in Google Connected Console and upload your app bundle to a testing track. Each Play app links to one Android MCP connected app.
  • Timeline: in Google’s Apps Experience Program, Android MCP is optional for now; enforcement waits until March 1, 2027 or three months after self-service registration opens, whichever is later.
  • Local check: adb shell cmd app_function list-app-functions --package <your.package> lists what the device registered.

An Android MCP server: the agent uses the phone

Add https://mobilebox.dev/mcp to your MCP client and sign in once. The agent gets tools such as create_phone, install_app, observe, act, screenshot and park_phone. It creates a phone, installs any APK, reads the screen as numbered elements and taps, types and swipes. The app needs no changes, so this works for your own app under test and for apps you don’t own. Mobilebox runs cloud Android 14 phones, iPhone and iPad, and real Android devices; cloud Android costs $0.01 a phone-minute, billed per second, and a parked phone keeps its apps and logins for free.

Side by side

AppFunctions (Google’s Android MCP)Android MCP server (Mobilebox)
Who does the workThe app developer adds Kotlin functionsNothing changes in the app
Who calls itGemini and other authorized assistants on the deviceAny MCP client: Claude Code, Cursor, Codex, ChatGPT
What the agent seesTyped functions and their KDocThe screen: numbered elements and screenshots
Apps you don’t ownOnly if they ship AppFunctionsAny APK
DeviceThe user’s own phone, Android 16 or laterCloud Android 14 phones, real Android devices, iPhone and iPad
StatusExperimental preview; Gemini through a developer previewLive, $0.01 per phone-minute

How to decide

  • You ship an app and want Gemini to act in it: build AppFunctions. It is Google’s route, and the one its Apps Experience Program will check.
  • Your coding agent should test your app, or finish a task in an app: use an Android MCP server. The agent works through the same screens your users see.
  • Both: AppFunctions cover what an assistant can call. The screens your users tap still need a check on every pull request, and a cloud phone per PR does that; see agent PRs that break only on Android.

Every Mobilebox tool, and how hosted compares with local servers: Android MCP server.