Oh My Android runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 30 Sep 2026.
AI agents see and drive the Android Emulator: screenshots, UI in dp, tap, dark mode, RTL, logcat.
We read the source, 6 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.
out = subprocess.run([server], input=lines, capture_output=True, text=True, timeout=30).stdout
let server = Process()
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.
Drive an Android emulator or device over adb: screenshot, inspect UI, tap, type, build and test.
Control Android devices and emulators via ADB — screenshots, UI automation, and logcat.
Disposable cloud Android emulators for coding agents: run an APK or PR build, tap, type, screenshot.
Gives AI agents eyes and hands into running React Native apps: logs, REPL, tap, screenshots
Gives AI agents eyes and hands into running React Native apps: logs, REPL, tap, screenshots
Lets AI agents drive a real terminal: type, press keys, click, read the screen, take screenshots.
Let AI agents inspect and drive running WPF apps: tree, bindings, screenshots, clicks, text input.
Live iOS Simulator and browser screenshots, logs, and a personal MCP hub for AI coding agents.
Answers built from our own checks of this server.