Android

io.github.martingeidoblerPublished by GitHub account martingeidoblerv1.2.1Updated Oct 27, 2026

Control Android devices and emulators via ADB — screenshots, UI automation, and logcat.

VerifiedSTDIODesktop onlyBrowser AutomationDeveloper Tools

Overview

AI-generated overview

Controls Android emulators and devices over ADB, letting an assistant take screenshots, inspect and tap UI elements, and read logcat.

What you can do
  • List devices and AVDs, start emulators, and read device info
  • Capture screenshots and inspect the UI element hierarchy
  • Tap, long-press, double-tap, swipe, scroll, type text, press keys, and target elements by resource-id, text, or content-desc
  • Read and clear logcat output filtered by package, level, and time
  • Install APKs, launch apps, check the foreground activity, pull files, and run arbitrary ADB shell commands
When to use it
Useful for driving Android apps during UI testing, smoke tests, and bug documentation, where the assistant should see screens, interact with them, and correlate behavior with logs. Works with any app without SDK integration.
Requirements
Runs locally via npx with Node.js 18+, an Android SDK with platform-tools (ADB) and emulator, and a running emulator or connected device. The SDK path is auto-detected on macOS or set through the ANDROID_HOME environment variable.
Before you install
The assistant can act on real devices: it installs APKs, launches apps, sends taps and text, clears the logcat buffer, pulls files to the local filesystem, and runs arbitrary ADB shell commands. Point it at a test device or emulator rather than a personal phone.

Installation

In SourceWeft

  1. Open Android in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Android MCP Server

[npm version] [npm downloads] [License: MIT] [android-mcp-server MCP server] [Awesome MCP Servers] [SocketBadge]

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

[ezgif-3bbb68e918812643] ^ Sped up for better viewing. More demos and test cases.

Features

  • 25 tools for complete Android device control
  • Screenshot capture with intelligent compression (Sharp-based, max 1280px)
  • UI tree inspection — read element hierarchy with bounds, text, resource IDs, and state
  • Touch automation — tap, swipe, scroll, type text, press hardware keys
  • Element targeting — find and tap elements by resource-id, text, or content-desc
  • App lifecycle — install APKs, launch apps, inspect current activity
  • Logcat integration — filter by package, log level, or timestamp
  • Device management — list devices, start emulators, get device info
  • Compound actions — tap_and_wait combines tap + settle + UI tree in one round trip
  • Persistent ADB shell — reuses a single shell session for faster command execution
  • Device info caching — queries device properties once per session
  • Multi-device support — target specific devices by ID
  • Zero app modifications — works with any Android app via ADB, no SDK integration needed

Prerequisites

  • Node.js 18+
  • Android SDK with platform-tools (ADB) and emulator
  • A running Android emulator or connected device

Finding your ANDROID_HOME

The 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:

bash
# macOSls ~/Library/Android/sdk/platform-tools/adb
# Or find it via Android Studio: Settings > Languages & Frameworks > Android SDK

Setup

Claude Code
bash
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:

bash
claude mcp add --scope user --env ANDROID_HOME=/path/to/sdk android -- npx -y android-mcp-server
Claude Desktop

Add to your Claude Desktop config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
json
{  "mcpServers": {    "android": {      "command": "npx",      "args": ["-y", "android-mcp-server"],      "env": {        "ANDROID_HOME": "/path/to/android/sdk"      }    }  }}
VS Code

Add to your VS Code settings (.vscode/settings.json):

json
{  "mcp": {    "servers": {      "android": {        "command": "npx",        "args": ["-y", "android-mcp-server"],        "env": {          "ANDROID_HOME": "/path/to/android/sdk"        }      }    }  }}
Cursor

Add to your Cursor MCP config (~/.cursor/mcp.json):

json
{  "mcpServers": {    "android": {      "command": "npx",      "args": ["-y", "android-mcp-server"],      "env": {        "ANDROID_HOME": "/path/to/android/sdk"      }    }  }}
Windsurf

Add to your Windsurf MCP config (~/.codeium/windsurf/mcp_config.json):

json
{  "mcpServers": {    "android": {      "command": "npx",      "args": ["-y", "android-mcp-server"],      "env": {        "ANDROID_HOME": "/path/to/android/sdk"      }    }  }}
Project config (.mcp.json)

Add to your project's .mcp.json (checked into version control so your team gets it too):

json
{  "mcpServers": {    "android": {      "command": "npx",      "args": ["-y", "android-mcp-server"],      "env": {        "ANDROID_HOME": "/path/to/android/sdk"      }    }  }}
Build from source
bash
git clone https://github.com/martingeidobler/android-mcp-server.gitcd android-mcp-servernpm installnpm run buildclaude mcp add --scope user android -- node /path/to/android-mcp-server/dist/index.js

Available Tools

Device Management

ToolDescription
list_devicesList connected Android devices and emulators
list_avdsList available Android Virtual Devices
start_emulatorStart an AVD by name (waits up to 60s)

Screenshot & UI Analysis

ToolDescription
screenshotTake screenshot for visual analysis. Optional save_path to save to disk
get_ui_treeGet UI element hierarchy with bounds, text, resource IDs, and state

Interaction

ToolDescription
tapTap at screen coordinates
tap_elementTap element by resource-id, text, or content-desc
tap_and_waitTap element, wait for UI to settle, return new UI tree — single round trip
long_pressLong press at coordinates (context menus, drag handles)
double_tapDouble tap at coordinates
multi_tapTap the same coordinates N times with a fixed interval (spam tapping)
tap_sequenceMulti-step action chain: taps, waits, text input, key presses, swipes in any order
type_textType text into focused input
press_keyPress key (back, home, enter, tab, delete, menu, etc.)
swipeSwipe gesture between coordinates
scroll_to_elementScroll until element is visible
wait_for_elementWait for element to appear (with timeout)

Diagnostics

ToolDescription
get_logsGet logcat output, filterable by package, log level, and time
clear_logsClear logcat buffer (call before reproducing a bug for clean output)
get_device_infoGet model, Android version, API level, screen size, DPI

App Management

ToolDescription
launch_appLaunch app by package name
install_apkInstall APK file
get_current_activityGet foreground app and activity
pull_filePull a file from the device to local filesystem
adb_shellRun arbitrary ADB shell command

Example Workflows

Bug documentation

"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")

UI testing

"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.

Smoke testing

"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.

Element interaction

"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")

Demos & Prompting Guide

  • DEMOS.md — copy-paste prompt scenarios you can try right now
  • PROMPTING.md — best practices, performance tips, and common pitfalls

How It Works

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.

Contributing

Contributions are welcome! Please see CONTRIBUTING.md for guidelines.

License

MIT - see LICENSE.

Source: README.md at commit 15a4b90

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.2.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts