Skip to content
ReviewRamble

The weekly brief

AI, reviewed, in your inbox.

  • New reviews of tools, models, MCP servers and repos, with the verdict up front
  • Re-checked prices and ratings when something changes
  • New analysis pieces as they are published

Models, agents, MCP servers and the tools actually worth your time.

One email a week. Unsubscribe with the link in any brief. How we use your email

Droidline

Drives real Android phones from Python, Node.js, the shell, HTTP or an MCP server, through an on-phone app instead of ADB, USB or root.

Reviewed by ReviewRamble editors · Updated

View on GitHub Open source

Share this page:XLinkedInFacebookRedditWhatsAppEmail

Our rating

3.5/5

A thoughtfully designed way to give an agent a real Android phone without ADB, held back for now by being a six-week-old 0.1 release that has barely met real handsets.

What is Droidline?

Droidline is an open-source tool for automating real Android phones from code. A Go server runs on your PC (droidline serve, on localhost:8780) and an app on the phone, using the accessibility service and its own keyboard, carries out commands. Phones pair with a QR code or a 6-digit code, so there is no developer mode, USB debugging or root. The same commands, such as touch, input, wait and screenshot, are available from Python, Node.js, .NET, the CLI, plain HTTP, Appium clients and an MCP server that Claude, Cursor or VS Code can use.

Commands target elements by text, id or description rather than pixels, wait for them by default, and return coded errors that say whether a retry helps. One PC can drive a shelf of phones in parallel. Phones always connect outwards, over the same Wi-Fi, a forwarded port, a tunnel or a relay you deploy, with traffic encrypted end to end using P-256 and AES-256-GCM. With permission, it can also read texts, call history, contacts and location, place calls and forward notifications.

The repo is MIT-licensed with about 560 GitHub stars. It was created on 7 October 2026 and v0.1.13 shipped on 3 November 2026.

Is Droidline worth it?

Droidline's distinctive choice is to skip ADB. Instead of developer options and a USB cable, an ordinary app with accessibility and keyboard permissions does the tapping, and the phone dials out to your PC, so it works across mobile data as well as on the desk. For an AI agent that matters: the MCP server exposes the same dump, screenshot and touch commands as the SDKs, and you can cut it down with --tools or --read-only so the agent only looks.

The engineering shows care. Commands are generated from one spec for every language, waits are built in, a command in flight when the connection drops is answered from the phone's cache rather than run twice, and remote routes encrypt every line so a tunnel or relay only sees ciphertext. The README also says plainly what it cannot do: get past a PIN, open screens an app does not export, read one-time codes on Android 15 and later, or see elements in games.

The catch: maturity and reach. By the project's own status page, the server and SDKs pass tests against a simulated phone and the app has run on an Android 13 emulator; testing across phone brands is the next step. It is a single maintainer's project with about 560 stars and 75 npm downloads in the week to 19 November. The permissions it asks for, accessibility control plus optional access to texts, calls and contacts, amount to full control of the phone, and features such as per-app proxies and toggling airplane mode for new mobile IPs are built for phone farms, which some apps' terms forbid.

Our take: agent-device is the safer pick when you are testing your own app on emulators. Droidline is the one to watch when the job is a physical phone in a drawer that an agent should operate, and worth trying now on a spare handset rather than your own.

Where it earns its place

  • A mobile developer testing a login flow

    Check that sign-in works when the code arrives by text message on a real phone

    Pair a spare phone, script launch, input and touch in Python with pytest, and read the SMS code with the personal-data commands. Free; runs on the PC and phone you already have.

  • A Claude Code user

    Let the agent look at a phone screen and report what an app shows

    Run claude mcp add droidline -- droidline mcp --read-only, so the agent can dump the element tree and take screenshots but not tap. Free; the model's tokens are the only cost.

Before you commit

Setup
Download the droidline archive and droidline-agent.apk from GitHub Releases, run droidline serve, install the app and switch on accessibility, keyboard, notification and battery permissions (allow restricted settings on Android 13+), then droidline pair. droidline-fakephone simulates a phone for a first script.
Integrations
Python (pip install droidline), Node.js (npm install droidline), .NET (dotnet add package Droidline), CLI, HTTP on localhost:8780, MCP server (droidline mcp, a .mcpb bundle for Claude Desktop, listed in the MCP Registry), WebDriver for Appium, pytest plugin, Cloudflare Workers relay.
Data and privacy
No usage data or telemetry, per the README; the server listens on your machine and the app talks only to its paired PC, plus GitHub once a day for update checks. Remote traffic is end-to-end encrypted. The app can read texts, call history, contacts and location once you grant it.
Cost at scale
No paid edition. Costs are the phones, any relay or tunnel you run, and model tokens when an agent drives it.
Limits
Android 9 or later only; no iOS. Settings recipes depend on phone maker, Android version and language. Games and custom-drawn apps expose no elements, so fall back to coordinates and colour checks.

What’s good

  • No ADB, USB cable, developer mode or root
  • Same commands across Python, Node.js, .NET, CLI, HTTP, Appium and MCP
  • MCP tools can be limited with --tools or --read-only
  • End-to-end encryption on remote routes; no telemetry, per the README

What’s not

  • Version 0.1; real-phone testing across brands not yet done
  • Single maintainer and a small user base so far
  • Accessibility and personal-data permissions give it full phone control
  • Cannot get past lock screens or read OTPs on Android 15+

Best for

Developers who want an AI agent or a script to operate a physical Android phone they own, without setting up ADB.

Droidline alternatives

Droidline: common questions

Is Droidline worth it?
A thoughtfully designed way to give an agent a real Android phone without ADB, held back for now by being a six-week-old 0.1 release that has barely met real handsets. We rate it 3.5 out of 5.
How much does Droidline cost?
Free and open source (MIT).
What are the downsides of Droidline?
Version 0.1; real-phone testing across brands not yet done; single maintainer and a small user base so far; accessibility and personal-data permissions give it full phone control; cannot get past lock screens or read OTPs on Android 15+.
Who is Droidline best for?
Developers who want an AI agent or a script to operate a physical Android phone they own, without setting up ADB.
How much does Droidline cost for a team or in production?
No paid edition. Costs are the phones, any relay or tunnel you run, and model tokens when an agent drives it.
Is Droidline safe for company data?
No usage data or telemetry, per the README; the server listens on your machine and the app talks only to its paired PC, plus GitHub once a day for update checks. Remote traffic is end-to-end encrypted. The app can read texts, call history, contacts and location once you grant it.
What are the best Droidline alternatives?
The closest alternatives we have reviewed are agent-device.

Answers checked Nov 20, 2026.