MCP server for Android development - build, device, debug, and scaffolding tools
The server provides 33 well-structured tools with consistent naming patterns (verb_noun: apk_analyze, device_list, app_launch, etc.). Most tools have clear, actionable descriptions (100-250 chars) and explicit parameter schemas with types and descriptions. However, there are systematic gaps: (1) Output schemas are not documented in the visible source, only input schemas are visible; (2) Error handling guidance is absent, tools do not describe recovery paths or retryability; (3) Some parameter descriptions lack detail on constraints (e.g., what constitutes a valid 'package name'?); (4) No tool defines permission requirements or security considerations. The server follows composition principles well (each tool has one clear responsibility) and naming is consistently verb-first, making tool selection straightforward for LLMs. Overall, this is a solid mid-range implementation with good naming and parameter coverage, but missing the polish (documented outputs, error recovery guidance, security annotations) that would elevate it to A-grade.
Connect to a device over WiFi ADB. Switches to TCP/IP mode, detects IP, and connects wirelessly
Disconnect a WiFi ADB connection
Analyze an APK file: size, version, SDK targets, DEX references, and optionally full file listing and manifest
Install an APK file on a connected Android device or emulator
List all permissions declared in an APK file
Clear all data for an installed app (equivalent to clearing storage in settings)
Launch an Android application on a connected device by package name
No output schemas documented for any tool. Only input schemas are visible in the source code. LLMs cannot plan downstream tool chains without knowing what fields are returned.
Error handling and recovery guidance is absent. Tools do not document whether errors are retryable, what the LLM should do if a call fails, or which errors are user-fixable vs. fatal.
Parameter descriptions lack constraint details. For example, 'packageName' is described only as 'Application package name' without explaining format (must match Java package naming: dot-separated identifiers) or examples of what is/isn't valid.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 61 | 2025-06-18+ | v2 |
| 2026-03-09 | D | 59 | - | v1 |
Grant or revoke a runtime permission for an app
List all permissions for an installed app, showing which are granted and which are denied
Force stop an application on a connected Android device
Create a new Android Virtual Device (AVD) with specified configuration
List all available Android Virtual Devices (AVDs)
Send an Android broadcast intent
Test a deep link URI on a connected Android device. Opens the URI with ACTION_VIEW
Get detailed information about a connected Android device including model, OS version, screen density, and more
List all connected Android devices and running emulators with their status
Capture a screenshot from a connected Android device and return it as a base64-encoded PNG
Execute an arbitrary ADB shell command on a connected Android device. Use with caution
Start an Android emulator by AVD name. Returns once the device has booted or after timeout
Stop a running Android emulator
Pull a file or directory from a connected Android device to the local machine
Push a file or directory from the local machine to a connected Android device
Send an Android intent to start an activity with optional action, data URI, component, and extras
Clear the logcat buffer on a connected Android device
Read Android logcat output with optional filtering by tag, priority level, or search string
Create a new Android project with Kotlin and Gradle KTS, optionally with Jetpack Compose
Generate a new Activity Kotlin file from a template and add it to an existing Android project
Generate a new Jetpack Compose screen file with a composable function and preview
Generate a new Fragment Kotlin file from a template
Record the device screen as an MP4 video and save it locally
Install Android SDK packages (system images, build tools, platforms, etc.)
List installed or available Android SDK packages, system images, and build tools
Dump the current screen's UI hierarchy (view tree) as XML using UI Automator. Useful for understanding what's displayed on screen
No permission/scope annotations. Tools like device_shell (DESTRUCTIVE), app_clear_data (DESTRUCTIVE), and intent_send (DESTRUCTIVE) lack explicit documentation of what permissions or trust levels are required to invoke them safely.
Missing tool composition guidance. No multi-tool prompts document workflows like 'test a deep link: first ensure the app is installed (apk_install), then call deeplink_test' or 'debug a crash: clear logcat, launch app, reproduce, read logcat'. Prompts exist (debug-crash, setup-emulator) but are minimal.
device_shell accepts arbitrary ADB shell commands without constraints or validation guidance. Description says 'Use with caution' but provides no mechanism (e.g., allowlist, confirmation) to prevent misuse.