
Jidr
io.github.AbdurahmanAlmehdiPublished by GitHub account AbdurahmanAlmehdiv0.3.1Updated Nov 4, 2026
See and drive Android emulators on a Mac: screenshot, tap, type, UI tree, logs, root.
Overview
Lets an AI assistant see and drive virtual Android devices on an Apple Silicon Mac: screenshots, taps, typing, UI tree and logs.
- What you can do
- Inspect and control a running virtual Android device: take screenshots, tap, type, read the UI tree and pull logs.
- Manage emulated devices and images through the companion CLI, which the MCP server shares a control protocol with.
- Set root mode on a device (none, shell root, or full Magisk root) and revert it.
- Capture device state as PNG screenshots, MP4 recordings and snapshots.
- When to use it
- Useful when an assistant should test or operate an Android app on a Mac without a physical phone, for example driving UI flows, checking screens and reading logs during development or QA.
- Requirements
- Local install on macOS 14 or later on Apple Silicon, with about 10 GB free disk space. The Jidr app and CLI must be installed (Homebrew cask or DMG); the MCP server runs via the jidr mcp command or the Claude Desktop bundle. First launch downloads the Android SDK and a system image after accepting Google's license.
Installation
In SourceWeft
- Open Jidr in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Jidr (جذر)
Android on your Mac, rooted in a minute.
[Latest release] [macOS 14+ on Apple Silicon]
Jidr creates and runs virtual Android phones and tablets on Apple Silicon Macs. Pick Full root and Magisk is patched in and verified for you; pick Shell root for adb root; or keep the device stock. It's a free, open-source alternative to Genymotion Desktop, written in Rust, with a desktop app, a CLI and an MCP server for AI agents.
Or download the DMG. Site: jidr.ly. News: @Jidr_ly on X.
Features
- Devices: create, clone, start, stop and delete virtual devices from Google's emulator images (API 29–36, arm64). Jidr keeps its own SDK and never modifies Android Studio's SDK or AVDs.
- One-click root: None, Shell root (
adb root) or Full root (Magisk, patched into a per-device copy of the ramdisk and verified withsu -c id). Revert at any time. Play Store images get a guided beta. - Player window: the device screen with mouse and keyboard input, drag-and-drop for APKs and files, and logcat.
- Widgets: battery, rotation and motion sensors, network (Wi-Fi, mobile data, speed and delay profiles), calls, SMS and signal bars, GPS with GPX/KML route replay on an OpenStreetMap map, fingerprint, the host webcam as the camera, clipboard and developer toggles.
- Media and state: PNG screenshots, MP4 recordings, and snapshots tagged with the root mode they were taken in.
- Build identity: set build properties (model, brand, fingerprint…) on Full-root devices.
- CLI: every action is a
jidrcommand, with--jsonoutput and stable exit codes for CI. - MCP server:
jidr mcplets Claude and other MCP clients see and drive a device: screenshot, tap, type, UI tree, logs.
No accounts, no telemetry, no paid tier.
[The Jidr player: a running device, its toolbar, and the battery widget]
Install
You need macOS 14 or later on Apple Silicon, and about 10 GB of free disk space for the SDK and one system image.
- Homebrew:
brew install --cask abdurahmanalmehdi/tap/jidrinstallsJidr.appand puts thejidrCLI on yourPATH. Update withbrew upgrade --cask jidr. - DMG: download
Jidr-<version>-arm64.dmgfrom the latest release and drag Jidr to Applications. The CLI is at/Applications/Jidr.app/Contents/Helpers/jidr.
On first launch the app finds or downloads the Android SDK and a system image, after you accept Google's license.
Quick start (CLI)
Use it from an AI agent
Add Jidr to Claude Code as an MCP server:
For Claude Desktop, open jidr-mcp-<version>-darwin-arm64.mcpb from the latest release. Jidr is also in the MCP Registry as io.github.AbdurahmanAlmehdi/jidr. docs/mcp.md lists the tools.
Agent skills teach Claude Code, Cursor, Codex and other agents to create and drive Jidr devices with the CLI (jidr), to test an app on them (jidr-app-testing) and to get devices of their own without crowding the machine (jidr-agent-devices). Install them with the open skills CLI:
They live in skills/.
Documentation
- CLI reference
- MCP tools
- Root modes
- Control protocol: the JSON-RPC protocol the app, the CLI and the MCP server share
- Design system
- Decisions and architecture decision records
- Feature parity with Genymotion Desktop
- Clean-room policy
- Changelog
Build from source
You need rustup (it installs the toolchain pinned in rust-toolchain.toml) and protoc (brew install protobuf). CONTRIBUTING.md has the full setup and how to run the tests.
Licensing
Jidr is split-licensed. The desktop app (crates/jidr-ui, apps/jidr-gui) is GPL-3.0-only because it links Slint. Everything else (CLI, daemon, MCP server, libraries, site) is Apache-2.0. See LICENSE-APACHE, the LICENSE-GPL files in the two GUI crates, and NOTICE.
Jidr downloads the Android Emulator and system images from Google under the Android SDK License, which you accept in the app. It downloads Magisk (GPL-3.0) only when you choose Full root. None of these are bundled.
Questions and contributing
Questions, ideas and setups you want to share go in Discussions; bugs go in Issues.
Contributions are welcome: read CONTRIBUTING.md. Report security issues as described in SECURITY.md. If you work with an AI coding agent, point it at AGENTS.md.
Trademarks
Android is a trademark of Google LLC. Genymotion is a trademark of its owner. Jidr is not affiliated with Google or Genymotion.
Source: README.md at commit dc82e05
Tools
0Version history
3- v0.3.1LatestNov 4, 2026
- v0.3.0Nov 3, 2026
- v0.2.0Oct 18, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts