Android Mobile MCP

Overview

Android Mobile MCP bridges the Model Context Protocol with Android device automation, enabling AI agents to interact with Android devices through UI manipulation, app management, and screen capture.

MCP Configuration

{
  "mcpServers": {
    "android-mobile-mcp": {
      "command": "uvx",
      "args": ["android-mobile-mcp"]
    }
  }
}

Prerequisites

Connect Android device via USB or network
Enable USB debugging on your Android device
Install ADB (Android Debug Bridge)

Tools Reference

Screen Analysis

mobile_dump_ui - Extract UI elements as hierarchical JSON

Parses screen XML to identify focusable elements and text content
Calculates center coordinates for each interactive element
Returns structured parent-child element relationships

mobile_take_screenshot - Capture current screen state

Returns PNG image data for visual analysis

Touch Interactions

mobile_click - Click at specific coordinates

Validates coordinates against current UI state
Requires prior mobile_dump_ui call for coordinate verification
Prevents clicking on invalid or non-interactive areas

mobile_swipe - Perform swipe gestures

Executes directional swipes between two coordinate points
Configurable duration for gesture speed control

Text Input

mobile_type - Input text into focused fields

Sends text to currently active input field
Optional automatic submission with Enter key

mobile_key_press - Press system buttons

Supports hardware and virtual keys: BACK, HOME, RECENT, ENTER

App Management

mobile_list_apps - List installed applications

Filters out system apps and non-launchable packages
Returns only user-accessible applications

mobile_launch_app - Start applications by package name

Validates package existence before launch attempt

Metadata

Release files for android-mobile-mcp 2.4.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for android-mobile-mcp 2.4.1
File	Size	Uploaded
android_mobile_mcp-2.4.1.tar.gz	5.4 kB	Sep 16, 2025	Details

Built distribution (wheel)

Table of built distributions (wheels) for android-mobile-mcp 2.4.1
File	Interpreter	ABI	Platform	Reset
android_mobile_mcp-2.4.1-py3-none-any.whl 5.3 kB Sep 16, 2025	Python 3	none	any	Details

Total release size: 10.7 kB

Release files / android_mobile_mcp-2.4.1.tar.gz

Download URL	android_mobile_mcp-2.4.1.tar.gz
Size	5.4 kB
Tags	Source
SHA-256 checksum How to use checksums	`2f1c0f0187e251824ec397728ce97b347282e7c617a5dd948117490f02b98d6c`
BLAKE2b-256 checksum How to use checksums	`61d2643ef035e5b3c7d49ddc4f37204ccf451f288330191ca81d054938cf8d37`
Upload date	Sep 16, 2025
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/6.1.0 CPython/3.13.7`

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/erichung9060/Android-Mobile-MCP
Publishing commit: github.com/erichung9060/Android-Mobile-MCP/tree/b52b2c9f1a3596afb9740eac1a3bc4df653e042b

Workflow

Publishing configuration: github.com/erichung9060/Android-Mobile-MCP/blob/b52b2c9f1a3596afb9740eac1a3bc4df653e042b/.github/workflows/publish.yml
Publishing logs: github.com/erichung9060/Android-Mobile-MCP/actions/runs/17760165374/attempts/1

Artifact

Subject: android_mobile_mcp-2.4.1.tar.gz
SHA-256 checksum: 2f1c0f0187e251824ec397728ce97b347282e7c617a5dd948117490f02b98d6c Verifying attestations

Release files / android_mobile_mcp-2.4.1-py3-none-any.whl

Download URL	android_mobile_mcp-2.4.1-py3-none-any.whl
Size	5.3 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`16182783373be9fec6a49c8ebf766510a396dbe9bfbcc265a6326d042357269a`
BLAKE2b-256 checksum How to use checksums	`8e0e8616aaab4fcfa04854f9bdf5f2a9afad30c6315170cc5c9ac7e9338f7345`
Upload date	Sep 16, 2025
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/6.1.0 CPython/3.13.7`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/erichung9060/Android-Mobile-MCP
Publishing commit: github.com/erichung9060/Android-Mobile-MCP/tree/b52b2c9f1a3596afb9740eac1a3bc4df653e042b

Workflow

Publishing configuration: github.com/erichung9060/Android-Mobile-MCP/blob/b52b2c9f1a3596afb9740eac1a3bc4df653e042b/.github/workflows/publish.yml
Publishing logs: github.com/erichung9060/Android-Mobile-MCP/actions/runs/17760165374/attempts/1

Artifact

Subject: android_mobile_mcp-2.4.1-py3-none-any.whl
SHA-256 checksum: 16182783373be9fec6a49c8ebf766510a396dbe9bfbcc265a6326d042357269a Verifying attestations