Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Drive Android emulators: screenshots, taps, swipes, keys, text, rotation and foldable postures.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
ANDROID_VIEWER_URL, ANDROID_HOMEYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"android-viewer": {
"command": "npx",
"args": [
"-y",
"@acertijosapps/android-viewer",
"mcp"
],
"env": {
"ANDROID_VIEWER_URL": "your-value",
"ANDROID_HOME": "your-value"
}
}
}
}Run this in your terminal
claude mcp add android-viewer --env ANDROID_VIEWER_URL=your-value --env ANDROID_HOME=your-value -- npx -y @acertijosapps/android-viewer mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"android-viewer": {
"command": "npx",
"args": [
"-y",
"@acertijosapps/android-viewer",
"mcp"
],
"env": {
"ANDROID_VIEWER_URL": "your-value",
"ANDROID_HOME": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"android-viewer": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@acertijosapps/android-viewer",
"mcp"
],
"env": {
"ANDROID_VIEWER_URL": "your-value",
"ANDROID_HOME": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
ANDROID_VIEWER_URL envANDROID_HOME envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account acertijosapps, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.2) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Recta
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Cheaper cross-chain stablecoin routes for AI agents; 5 % of the verified saving, nothing if none.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Live Android emulator viewer for the browser, plus an MCP server so an AI agent can drive it. Built for the browser pane of AI coding tools (such as Claude Code): you and the agent watch and control the same emulator, in real time, including foldable postures.
adb exec-out screenrecord (H.264) over WebSocket, decoded in the browser with WebCodecs.adb shell input commands.adb.adb) and, to list and start AVDs, the emulator. Found through ANDROID_HOME, ANDROID_SDK_ROOT or the default SDK location; override with ADB and EMULATOR.npx @acertijosapps/android-viewer
Open http://localhost:8093 and pick a device. Deep links: ?avd=Pixel_10 or ?serial=emulator-5554.
android-viewer [options] Start the viewer
android-viewer mcp [options] Start the MCP server on stdio
-p, --port Viewer port (default 8093, env PORT) --host Interface to bind (default 127.0.0.1, env HOST) --viewer-url Viewer the MCP talks to (default http://localhost:8093)
Other environment variables: MAX_DIM (longest side of the encoded video, default 1024), BIT_RATE (default 6M), SCREENSHOT_MAX (longest side of MCP screenshots, default 1024) and DEBUG=1 (logs every input command).
Claude Code:
claude mcp add android-viewer -- npx -y @acertijosapps/android-viewer mcp
Any other MCP client:
{
"mcpServers": { "android-viewer": { "command": "npx", "args": ["-y", "@acertijosapps/android-viewer", "mcp"] } } }
Also listed in the official MCP Registry as io.github.acertijosapps/android-viewer.
Keep the viewer running (npx @acertijosapps/android-viewer) to watch what the agent does. Without it, the MCP drives the device through adb directly.
| Tool | What it does |
|---|---|
list_devices | AVDs on the machine (with serial and booted when running) and other adb devices |
launch_avd | Start an AVD by name |
get_state | Display size, rotation, current posture, available postures and the viewer URL |
screenshot | PNG of the active display, longest side ≤ 1024 px |
tap | input tap |
swipe | input swipe; same start and end with ≥ 500 ms is a long press |
press_key | back, home, recents, power, wakeup, volup, voldown, enter, delete, tab, escape |
type_text | input text (printable ASCII) |
rotate | Rotate 90° left or right (emulators) |
set_posture | closed, half_opened, opened, rear_display, a state id, or reset; returns the new state |
Coordinates are normalized to 0–1 over the screenshot (x = pixel_x / image_width), so they hold in any posture or orientation. serial is optional when only one device is connected.
Add the viewer to .claude/launch.json and open it with preview_start android-viewer:
{
"version": "0.0.1", "configurations": [ { "name": "android-viewer", "runtimeExecutable": "npx", "runtimeArgs": ["-y", "@acertijosapps/android-viewer"], "port": 8093, "autoPort": false } ] }
The MCP uses the viewer's API; you can call it too. serial goes in the query string or the body and is optional with a single device. POST requests require content-type: application/json and a local origin, so other websites can't drive your devices.
| Endpoint | ||
|---|---|---|
GET /api/devices | [{ avd, serial, booted, model }]: serial: null = stopped, booted: null = didn't answer in time | |
GET /api/state | Display size, rotation, displayId, posture and available postures | |
GET /api/screenshot?max= | PNG; real screen size in X-Screen-Width / X-Screen-Height | |
POST /api/tap | { x, y } | |
POST /api/swipe | { x1, y1, x2, y2, ms } | |
POST /api/key | { key } | |
POST /api/text | { text } | |
POST /api/posture | { posture } | |
POST /api/rotate | `{ direction: "left" \ | "right" }` |
POST /api/launch | { avd } |
When a viewer tab is watching the device, actions go through its live session: the viewer updates at once and a watchdog restarts the stream if a gesture produces no frames.
dumpsys display (size, rotation and the physical display behind logical display 0) and cmd device_state state. When the display changes, it waits for it to settle and restarts screenrecord with --display-id of the new panel: folding a device switches panels.screenrecord only emits frames when the screen changes, so the viewer keeps the GOP since the last IDR for late joiners and sends a screenshot while there is no video.screenrecord runs per device at a time: two of them exhaust the emulator's software encoder (err=-38). Restarts requested by clients are rate-limited.screencap (compressing PNG inside the emulator is slow under load), are scaled down by area averaging and encoded as PNG with node:zlib, with no native dependencies.input swipe with the real duration), not live.type_text and press_key.adb shell call can take seconds.DeviceStateManager.requestState), it wins over set_posture while it is in the foreground.Flip_Horizontal_Fold style AVDs with a single physical display change state when closed, but the picture stays the same.ws-scrcpy was tried first: streaming and input work, but the video freezes on a posture change until you reload (its scrcpy 1.19 server stays bound to the previous display), and it has no posture controls.
Branching model (main · beta), Conventional Commits and releases are described in CONTRIBUTING.md; changes are listed in CHANGELOG.md.
Made by AcertijosApps. See the rest of our libraries at acertijosapps.com/librerias.
Questions or proposals: acertijos.contacto@gmail.com or open an issue.
MIT