Jidr runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 18 Oct 2026.
See and drive Android emulators on a Mac: screenshot, tap, type, UI tree, logs, root.
We read the source, 4 d ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
&format!("rm -rf {MAGISK_ENV_DIR}"),
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.
pub type DeviceUpdate = Box<dyn for<'a> FnOnce(&'a mut Device) + Send + 'static>; /// Reports job progress: fraction (`None` = indeterminate) and a message. pub type ProgressFn = Arc<dyn Fn(Option<f32>, &str) + Send + Sync>;
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Jidr and you get told the day something new turns up.
AI agents see and drive the Android Emulator: screenshots, UI in dp, tap, dark mode, RTL, logcat.
Drive an Android emulator or device over adb: screenshot, inspect UI, tap, type, build and test.
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.
Drive live Flutter apps: snapshot the Semantics tree, tap, type, scroll and screenshot.
Let AI agents see, tap, type, scroll, screenshot and debug your Expo app on a real phone.
Let agents see and drive a Mac: screenshots, clicks, typing, apps and virtual displays.
Give your AI agent a real cloud Android phone: push APKs, drive it, get screenshots and logs.
Answers built from our own checks of this server.