droidsight runs on your own machine — the client starts it, so there is no endpoint to ping. 44 installs a week from npm. Last commit 25 Aug 2026.
Drives a real Android device over ADB and attaches the resulting screen to every action.
We read the source, 5 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.
child = spawn(binary, process.argv.slice(2), { stdio: "inherit" });
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 droidsight -- npx -y @edgecasehuman/droidsight
{
"mcpServers": {
"droidsight": {
"command": "npx",
"args": [
"-y",
"@edgecasehuman/droidsight"
]
}
}
}
[mcp_servers.droidsight]
command = "npx"
args = ["-y", "@edgecasehuman/droidsight"]
{
"mcpServers": {
"droidsight": {
"command": "npx",
"args": [
"-y",
"@edgecasehuman/droidsight"
]
}
}
}
{
"servers": {
"droidsight": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@edgecasehuman/droidsight"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
DROIDSIGHT_DEVICE_SERIAL (The only Android target the process may use. Required when ADB reports more than one authorized device; the server refuses to guess), DROIDSIGHT_ADB_PATH (Explicit path to the ADB executable. Falls back to ANDROID_SDK_ROOT, ANDROID_HOME, then PATH), DROIDSIGHT_LOCAL_ROOT (Confines host paths used by APK installation and file push/pull. Defaults to the process working directory), DROIDSIGHT_DEVICE_PIN (Numeric PIN for UI actions that require automatic unlock), DROIDSIGHT_ALLOW_SHELL (Set to 1 to publish the arbitrary shell and macro tools. Grants authority equivalent to broad ADB shell access), DROIDSIGHT_DEBUG_LOG (Path to a persistent debug log. File logging is otherwise disabled), DROIDSIGHT_LOG (Tracing filter. Defaults to warn, or debug when a debug log path is set), DROIDSIGHT_EVENTS (Set to 1 to start the long-running device event monitor. Requires DROIDSIGHT_DEVICE_SERIAL), DROIDSIGHT_SENTINEL (Set to 1 to start the background enforcement loop. It re-applies watched device state on a timer, including unlocking the screen. Off by default).
Drive the Android device attached to ZennoDroid ProjectMaker: screen, elements, apps, gestures.
Drive the Android devices of the tasks running in ZennoDroid: screen, elements, apps, gestures.
Drive a real Playwright browser: annotated screenshot + structured page state after every action.
Drive an Android emulator or device over adb: screenshot, inspect UI, tap, type, build and test.
Drive a hosted ERIUS PHONE Android device: read the screen, tap, type, install APKs, get crash logs.
Drive devices and APIs from their W3C Thing Description. You gate every operation.
Drive a stealth-patched Chromium daemon: navigate, screenshot, eval JS, attach over CDP.
Drive cloud Android phones on US mobile IPs. Read the screen, tap, type, install apps and run tasks.
Answers built from our own checks of this server.