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.

Note: Purpose-built tools return structured, minimal responses instead of raw XML dumps, keeping agent workflows fast and context consumption low, while keeping performance high.

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

• Exposes 14 core MCP tools covering screen capture, UI inspection, screen reading, element extraction, touch and swipe input, text entry, keycode events, app launching, arbitrary ADB commands, and device capability inspection

• Extra tool packs extend the core toolset via opt-in config — app_manager is the first pack, adding 9 tools for package management, app control, APK extraction, permission management, and intent injection

• Auto-detects the connected device when only one is present; presents a device list and requires the user to choose when multiple are connected

• All commands parsed via shlex — no shell injection possible

• Runs over stdio, compatible with any MCP-capable AI client

• Purpose-built screen reading and element extraction tools return structured, minimal responses — a fraction of the size of a raw XML hierarchy — keeping agent context lean across long automation runs

• Two execution modes: unrestricted (default, with optional shell denylist) and restricted (allowlist-only — only explicitly permitted shell commands are allowed); set ADB_EXECUTION_MODE=restricted to enable

• Set ADB_ALLOW_SHELL=false to block all adb shell commands entirely, regardless of mode

• Add tool names to tools.denied in adb_config.yaml to hide specific MCP tools from the agent at server startup — all filtering enforced at the server level

• Server instructions are automatically generated at startup and reflect the active tool set — agents receive a structured tool catalog at connect time, including any loaded extra tool packs

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

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

Full setup guide: docs/setup.md

Tools

Extra tool packs

Optional packs extend the core toolset and must be enabled in adb_config.yaml. 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

The server is configurable via adb_config.yaml and environment variables. Tuneable parameters include the ADB binary path, command timeouts, log level, execution mode, shell filtering rules, and tool visibility. Full reference: docs/configuration.md.

Session recording is configured separately via logging_config.yaml. Enable it by setting MCP_LOG_ENABLED=true and MCP_LOG_DIR in your MCP client config. 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.