Skip to main content
Glama

Agent Bridge

Give your AI agent a real Android phone.

Claude Code, Cursor, Antigravity or any MCP agent can see your phone's screen, tap, type, open apps, change settings and move files. One npx command on the computer, one QR scan on the phone.

npm npm downloads APK downloads Android 5.0+ MCP License: MIT

Website · Get started · Docs · Install the app

▶ Watch the film (1:30)

     

 ┌──────────────┐   MCP / CLI   ┌─────────────────────┐   Wi-Fi or USB   ┌──────────────────┐
 │ Claude Code, │ ────────────▶ │ android-agent-bridge │ ◀──────────────▶ │ Agent Bridge app │
 │ Cursor, …    │               │   (your computer)    │                  │   (your phone)   │
 └──────────────┘               └─────────────────────┘                  └──────────────────┘

Quick start

You need an Android phone (5.0+), Node.js 20+ and, the first time only, a USB cable.

1. Install the app and pair, over USB. Turn on USB debugging (Settings → About phone → tap Build number 7 times → Developer options), plug in, then:

npx android-agent-bridge usb

It installs the app, switches on its accessibility service, pairs and starts the bridge. If you don't have Android's adb tool, it downloads it from Google the first time.

No cable? On Android 11+, turn on Wireless debugging in Developer options and run npx android-agent-bridge wifi, then scan the QR code from Pair device with QR code.

2. Connect your agent. For Claude Code:

claude mcp add phone -- npx -y android-agent-bridge

3. Ask it something.

"Open YouTube on my phone and search for lofi music."

That's it. From now on the phone also works over Wi-Fi: run npx android-agent-bridge start and it reconnects by itself.

Download the APK and install it on the phone, then:

npx android-agent-bridge start

In the app: Scan QR code → point it at the code in your terminal (or the bigger one at localhost:8350/pair) → turn on the accessibility service. Phone and computer must be on the same Wi-Fi.

If Play Protect says "App blocked to protect your device", install from your computer instead with usb or wifi. Play Protect blocks sideloaded accessibility apps opened from a browser or chat app; installs through adb aren't affected.

Run npx android-agent-bridge init in your project (it writes .mcp.json, plus .cursor/mcp.json with --cursor), or add this to your client's MCP config:

{
  "mcpServers": {
    "phone": { "command": "npx", "args": ["-y", "android-agent-bridge"] }
  }
}

Related MCP server: phone-mcp-server

What it can do

👁 Sees the screen

A numbered list of every button and field, and screenshots with each element boxed. Knows what's hidden under sheets and dialogs.

🔤 Reads what apps hide

On-device OCR reads the pixels when an app hides its controls from accessibility, so "tap Account" still works. Nothing leaves the phone.

👆 Acts like a person

Tap by number, text or position. Type into fields, scroll, swipe, long-press, Back and Home. Open any app by name.

🎛 Runs the device

Volume, brightness, flashlight, rotation, Do Not Disturb, settings pages, links, dialer, battery, notifications, clipboard.

📁 AirDrop, both ways

phonectl send photo.jpg, drag files onto localhost:8350/drop, or Share → Agent Bridge on the phone. Any size, no cloud.

📱 Old phones welcome

Android 5.0 (2015) and up. Where old Android can't do something, the computer does it over USB.

Try these prompts

Once the phone is connected, paste any of these into your agent:

  • "Is my phone connected? Take a screenshot and tell me what's on screen."

  • "Read my phone's notifications and summarise them by app. Don't reply to anything."

  • "Turn media volume to 30%, brightness to 60 and switch on Do Not Disturb."

  • "Open my app (com.example.app) and test the sign-up flow like a QA tester. Give me a bug list."

  • "Send ./report.pdf to my phone and tell me where it was saved."

More in the prompt library. Agents are told to ask before sending, posting, paying or deleting, and never to type passwords.

For agents

The MCP server gives your agent 27 tools and 6 ready-made prompts. In Claude Code the prompts are slash commands:

