Agent Droid Bridge
Let Claude Code or Cursor drive real Android devices through ADB for UI checks, installs, and scripted device actions while you ship a mobile app.
Overview
Agent Droid Bridge is an MCP server for the Build phase that connects AI agents to Android devices via ADB for inspection and controlled automation.
What is this MCP server?
- Stdio MCP server (uvx/PyPI agent-droid-bridge v0.6.1) over ADB for screenshots, input, and device state
- ADB_EXECUTION_MODE: unrestricted vs restricted with optional ADB_SHELL_ALLOWLIST deny/allow policies
- ADB_ALLOW_SHELL boolean gate to block all adb shell regardless of mode
- Configurable ADB_PATH and ADB_EXTRA_TOOL_PACKS for custom platform-tools layouts
- Gives agents eyes and hands on emulators or USB devices without a separate mobile-only IDE plugin
- Server version 0.6.1 on PyPI identifier agent-droid-bridge
- Stdio transport with runtimeHint uvx
- ADB_EXECUTION_MODE supports 2 choices: unrestricted and restricted
Community signal: 15 GitHub stars.
What problem does it solve?
You want your coding agent to verify Android UI and run device commands without writing one-off adb scripts and pasting screenshots back into chat.
Who is it for?
Solo builders testing Android apps with Claude Code or Cursor who already use adb and want MCP-native device control with optional command lockdown.
Skip if: Teams that need iOS/WebDriver-only stacks, zero shell exposure, or managed device farms without local ADB setup.
What do I get? / Deliverables
After you register the server, your agent can drive emulators or phones through MCP tools with configurable shell restrictions instead of manual ADB juggling.
- MCP tools that read and act on connected Android devices
- Policy-controlled adb shell access (unrestricted, restricted, or shell disabled)
- Repeatable agent workflows for on-device verification during builds
Recommended MCP Servers
Journey fit
Android device control sits in Build because you wire agent tooling into the product and test flows on hardware or emulators before release. Agent-tooling is the canonical shelf for MCP servers that extend what coding agents can touch outside the repo—here, the device shell and UI.
How it compares
ADB device bridge MCP, not a Play Store deployment or CI emulator farm product.
Common Questions / FAQ
Who is Agent Droid Bridge for?
Indie and solo Android developers who use MCP-enabled agents and want direct emulator or USB device access from the same session as their code.
When should I use Agent Droid Bridge?
Use it during Build when you need agent-driven UI checks, installs, or adb workflows on Android without leaving Claude Code or Cursor.
How do I add Agent Droid Bridge to my agent?
Add the io.github.Neverlow512/agent-droid-bridge MCP entry with stdio transport (runtimeHint uvx, PyPI agent-droid-bridge), set ADB_PATH if needed, choose restricted or unrestricted ADB_EXECUTION_MODE, then restart the client.