Skip to main content
Glama
README.md
# 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
```json
{
  "mcpServers": {
    "android-mobile-mcp": {
      "command": "uvx",
      "args": ["android-mobile-mcp"]
    }
  }
}
```

### Prerequisites
1. Connect Android device via USB or network
2. Enable USB debugging on your Android device
3. 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

### Navigation

**`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

TDQS

A3.7/5.0

Scored across 9 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues