Android MCP Server
Android device navigation and UI interaction via native ADB accessibility APIs.
Data last scanned yesterday · Reviewed last month
Overview
Android MCP allows AI agents to interact directly with mobile interfaces by leveraging ADB and the Android Accessibility API. This setup enables models to launch applications, perform gestures like swipes and taps, input text, and analyze view hierarchies without needing complex computer-vision pipelines or OCR.
Our verdict
This server receives a security score of 45/100, indicating a high risk level. Critical security aspects, including OAuth, read-only mode, and authentication methods, have not yet been editorially reviewed. Given the tool's capability to execute shell commands and interact with device states, it is recommended only for developers testing in isolated, non-production environments.
- Supports Android 10 and newer devices or emulators
- Requires zero direct dependencies
- Offers broad set of mobile automation tools
- Maintains an active development cycle
- High security risk due to unreviewed authentication
- No official vendor maintenance
- Unreviewed read-only mode
Tools
| Tool | Description | Risk |
|---|---|---|
| State-Tool | Understand the state of the device or get a combined snapshot of active apps and interactive UI elements. | low |
| Click-Tool | Click on the screen at the given coordinates. | medium |
| Long-Click-Tool | Perform long click on the screen at the given coordinates. | medium |
| Type-Tool | Type text on the specified coordinates (optionally clears existing text). | medium |
| Swipe-Tool | Perform swipe from one location to other. | medium |
| Drag-Tool | Drag from one point to another. | medium |
| Press-Tool | Press the keys on the mobile device (Back, Volume Up, etc). | medium |
| Wait-Tool | Pause for a defined duration. | low |
| Notification-Tool | Access the notifications seen on the device. | low |
| Shell-Tool | Execute shell commands on the android device. | high |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›What are the core technical requirements to run Android-MCP?
You need Python 3.13, the Android Debug Bridge (ADB) installed, and a device or emulator running Android 10 or higher.
›How does the server choose which Android device to connect to?
If no specific device is set, the server auto-detects connected devices and prefers physical devices over emulators. You can override this by using the --device flag with a serial number or setting the ANDROID_MCP_DEVICE environment variable.
›Can I connect to a device over WiFi instead of USB?
Yes, you can configure WiFi connections by providing the host address via the ANDROID_MCP_HOST environment variable or the --wifi flag.
›Why is my device not showing up when I run adb devices?
If the list is empty or displays 'unauthorized', you should verify that USB debugging is properly enabled in your Android device's developer settings.
›What is the typical performance latency for automated actions?
The typical latency between actions, such as two consecutive taps, ranges from 2 to 4 seconds depending on the load and your device's specifications.
›Are there specific version requirements for Windows users?
Yes, Windows users must use Python 3.13 for uvx, as Python 3.14 fails to resolve a required transitive dependency used by the MCP stack.
Alternatives
Changelog
- Improvedv0.2.0
2026-05-14
- Securityv0.1.0 — Initial Release
2026-05-14
Badge
Maintain this server? Add the live badge to your README.