Slash command

What it does

/mcp__phone__phone_tour

Checks the phone is connected and describes the screen

/mcp__phone__do_in_app

Opens an app and carries out a task step by step

/mcp__phone__test_my_app

QA walkthrough of an app, with a bug report

/mcp__phone__catch_up

Summarises notifications, urgent first

/mcp__phone__set_up_phone

Volume, brightness, Do Not Disturb in one go

/mcp__phone__send_to_phone

Sends files and confirms where they landed

MCP tool

CLI

What it does

phone_status

status

Connected phone, Android version, capabilities

phone_screen

screen [--mode marks|grid|both|plain]

Screenshot with numbered elements or a lettered grid

phone_elements

elements [--all] [--ocr]

Element list only (cheap text)

phone_ocr

ocr

Text read from the screen pixels, with positions

phone_tap

tap <target> [--long]

Tap or long-press

phone_type

type <text> [--into t] [--submit]

Type into a field

phone_scroll

scroll <dir> [--in t]

Scroll the screen or a list

phone_swipe

swipe <from> <to>

Drag between two points

phone_key

key <name>

back, home, recents, notifications, quick_settings, enter, lock

phone_open_app

launch <app> [--store]

Open an app by name, or its Play Store page

phone_apps

apps [filter]

Installed apps

phone_wait_for

wait <text>

Wait for text to appear

phone_volume

volume [stream] [level]

Media, ring, notification, alarm, call volume

phone_brightness

brightness [0-100|auto]

Screen brightness

phone_toggle

flashlight · rotation · dnd · ringer

Quick switches

phone_settings

settings <page>

Wi-Fi, Bluetooth, display, battery… or an app's info page

phone_open_link

url <link>

Web pages and deep links

phone_dial

dial <number>

Dialer with the number filled in (never calls)

phone_web_search

search <query>

Web search on the phone

phone_device_info

battery · current

Battery, app in front

phone_notifications

notifications

Notifications since the service started

phone_clipboard

clipboard [set <text>]

Read or set the clipboard

phone_wake

wake

Turn the screen on (stays PIN-locked)

phone_permissions

permissions [grant]

Optional permissions, switched on over USB

phone_send_files

send <files…>

Computer → phone

phone_received_files

received

Files the phone sent to the computer

phone_stop_app

stop <package>

Force-stop an app (USB)

A target is an element number (12), visible text (Sign in), a grid cell (C7) or pixels (540,1200).

From the terminal

Everything an agent can do, you can do too. npm i -g android-agent-bridge gives you the phonectl command; keep start running in another terminal.

phonectl status                         # is the phone connected?
phonectl launch YouTube                 # open an app
phonectl screen --out shot.jpg          # screenshot with numbered elements
phonectl tap "Search"                   # tap by text, number, grid cell or pixels
phonectl type "lofi music" --submit     # type and press Enter
phonectl volume 40%                     # media volume
phonectl send report.pdf                # send a file to the phone

Full reference: Docs → Commands.

Works on

Android 5–6

Android 7–10

Android 11+

Read the screen, type, tap elements, Back/Home

✅

✅

✅

Tap anywhere (grid, pixels), swipes

over USB

✅

✅

Screenshots

one-time prompt, or USB

one-time prompt, or USB

✅ built in

Apps that block screen capture (banking, streaming) show up black in screenshots; their element list usually still works. iPhone isn't supported: iOS has no equivalent of Android's accessibility service for apps.

Security

  • Paired, not public. Only a computer holding the secret from your QR code can connect. npx android-agent-bridge pair --reset makes a new one.

  • Stays on your network. Wi-Fi or USB straight to your computer. No cloud, no account, no analytics. Wi-Fi traffic isn't encrypted, so use networks you trust; over USB it never leaves the cable.

  • One switch to stop. Turn off the accessibility service and access ends at once.

  • Agents ask first. The bundled guide tells agents to ask before sending, paying, posting or deleting, and never to type passwords.

  • "App blocked to protect your device": install from your computer with npx android-agent-bridge usb, or npx android-agent-bridge wifi (Android 11+, no cable).

  • No phone connected: is start running? Same Wi-Fi? On Windows, allow Node.js through the firewall. Over USB, run usb again.

  • Accessibility switch greyed out (Android 13+): App info → ⋮ → Allow restricted settings.

  • A tap opened nothing right after Home: Android holds app starts for about 5 seconds after Home; run it again.

