adb-mcp: Android emulator and device control over adb runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 26 Aug 2026.
Drive an Android emulator or device over adb: screenshot, inspect UI, tap, type, build and test.
We read the source, 1 d ago · rules ccca72095570
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
proc = subprocess.Popen(
path := filepath.Join(opts.Destination, rel)
s.LastHMRUpdate = markerTime.Format(time.RFC3339)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Control Android devices and emulators via ADB — screenshots, UI automation, and logcat.
MCP server for Android automation with UI interaction, screenshots, and device control
Disposable cloud Android emulators for coding agents: run an APK or PR build, tap, type, screenshot.
AI agents see and drive the Android Emulator: screenshots, UI in dp, tap, dark mode, RTL, logcat.
AI control of Android/iOS devices. Screenshots, UI tree, AI vision, Flutter, video. 49 tools.
MCP server for desktop, browser (CDP), and Android automation. Screenshot, OCR, click, type.
MCP server for Roku device automation — deploy, ECP control, screenshots, and debug console
AI game maker: build, run, screenshot and play-test Godot and retro console games in a live project
Answers built from our own checks of this server.