Drives a real Android device over ADB and attaches the resulting screen to every action.
Droidsight is an MCP integration. Drives a real Android device over ADB and attaches the resulting screen to every action.
The published npm package is @edgecasehuman/droidsight, version 1.0.0. Its declared MCP transport is stdio.
The package declares 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..
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository. This profile uses version 1.0.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related other integrations MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| 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. | Optional |
| DROIDSIGHT_ADB_PATH | Explicit path to the ADB executable. Falls back to ANDROID_SDK_ROOT, ANDROID_HOME, then PATH. | Optional |
| DROIDSIGHT_LOCAL_ROOT | Confines host paths used by APK installation and file push/pull. Defaults to the process working directory. | Optional |
| DROIDSIGHT_DEVICE_PIN | Numeric PIN for UI actions that require automatic unlock. | Optional |
| DROIDSIGHT_ALLOW_SHELL | Set to 1 to publish the arbitrary shell and macro tools. Grants authority equivalent to broad ADB shell access. | Optional |
| DROIDSIGHT_DEBUG_LOG | Path to a persistent debug log. File logging is otherwise disabled. | Optional |
| DROIDSIGHT_LOG | Tracing filter. Defaults to warn, or debug when a debug log path is set. | Optional |
| DROIDSIGHT_EVENTS | Set to 1 to start the long-running device event monitor. Requires DROIDSIGHT_DEVICE_SERIAL. | Optional |
| 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. | Optional |
Connect Flutter applications with AI coding assistants via the Model Context Protocol.
Extracts and analyzes errors and warnings from Xcode build logs for integration with AI assistants.
Run A/B experiments through your AI assistant. SDKs for Ruby, Python, JS, Node, React Native, Go.
ADB Friend is a tiny cli tool, which helps you to manage your Android device via ADB. Its features were mostly designed for developers, but it can be
MCP server for Android Debug Bridge (ADB) interactions in TypeScript
Boot an AVD, screenshot, read the UI hierarchy, tap/swipe/type, set a device lock, read logcat, run Gradle builds and tests. 79 tools, from Claude Code, Cursor, VS Code, or any MCP client over stdio.