Build from source

git clone https://github.com/Rudrasamadhiya/android-agent-bridge
cd android-agent-bridge && npm install
cd android && ./gradlew assembleRelease   # JDK 17 + Android SDK

Copy android/app/build/outputs/apk/release/app-release.apk to apk/agent-bridge.apk. The website lives in website/ (Next.js); npm run build there publishes it to docs/.

License

MIT · Made by Rudra Samadhiya

Available Tools

27 tools
phone_appsA

List installed apps that can be opened (name and package).

Inputs: filter.

phone_brightnessA

Read or set screen brightness: "get", 0–100, "auto" or "manual". Needs "Modify system settings" once (phone_permissions grant=true over USB, or the phone opens that settings page).

Inputs: value.

phone_clipboardA

Read the phone clipboard, or set it (set="text"). Android 10+ may hide the clipboard from background apps, so reading can come back empty.

Inputs: set.

phone_device_infoC

Battery (level, charging, temperature, power saver, screen on), the app in front, and which permissions Agent Bridge has (system settings, Do Not Disturb, screen capture, gestures).

Inputs: no named parameters.

phone_dialA

Open the phone dialer with a number filled in. It never places the call; the user presses call. If several dialer apps are installed, Android shows "Complete action using": tap one.

Inputs: number (required).

phone_elementsA

Text list of what is on screen: numbered tappable elements, inputs, text and their positions. Cheaper than a screenshot. all=true also lists elements hidden under sheets or dialogs (for debugging).

Inputs: all.

phone_keyC

System buttons and keys: back, home, recents, notifications, quick_settings, enter, lock, power_dialog.

Inputs: key (required), after, settle.

phone_notificationsC

Notifications that arrived on the phone since the Agent Bridge service started (app, text, time), newest first.

Inputs: clear, limit.

phone_ocrA

Read the text drawn on the screen (on-device OCR) with positions. Use when something you can see in a screenshot is missing from phone_elements: many apps hide tab bars, rows or custom-drawn buttons from accessibility. phone_tap with that text also falls back to OCR automatically.

Inputs: no named parameters.

phone_open_appA

Open (launch) an installed app by its name ("WhatsApp") or package ("com.whatsapp"). With store=true, an app that is not installed is shown in the Play Store instead (nothing is installed automatically).

Inputs: name (required), after, store, settle.

phone_permissionsB

Check what Agent Bridge is allowed to do. grant=true switches on the one-time permissions (Modify system settings, Do Not Disturb access) over USB with adb.

Inputs: grant.

phone_received_filesB

Files the user sent from the phone to this computer (newest first) and the folder they are in, so you can open or read them.

Inputs: limit.

phone_screenA

Screenshot of the phone with every tappable element boxed and numbered, plus the element list as text. mode "grid" overlays lettered cells (A1 top-left) for spots without an element (games, maps, images); "both" draws both. Use phone_elements instead when text is enough.

Inputs: cols, mode, maxSide.

phone_scrollA

Scroll the screen or one scrollable element. direction is where the content moves into view: "down" shows what is below.

Inputs: direction (required), after, amount, settle, +1 more.

phone_send_filesA

Send files from this computer to the phone (absolute paths). They are saved in Downloads/Agent Bridge on the phone. Works over Wi-Fi or USB.

Inputs: paths (required).

phone_settingsA

