Server data from the Official MCP Registry
Control Android devices and emulators via ADB — screenshots, UI automation, and logcat.
Control Android devices and emulators via ADB — screenshots, UI automation, and logcat.
Valid MCP server (2 strong, 4 medium validity signals). 1 code issue detected. 3 known CVEs in dependencies (0 critical, 3 high severity) Package registry verified. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.
5 files analyzed · 5 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: ANDROID_HOME
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-martingeidobler-android": {
"env": {
"ANDROID_HOME": "your-android-home-here"
},
"args": [
"-y",
"android-mcp-server"
],
"command": "npx"
}
}
}From the project's GitHub README.
MCP server for controlling Android emulators and devices via ADB. Gives AI assistants the ability to see, interact with, and debug Android apps — taking screenshots, tapping elements, reading logs, and documenting bugs.
npm Package | GitHub | Issues
^ Sped up for better viewing. More demos and test cases.
tap_and_wait combines tap + settle + UI tree in one round tripThe server auto-discovers the SDK at ~/Library/Android/sdk (macOS) or via ANDROID_HOME. If your SDK is elsewhere, set ANDROID_HOME in the MCP config (see below).
To check:
# macOS
ls ~/Library/Android/sdk/platform-tools/adb
# Or find it via Android Studio: Settings > Languages & Frameworks > Android SDK
claude mcp add --scope user android -- npx -y android-mcp-server
This registers the server globally so it's available in all projects. Use --scope project instead to limit it to the current project.
If your SDK is not in the default location:
claude mcp add --scope user --env ANDROID_HOME=/path/to/sdk android -- npx -y android-mcp-server
Add to your Claude Desktop config file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json{
"mcpServers": {
"android": {
"command": "npx",
"args": ["-y", "android-mcp-server"],
"env": {
"ANDROID_HOME": "/path/to/android/sdk"
}
}
}
}
Add to your VS Code settings (.vscode/settings.json):
{
"mcp": {
"servers": {
"android": {
"command": "npx",
"args": ["-y", "android-mcp-server"],
"env": {
"ANDROID_HOME": "/path/to/android/sdk"
}
}
}
}
}
Add to your Cursor MCP config (~/.cursor/mcp.json):
{
"mcpServers": {
"android": {
"command": "npx",
"args": ["-y", "android-mcp-server"],
"env": {
"ANDROID_HOME": "/path/to/android/sdk"
}
}
}
}
Add to your Windsurf MCP config (~/.codeium/windsurf/mcp_config.json):
{
"mcpServers": {
"android": {
"command": "npx",
"args": ["-y", "android-mcp-server"],
"env": {
"ANDROID_HOME": "/path/to/android/sdk"
}
}
}
}
Add to your project's .mcp.json (checked into version control so your team gets it too):
{
"mcpServers": {
"android": {
"command": "npx",
"args": ["-y", "android-mcp-server"],
"env": {
"ANDROID_HOME": "/path/to/android/sdk"
}
}
}
}
git clone https://github.com/martingeidobler/android-mcp-server.git
cd android-mcp-server
npm install
npm run build
claude mcp add --scope user android -- node /path/to/android-mcp-server/dist/index.js
| Tool | Description |
|---|---|
list_devices | List connected Android devices and emulators |
list_avds | List available Android Virtual Devices |
start_emulator | Start an AVD by name (waits up to 60s) |
| Tool | Description |
|---|---|
screenshot | Take screenshot for visual analysis. Optional save_path to save to disk |
get_ui_tree | Get UI element hierarchy with bounds, text, resource IDs, and state |
| Tool | Description |
|---|---|
tap | Tap at screen coordinates |
tap_element | Tap element by resource-id, text, or content-desc |
tap_and_wait | Tap element, wait for UI to settle, return new UI tree — single round trip |
long_press | Long press at coordinates (context menus, drag handles) |
double_tap | Double tap at coordinates |
multi_tap | Tap the same coordinates N times with a fixed interval (spam tapping) |
tap_sequence | Multi-step action chain: taps, waits, text input, key presses, swipes in any order |
type_text | Type text into focused input |
press_key | Press key (back, home, enter, tab, delete, menu, etc.) |
swipe | Swipe gesture between coordinates |
scroll_to_element | Scroll until element is visible |
wait_for_element | Wait for element to appear (with timeout) |
| Tool | Description |
|---|---|
get_logs | Get logcat output, filterable by package, log level, and time |
clear_logs | Clear logcat buffer (call before reproducing a bug for clean output) |
get_device_info | Get model, Android version, API level, screen size, DPI |
| Tool | Description |
|---|---|
launch_app | Launch app by package name |
install_apk | Install APK file |
get_current_activity | Get foreground app and activity |
pull_file | Pull a file from the device to local filesystem |
adb_shell | Run arbitrary ADB shell command |
"Clear the logs, open the settings screen, tap the save button, then show me the logs and a screenshot"
Claude will: clear_logs → launch_app → tap_element → get_logs(package_name="com.example.app", level="E") → screenshot(save_path="./bugs/settings-crash.png")
"Navigate through the login flow and verify each screen matches the designs"
Claude will use screenshot + get_ui_tree to see and understand each screen, tap_element/type_text to interact, and its vision capabilities to compare against mockups or descriptions.
"Install the APK, launch the app, and tap through the main screens to check nothing crashes"
Claude will: install_apk → launch_app → navigate with tap_element → get_logs(level="E") to check for errors after each screen.
"Open Settings, search for 'display', tap the first result, then go back"
Claude will: launch_app(package_name="com.android.settings") → tap_and_wait(by="text", value="Search settings") → type_text("display") → tap_and_wait(by="text", value="Display") → press_key(key="back")
The server communicates over stdio using the Model Context Protocol. All device interaction goes through ADB — no modifications to your app are required. Screenshots are captured in memory, compressed, and returned as base64 images that the AI can see and analyze visually.
Contributions are welcome! Please see CONTRIBUTING.md for guidelines.
MIT - see LICENSE.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.