droidsight MCP server

droidsight

An MCP server that drives a real Android device over ADB — and hands the agent back the screen its action produced.

One native binary. The server has no Python, Appium, scrcpy, or ffmpeg dependency and runs no Node at all — npx below is only a convenient installer — so the runtime is the binary plus adb. A background H.264 screenrecord stream is decoded in process, so the screen that follows an action is attached to the tool result automatically instead of costing a second round trip to ask what happened.

Every image carries the coordinate space it was produced in, so a model can tap what it just looked at without guessing a scale factor. When the accessibility tree comes back empty — Flutter, React Native, canvas, games — OCR and template matching still find the target.

This is a powerful local controller, not a sandbox. Run it only against a device and an MCP client you trust.

Install

npx -y @edgecasehuman/droidsight

That downloads a prebuilt binary for your platform and needs no build tools. The server is also listed in the official [MCP Registry] as io.github.edgecasehuman/droidsight.

To compile it instead, from [crates.io]:

cargo install droidsight

Or from source:

cargo build --locked --release --bin droidsight

Both compiling routes need NASM on the PATH. The H.264 decoder is built from C++ by openh264-sys2, which assembles its hot paths with NASM, and no platform ships it by default -- without it the build fails inside a transitive dependency rather than in this crate. Install it with apt install nasm, brew install nasm, or winget install NASM.NASM. The npx route above needs none of this.

The server is target/release/droidsight. It speaks newline-delimited JSON-RPC 2.0 over stdin and stdout.

[MCP Registry]: https://registry.modelcontextprotocol.io [crates.io]: https://crates.io/crates/droidsight

Client configuration

{
  "mcpServers": {
    "android": {
      "command": "npx",
      "args": ["-y", "@edgecasehuman/droidsight"],
      "env": {
        "DROIDSIGHT_DEVICE_SERIAL": "<serial from `adb devices`>"
      }
    }
  }
}

ADB must be reachable through PATH, ANDROIDSDKROOT, ANDROIDHOME, or an explicit DROIDSIGHTADBPATH. If more than one authorized device is visible the server refuses to guess; set DROIDSIGHTDEVICE_SERIAL.

Tools

Thirty-one tools are published by default. Two more appear only when DROIDSIGHTALLOWSHELL=1 is set, and are listed last.

Seeing the screen

Driving the device

Shortened. The full README is on GitHub.