Android Debug Bridge

MCP plugin to control Android devices via ADB (Android Debug Bridge) for automation, testing, and agent integration.

typescript

18

GitHub Stars

typescript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "tiagodanin-android-debug-bridge-mcp": {
      "command": "npx",
      "args": [
        "android-debug-bridge-mcp"
      ]
    }
  }
}

Android Debug Bridge MCP lets you automate and control Android devices through an MCP client. With this server, you can manage tests, interact with apps, capture UI data, and simulate user input to streamline automation, testing, and agent integration.

How to use

You interact with Android devices by configuring an MCP client to communicate with this server. After installation, you can ask your client to perform actions such as creating test folders, listing apps, opening apps by package name, taking screenshots, capturing UI hierarchies, and simulating input (key events, taps, text entry, and scrolling). Use natural language prompts to drive the server through your MCP client.

Practical usage patterns include: creating a test folder called login_test, listing apps with a name match like chrome, launching an app by its package name (for example com.android.chrome), saving a screenshot under a step label like 001_homepage, capturing the current UI hierarchy for inspection, and performing input actions to automate navigation or data entry.

How to install

npm install -g android-debug-bridge-mcp

Additional setup and usage notes

Prerequisites you need on the host machine include having the Android Debug Bridge (ADB) installed and accessible in your PATH, and a connected Android device (or emulator) with USB debugging enabled and authorized.

Configure your MCP client to use the server entry that runs locally. For example, use the following command to start the MCP server via npx (no local build step is shown in this setup): the client will connect to the local MCP endpoint automatically.

Security and accessibility

Ensure your device remains connected and authorized for debugging during automation. Limit access to the MCP endpoint to trusted clients and consider enabling network-level access controls if you expose the server beyond your local machine.

Examples and tips

To quickly try a workflow, first create a test folder, then list apps with a familiar pattern, and finally capture a screenshot to verify the flow.

Troubleshooting

If commands fail, verify ADB is installed and accessible, the Android device is connected and authorized, and your MCP client is configured to reach the MCP server as described in the setup steps.

Notes

This server supports test organization, app control, screen capture, UI analysis, and input simulation to cover common automation scenarios on Android devices.

Available tools

Create test folders

Organize automation tests by creating named folders to group related test assets and scripts.

List installed apps

Query the device for apps installed on the system and filter by name patterns.

Open app by package

Launch an application directly using its package name.

Take screenshot

Capture the current device screen and save it under a structured test folder with a step label.

Capture UI hierarchy

Dump the UI hierarchy for inspection of elements and layout.

Input simulation

Send key events, tap at coordinates, input text into fields, and perform directional scrolling on the device.