Android Mobile MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mobile_initA | Initialize the Android device connection. Must be called before using any other mobile tools. |
| mobile_dump_uiA | 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_clickC | Click on a specific coordinate on the Android screen. Args: x: X coordinate to click y: Y coordinate to click |
| mobile_typeA | Input text into the currently focused text field on Android. Args: text: The text to input submit: Whether to submit text (press Enter key) after typing |
| mobile_key_pressC | Press a physical or virtual button on the Android device. Args: button: Button name (BACK, HOME, RECENT, ENTER) |
| mobile_swipeC | Perform a swipe gesture on the Android screen. Args: start_x: Starting X coordinate start_y: Starting Y coordinate end_x: Ending X coordinate end_y: Ending Y coordinate duration: Duration of swipe in seconds (default: 0.5) |
| mobile_list_appsA | List all installed applications on the Android device. Returns a JSON array with package names and application labels. |
| mobile_launch_appB | Launch an application by its package name. Args: package_name: The package name of the app to launch (e.g., 'com.android.chrome') |
| mobile_take_screenshotA | Take a screenshot of the current Android screen. Returns an image object that can be viewed by the LLM. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose with no overlap. Clicking, UI dumping, initialization, key pressing, app launching, app listing, swiping, screenshotting, and typing are all unique operations in Android automation. The descriptions reinforce this distinction, making tool selection unambiguous.
All tools follow a consistent 'mobile_' prefix with descriptive verb_noun combinations (e.g., mobile_click, mobile_dump_ui, mobile_launch_app). The naming pattern is uniform throughout, using snake_case and clear action-oriented verbs that align with their functions.
With 9 tools, this server is well-scoped for Android mobile automation. It covers essential operations like interaction (click, swipe, type), navigation (launch apps, key press), and inspection (UI dump, screenshot, list apps), plus initialization. Each tool earns its place without redundancy or bloat.
The toolset provides strong coverage for core Android automation tasks, including UI interaction, app management, and screen inspection. A minor gap exists in more advanced operations like handling permissions, accessing device settings, or interacting with specific UI elements by ID, but agents can work around this with the available tools.