Your Android device, live inside VS Code.

Get started

DroidBridge works with USB devices, emulators and phones on your Wi-Fi. You only need ADB, and DroidBridge finds or downloads it for you.

1. Install the extension from the VS Code Marketplace or Open VSX, or run:

   code --install-extension lusansapkota.droidbridge

2. Turn on developer options on the device: Settings > About phone, then tap Build number seven times.
3. Connect the device. Plug it in over USB and accept the debugging prompt, or start an emulator. The sidebar shows Device ready as soon as ADB sees it.
4. For Wi-Fi, open Developer options > Wireless debugging. Pair once with the code shown there using Wireless Pairing in the sidebar, then enter the IP and port under Connect.
5. Open the DroidBridge view in the activity bar and click Start Mirror.

Screen mirror

The device screen streams into the sidebar and stays interactive. It keeps the device's shape at any sidebar width and follows rotation, so phones and landscape tablets both fit.

More room

Use Open in editor tab to move the mirror into a resizable editor tab. Drag that tab out to give the device its own window, and use Move back to sidebar to dock it again.

Prefer the classic scrcpy window? Use Open in native scrcpy window. It needs scrcpy installed; the embedded mirror does not.

AI agents (MCP)

DroidBridge includes an MCP server, so AI agents can look at the screen, read its elements, tap, type, read logs and install builds. Keep the mirror open and watch every step.

Try prompts like these:

• Install the debug APK from app/build/outputs, log in with the test account and tell me if the dashboard loads.
• Open the settings screen and check logcat for the crash. Explain the cause.
• Rotate the tablet and check whether the checkout layout still fits.

claude mcp add droidbridge -e DROIDBRIDGE_ADB="/path/to/adb" -- node "/path/to/globalStorage/lusansapkota.droidbridge/mcp-server.js"

{
  "mcpServers": {
    "droidbridge": {
      "command": "node",
      "args": ["/path/to/globalStorage/lusansapkota.droidbridge/mcp-server.js"],
      "env": { "DROIDBRIDGE_ADB": "/path/to/adb" }
    }
  }
}

External clients need Node.js. The copied path stays the same when DroidBridge updates.

Agent tools

Coordinates are device pixels. With more than one device connected, every tool takes a serial from list_devices.

Agents act on your device the way you would. Review what you allow, especially shell and install_apk. Most MCP clients ask before each tool call.

Settings

Open Settings and search for DroidBridge, or add these to settings.json.

Commands

All commands are in the command palette under DroidBridge.

Troubleshooting

Requirements