Android Viewer runs on your own machine — the client starts it, so there is no endpoint to ping. 897 installs a week from npm. Last commit 3 Nov 2026.
Drive Android emulators: screenshots, taps, swipes, keys, text, rotation and foldable postures.
We read the source, 3 d ago · rules 995398eba69f
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.
execFile(ADB, full, { timeout, encoding, maxBuffer: 64 * 1024 * 1024 }, (err, stdout, stderr) => {
const sdkTool = (rel, fallback) => (existsSync(path.join(SDK, rel)) ? path.join(SDK, rel) : fallback);
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.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add android-viewer -- npx -y @acertijosapps/android-viewer
{
"mcpServers": {
"android-viewer": {
"command": "npx",
"args": [
"-y",
"@acertijosapps/android-viewer"
]
}
}
}
[mcp_servers.android-viewer]
command = "npx"
args = ["-y", "@acertijosapps/android-viewer"]
{
"mcpServers": {
"android-viewer": {
"command": "npx",
"args": [
"-y",
"@acertijosapps/android-viewer"
]
}
}
}
{
"servers": {
"android-viewer": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@acertijosapps/android-viewer"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
ANDROID_VIEWER_URL (Viewer to show actions live (default http://localhost:8093); without it, adb is used directly), ANDROID_HOME (Android SDK location, if adb and emulator are not found automatically).
See and drive Android emulators on a Mac: screenshot, tap, type, UI tree, logs, root.
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.
AI agents see and drive the Android Emulator: screenshots, UI in dp, tap, dark mode, RTL, logcat.
57 tools for AI-powered iOS Simulator automation — tap, swipe, type, screenshots, and more.
Drive Electron apps over CDP: screenshots, clicks, drags, keys, JS in renderer and main, logs.
Drive an Android emulator or device over adb: screenshot, inspect UI, tap, type, build and test.
See and operate Expo / React Native apps: screenshots, taps, typing, auto-testing. No emulator.
Answers built from our own checks of this server.