List all connected Android devices with their status and model information

Get detailed information about a connected Android device including model, Android version, SDK version, screen size, brand, and manufacturer

Get the screen resolution (width x height in pixels) of the connected Android device

Check the health status of the MCP server and ADB connectivity. Returns server uptime, ADB availability, connected device count, and configuration summary.

Tap at specific coordinates on the Android screen. Coordinates can be absolute pixels or normalized (0-1 range, will be scaled to screen size).

Swipe from one point to another on the Android screen. Useful for scrolling, swiping between pages, or drag gestures.

Long press at specific coordinates on the Android screen. Useful for context menus, drag initiation, or selection.

Double tap at specific coordinates on the Android screen. Useful for zooming or selecting text.

Type text into the currently focused input field on the Android device. The field must already be focused (tapped).

Press a hardware/software key on the Android device. Common keycodes: HOME, BACK, MENU, ENTER, VOLUME_UP, VOLUME_DOWN, POWER, DEL, TAB, SPACE, APP_SWITCH, SEARCH, CAMERA.

List installed applications on the Android device. By default shows third-party apps only.

Launch an Android application by its package name (e.g. com.google.android.youtube). The app must be installed.

Force-stop an Android application by its package name.

Install an APK file onto the Android device from a local file path.

Uninstall an application from the Android device. Requires allowDestructiveOps to be enabled in server configuration.

Get the package name of the currently focused/foreground Android application.

List files and directories at a given path on the Android device. Returns file names, types, sizes, and permissions.

Download a file from the Android device to the local machine.

Upload a file from the local machine to the Android device.

Capture the current UI hierarchy from the Android screen. Returns a structured representation of all visible UI elements with their properties, text, bounds, and states. This is the primary way to understand what is currently on screen.

Find a UI element on the Android screen matching the given selector criteria. Returns the first matching element with its properties and bounds. Use this to locate buttons, text fields, or any UI component before interacting with it.

Find a UI element matching the selector and tap its center. This is the preferred way to interact with UI elements rather than using raw coordinates.

Wait for a UI element to appear on screen within a timeout period. Useful after navigation, loading screens, or animations. Polls the UI tree at regular intervals until the element is found.

Check whether a UI element exists on the current screen. Returns true/false without throwing an error. Useful for test assertions and conditional logic.

Capture a screenshot of the current Android device screen. Returns a base64-encoded PNG image that can be displayed or analyzed visually. Use this to see what is currently on screen.

Capture a screenshot and analyze the screen content. Returns both the visual screenshot and a text summary of the UI tree for comprehensive screen understanding. Use this when you need to understand the full screen context.

Detect interactive elements on the screen using a combination of screenshots and UI tree analysis. Returns a list of all clickable/focusable elements with their coordinates and descriptions. Use this when you need to find elements to interact with.

Compare the current screen with the previously captured screenshot to detect changes. Returns the percentage of pixels that changed and whether the screen has significantly changed. Useful for verifying that an action had an effect.

Intelligently click an element using multiple strategies: UIAutomator → Accessibility → Vision → Coordinates fallback. This is the most reliable way to click elements.

Execute an ordered test scenario with multiple steps and assertions. Each step performs an action and optionally verifies the result. Returns detailed pass/fail results per step.

Start recording actions to create a macro. All subsequent tool calls will be recorded. Use stop_recording to save.

Stop the active recording and save it to disk.

Replay a previously recorded action sequence.

List all saved action recordings/macros.

Get the current tracked state of a device including current app, screen history, and recent actions. Useful for understanding context.

Get performance metrics and action history for the MCP server. Shows per-tool latency, success/failure counts.

List all loaded MCP server plugins and their versions.