Android-MCP
MCP Server for interacting with Android Devices.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/CursorTouch/Android-MCP with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/CursorTouch/Android-MCP'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/cursortouch--android-mcp)HTML
<a href="/listings/cursortouch--android-mcp"><img src="/api/listings/cursortouch--android-mcp/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
📦 Prerequisites
- Python 3.13 - ADB (Android Debug Bridge) - Android 10+ (Emulator/ Android Device)
📲 Testing ADB Connection
Before running the server, ensure your Android device is connected and recognized by ADB:
1. Connect your Android device via USB or ensure your emulator is running. 2. Open a terminal and run:
adb devices
3. You should see your device listed:
List of devices attached R38M30XXXXX device
The serial number will differ per device. Emulators show serials like `emulator-5554`. If the list is empty or shows "unauthorized", check your USB debugging settings on the device.
For WiFi ADB, connect the device first:
adb connect 192.168.1.3:5555 adb devices
🏁 Getting Started
You can run the Android MCP server using **UVX** (recommended) or **UV** (for local development).
Option 1: UVX (Recommended)
No need to install dependencies manually. Just configure Claude Desktop:
> **Windows note:** Use Python 3.13 for `uvx` on Windows. Python 3.14 currently fails to resolve a transitive `pywin32` dependency used by the MCP stack.
1. **Locate your config file** - Windows: `%APPDATA%\Claude\claude_desktop_config.json` - macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
2. **Add the configuration**
{
"mcpServers": {
"android-mcp": {
"command": "uvx",
"args": [
"--python",
"3.13",
"android-mcp"
]
}
}
}> **Note:** The server starts first and connects lazily when a tool runs. If no device is specified, it auto-detects connected devices and **prefers physical devices over emulators**. Use `--device <serial>` or the `ANDROID_MCP_DEVICE` environment variable to target a specific device.
Configure a specific WiFi device with environment variables:
{
"mcpServers": {
"android-mcp": {
"command": "uvx",
"args": [
"--python",
"3.13",
"android-mcp"
],
"env": {
"ANDROID_MCP_CONNECTION": "wifi",
"ANDROID_MCP_HOST": "192.168.1.3"
}
}
}
}Or pass explicit flags:
{
"mcpServers": {
"android-mcp": {
"command": "uvx",
"args": [
"--python",
"3.13",
"android-mcp",
"--wifi",
"192.168.1.3"
]
}
}
}Option 2: UV Mode (Local Development)
1. **Clone and Install**
git clone https://github.com/CursorTouch/Android-MCP.git cd Android-MCP uv sync
2. **Configure Claude Desktop**
{
"mcpServers": {
"android-mcp": {
"command": "uv",
"args": [
"--directory",
"</PATH/TO/Android-MCP>",
"run",
"android-mcp"
]
}
}
}> **Note:** Replace `</PATH/TO/Android-MCP>` with the full path to your cloned directory. You can also add `"--device", "<YOUR_DEVICE_serial>"`, `"--wifi", "192.168.1.3"`, or `"--usb"` to control device selection. > `uv sync` follows the repo's `.python-version`, so local development uses Python 3.13 by default.
Option 3: OpenCode
You can also use Android-MCP with [OpenCode](https://opencode.ai). After cloning and installing the repo (see Option 2), add the server as a local MCP in your OpenCode config (`opencode.json`):
{
"mcp": {
"android-mcp": {
"type": "local",
"command": ["uv", "--directory", "</PATH/TO/Android-MCP>", "run", "android-mcp"]
}
}
}> **Note:** Replace `</PATH/TO/Android-MCP>` with the full path to your cloned directory. As with UV mode, you can append `"--device"`, `"--wifi"`, `"--usb"`, etc. to the `command` array to control device selection.
🔌 Device Selection
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 103 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- # android-mcp-beta
- Clean-room reimplementation of [Android-MCP](https://github.com/CursorTouch/Android-MCP): an MCP
- server that lets an AI agent operate an Android device over ADB.
- It needs only `adb`. Nothing is installed on the device, and there is no dependency on
- uiautomator2.
- ## Run
- Requires Python 3.13 and `adb` (Android platform-tools).
- ```
- uv run android-mcp-beta
- ```
- The server speaks MCP on stdio. In a client's config:
- ```json
- {
- "mcpServers": {
- "android-mcp-beta": {
- "command": "uv",
- "args": ["--directory", "D:/Projects/android-mcp-beta", "run", "android-mcp-beta"]
- }
- }
- }
- ```
- The device is connected on the first tool call, so the server starts whether or not one is
- attached yet.
- ## Choosing the device
- With no options it uses the first physical device, or an emulator when there is none.
- | Option | Environment | Meaning |
- |---|---|---|
- | `--device SERIAL` | `ANDROID_MCP_DEVICE` | A serial, or `host:port` for a device on the network |
- | `--connection auto\|usb\|wifi` (alias `--transport`) | `ANDROID_MCP_CONNECTION` | How to pick when no device is named |
- | `--wifi [HOST]` | `ANDROID_MCP_HOST` | ADB over Wi-Fi; `HOST` or `HOST:PORT`, port 5555 by default |
- | `--usb [SERIAL]` | | ADB over USB, optionally a specific serial |
- Options win over the environment. Other variables:
- - `ANDROID_MCP_ADB_PATH` names the `adb` binary. Otherwise `adb` is looked for on `PATH`, then in
- `ANDROID_HOME`, `ANDROID_SDK_ROOT` and the default Android Studio SDK folders.
- - `SCREENSHOT_QUANTIZED=true` reduces screenshots to 256 colours, which makes them smaller.
- ## Tools
- | Tool | Does |
- |---|---|
- | `ListDevices`, `ConnectDevice`, `Device` | List, choose, or disconnect the device |
- | `Snapshot` | The interactive elements, each with a label and tap coordinates. `use_vision` adds a screenshot with the labels drawn on it; `use_annotation=false` leaves it clean |
- | `Click`, `LongClick`, `Swipe`, `Drag` | Touch input by coordinates |
- | `ClickBySelector` | Tap an element found by `text`, `resourceId`, `className` or `description` (exact match; `resourceId` may be the part after the slash), with `index` for the nth match |
- | `Type` | Type into a field. `x` and `y` tap it first; `clear` empties it first. Other scripts and emoji need the optional ADBKeyboard app (below) |
- | `Press` | A button: back, home, recent, volume up, enter, and so on |
- | `Notification` | Pull down the notification shade |
- | `Wait`, `WaitForElement` | Pause, or wait for an element to appear |
- ## Typing other scripts (optional)
- `Type` uses `adb shell input text`, so on its own it types printable ASCII and the accented Latin
- letters Android can compose (é ñ ü ÿ and 107 others, not ç ß å ø). A newline presses Enter and a
- tab presses Tab. For anything else (CJK, Cyrillic, Arabic, emoji, ç), install the
- [ADBKeyboard](https://github.com/senzhk/ADBKeyBoard) app on the device once:
- ```
- adb install keyboardservice-debug.apk
- ```
- Download it from the [releases page](https://github.com/senzhk/ADBKeyBoard/releases). This project
- does not bundle it: ADBKeyboard is GPL-2.0, and it is only ever talked to over broadcasts. I tested
- v2.5-dev (SHA-256 `41a8a099…46fbbb`) on Android 15.
- With it installed, text that `input text` cannot type is sent through it automatically. For about
- a second the device's keyboard is switched to ADBKeyboard, which shows no keyboard of its own, and
- then the keyboard that was active before is put back (and ADBKeyboard is disabled again if it was
- not enabled). A text field must be focused, or the call fails with an error saying so. If a crash
- ever leaves the device on ADBKeyboard, `adb shell ime reset` restores the default. Without the app,
- such text is rejected before anything is sent, with these instructions in the error.
- ## Other limits
- - **Busy screens.** The element list comes from `uiautomator dump`, which gives up when the screen
- never goes idle (a video, a running timer). `Snapshot` with `use_vision` then returns the
- screenshot alone and says so; click by coordinates still works.
- - **Drag** needs Android 8 or later. **Clearing a field** uses `input keycombination`, which needs
- Android 12; older devices fall back to a slower method that clears up to 200 characters.
- ## Development
- ```
- uv sync
- uv run pytest
- uv run ruff check . && uv run ruff format --check .
- ```
- The tests need no device. Layers, bottom to top: `android_mcp.adb` (talks to `adb`),
- `android_mcp.tree` (reads the screen), `android_mcp.mobile` (one connected device: state and
- actions), `android_mcp.server` (the MCP tools and the choice of device).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.