mobile_click
Click on a specific coordinate on the Android screen.
LABSCO SUMMARY
Coordinate-level Android automation, anchored to the UI the device actually reports.
Because mobile_click validates against the elements mobile_dump_ui returned, the agent taps real, interactive targets rather than guessed positions — so a flow of read-screen, tap, type, and screenshot stays grounded in the device's actual state.
What it is
A server that bridges an assistant to an Android device, exposing UI automation, app management, and screen capture so the agent can operate the phone by coordinate and by app.
What you get
- mobile_init connects to the device and must run first; mobile_dump_ui returns the screen's elements as hierarchical JSON with centre coordinates for interactive elements
- mobile_click, mobile_type, mobile_swipe, and mobile_key_press drive touch, text entry, gestures, and system buttons like BACK and HOME
- mobile_list_apps returns installed user apps and mobile_launch_app starts one by package name
- mobile_take_screenshot captures the current screen as an image for the model to view
Requirements
Runs through uvx; needs ADB installed and an Android device connected with USB debugging enabled.
Setup effort
One command — uvx android-mobile-mcp
USE CASES
01
Driving a flow through an app
mobile_launch_app opens the app, mobile_dump_ui reads the screen, and mobile_click and mobile_type act on the elements it found.
02
Reading what is on screen reliably
mobile_dump_ui returns interactive elements with their coordinates, so taps land on real targets.
03
Capturing the screen for the model
mobile_take_screenshot returns the current screen as an image the model can look at.
04
Entering text and navigating
mobile_type fills the focused field and mobile_key_press sends BACK or HOME to move around.
9 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
mobile_dump_ui
Get UI elements from Android screen as JSON with hierarchical structure.
Returns a JSON structure where elements contain their child elements, showing parent-child relationships. Only includes focusable elements or elements with text/content_desc/hint attributes.
mobile_init
Initialize the Android device connection.
Must be called before using any other mobile tools.
mobile_key_press
Press a physical or virtual button on the Android device.
mobile_launch_app
Launch an application by its package name.
mobile_list_apps
List all installed applications on the Android device.
Returns a JSON array with package names and application labels.
mobile_swipe
Perform a swipe gesture on the Android screen.
mobile_take_screenshot
Take a screenshot of the current Android screen.
Returns an image object that can be viewed by the LLM.
mobile_type
Input text into the currently focused text field on Android.
BEFORE YOU INSTALL
What to know first
Tools you get
9 tools when we connected.
Requires
uvx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 9 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"android-mobile-mcp": {
"command": "uvx",
"args": [
"android-mobile-mcp"
]
}
}
}uvx
TERMINAL
uvx android-mobile-mcp