Open a system settings page directly: settings, wifi, bluetooth, mobile-data, airplane, hotspot, nfc, location, display, sound, battery, storage, apps, notifications, security, privacy, accessibility, date, language, keyboard, developer, about, dnd, cast, vpn; Android 10+ panels: wifi-panel, internet-panel, volume-panel. Or app= for an app's info page (permissions, storage, force stop).

Inputs: app, page.

phone_statusA

Is a phone connected? Shows model, Android version, how it is connected and what it can do. Call first; if nothing is connected it explains how to pair.

Inputs: no named parameters.

phone_stop_appA

Force-stop an app by package (needs the phone on USB). Unsaved work in that app is lost.

Inputs: package (required).

phone_swipeB

Drag from one point to another (sliders, swipe-to-dismiss, custom gestures). from/to take the same targets as phone_tap.

Inputs: to (required), from (required), ms, after, +1 more.

phone_tapB

Tap (or long-press) something on the phone. what to act on: element number from the last screen ("12"), grid cell ("C7"), pixel coordinates ("540,1200") or visible text ("Sign in"; text missing from the element list is found by OCR).

Inputs: target (required), long, after, settle.

phone_toggleB

Quick device switches. flashlight: on|off. rotation: get|auto|portrait|landscape (needs "Modify system settings" once). dnd (Do Not Disturb): get|on|alarms|total|off (needs DND access once). ringer: get|normal|vibrate|silent.

Inputs: setting (required), value.

phone_typeA

Type text into an input (no keyboard tapping needed). Without target it types into the focused input. submit presses Enter/Search/Send afterwards.

Inputs: text (required), after, append, settle, +2 more.

phone_volumeA

Read or change volume. stream: media (default), ring, notification, alarm, call, system. action: get, up, down, mute, unmute, max, a level number, or a percentage like "40%". Returns every stream level and the ringer mode.

Inputs: show, action, stream.

phone_wait_forB

Wait until some text appears on screen (page loads, messages arriving). Returns the element list.

Inputs: text (required), timeout.

phone_wakeA

Turn the screen on. A PIN, pattern or password lock stays locked: ask the user to unlock.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools target a distinct resource+action, and descriptions proactively explain boundaries (phone_screen vs phone_elements vs phone_ocr, phone_tap vs phone_swipe). The weaker spots are the informational trio phone_status / phone_device_info / phone_permissions, which overlap on connection and permission state, and phone_scroll vs phone_swipe, which both move content.

    Naming Consistency4/5

    All 27 tools share the phone_ prefix, giving a strong predictable family. Action naming is mostly verb_noun (phone_open_app, phone_stop_app, phone_send_files, phone_open_link), with a minority of bare-noun tools (phone_screen, phone_elements, phone_apps, phone_status) that read fine but break the pattern slightly.

    Tool Count3/5

    27 tools is at the heavy end for a single-purpose bridge, and a few (phone_ocr, phone_wait_for, phone_web_search, phone_dial) feel like conveniences layered on top of a core tap/type/screen loop. Most tools do earn their place given the breadth of device control, so it is borderline rather than bloated.

    Completeness4/5

    The surface covers the full device-automation lifecycle: discovery, UI reading, input, navigation, apps, files both directions, settings, toggles, notifications, clipboard and permissions. Gaps are minor and partly intentional (no direct call placement, no app install/uninstall, no SMS or contacts), which agents can route around via deep links or the UI.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP server that gives AI agents full vision and control over Android devices via ADB and scrcpy. Supports screenshots, input, apps, UI automation, shell, files, and clipboard.
      38
      392 npm
      136
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to control a physical Android device or Docker-hosted emulator over ADB by taking screenshots and performing taps, swipes, key presses, text input, shell commands, app launches, and device info queries. It runs as a local MCP stdio server alongside a web UI and REST API for remote access.
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible AI assistants to see and control Android devices through screenshots, taps, swipes, typing, app management, UI inspection, file transfer, shell commands, and audio/video streaming. It connects over ADB with optional low-latency acceleration for faster input and near-instant screenshots.
      392 npm
      MIT