Agent Droid Bridge

Agent Droid Bridge is an MCP server that connects AI agents to Android devices and emulators over ADB. It is built for mobile automation, app testing, dynamic analysis, and reverse engineering: exposing the full surface of ADB as structured tools that any MCP-compatible AI client can call directly. If ADB can do it, an agent can do it.

> Purpose-built tools return structured, minimal responses. No raw XML dumps, no wasted context — agents stay fast across long sessions.

Demo

The demo above runs through a few straightforward tasks to show what a connected agent can do, and this is just scratching the surface:

• Installs the Paint app, opens it, and draws a house by calculating pixel coordinates for the walls and roof
• Opens the device browser, searches for "MCP Wikipedia", navigates to the result page, and takes a screenshot
• Opens the Calculator, computes 1337 × 42, and extracts the result to the host machine
• Opens Contacts, creates a new entry with a name and phone number, and confirms it saved
• Opens the Calendar and schedules an appointment for a specific date
• Opens Settings and toggles dark mode
• Extracts the Calculator APK from the device to the host machine
• Installs Notepad, writes a one-sentence summary of every task completed, and takes a final screenshot

What it does

Tools

• 14 built-in tools for screen capture, UI inspection, text reading, element extraction, touch and swipe input, text entry, keycode events, app launching, ADB commands, and device inspection
• `app_manager` pack adds 9 tools for package management, app lifecycle, APK extraction, permissions, and intent injection. Load it with `ADB_EXTRA_TOOL_PACKS=app_manager`
• Tool availability is reflected in the server's startup instructions. Agents receive an accurate catalog at connect time

Device handling

• Auto-detects a single connected device; prompts for selection when multiple devices are present
• Runs over stdio, compatible with any MCP-capable AI client
• Structured responses instead of raw XML dumps, keeping agent context lean across long automation runs

Security

• Two execution modes: `unrestricted` (full ADB access, optional denylist) and `restricted` (allowlist-only, blocks everything not explicitly permitted)
• Set `ADB_ALLOW_SHELL=false` to disable all shell commands regardless of mode
• Hide specific tools from the agent with `ADB_DENIED_TOOLS`
• All commands parsed via `shlex`. No shell injection possible

Observability

• Optional session recorder logs every tool call, ADB command, and security event to structured JSONL files. Enable with `MCP_LOG_ENABLED=true` and `MCP_LOG_DIR`

Use cases

Mobile QA and test automation

Automate UI flows across real devices and emulators without modifying the app or writing test code. Tap, swipe, type, read screen content, take screenshots — all from a natural language prompt.

App security research

Extract APKs, inspect declared permissions, fire arbitrary intents, and observe runtime behavior on screen. No instrumentation, no jailbreak required.

Dynamic analysis

Launch apps in controlled states, drive UI interactions, capture screen state at each step, and pull artifacts — all scriptable through an AI agent.

Development and debugging

Install builds, verify UI states, check app info, and run ADB commands without leaving your coding environment.

Install

uvx agent-droid-bridge

No cloning or virtual environments needed. Requires Python 3.11+ and ADB installed on your host.

`uvx` is provided by uv. If you don't have it: `curl -LsSf https://astral.sh/uv/install.sh | sh`

To install from source instead, see docs/setup.md — Option B.

To verify the install: `uvx agent-droid-bridge --help`

Quick start

1. Install ADB — see docs/setup.md for platform-specific instructions

2. Connect an Android device or start an emulator

3. Add the server to your MCP client config:

{
  "mcpServers": {
    "agent-droid-bridge": {
      "command": "uvx",
      "args": ["agent-droid-bridge"],
      "env": {
        "ADB_EXECUTION_MODE": "unrestricted",
        "ADB_ALLOW_SHELL": "true",
        "ADB_PATH": "adb",
        "ADB_EXTRA_TOOL_PACKS": "",
        "MCP_LOG_ENABLED": "false",
        "MCP_LOG_DIR": "~/logs/agent-droid-bridge"
      }
    }
  }
}

To enable session logging, set `MCP_LOG_ENABLED` to `"true"` and update `MCP_LOG_DIR` to a writable path on your machine.

4. Prompt your agent to use the `agent-droid-bridge` MCP tools

Full setup guide and environment variable reference: docs/setup.md

Tools

Extra tool packs

Optional packs extend the core toolset. Enable them by setting `ADB_EXTRA_TOOL_PACKS` in your MCP client config. See docs/extra-tool-packs.md.

app_manager

Package management, app lifecycle control, APK extraction, permission management, and intent injection.

Full parameter reference: docs/tools.md

Configuration

Configure the server entirely from your MCP client's `env` block. No files to edit. The env block in the Quick Start above covers the most common settings. For the full reference including security filtering, tool visibility, and timeouts, see docs/configuration.md.

To use a YAML config file instead, set `ADB_CONFIG_SOURCE=yaml`. See docs/configuration.md for details.

Session recording is separate. Enable it with `MCP_LOG_ENABLED=true` and `MCP_LOG_DIR`. Full reference: docs/logging.md.

Documentation

Contributing

Contributions are welcome. See CONTRIBUTING.md for guidelines on setup, code standards, and submitting pull requests.

To report a security vulnerability, follow the process in SECURITY.md — do not open a public issue.