Oh My Android

Testing an Android app means doing the same chores over and over: switch to dark mode, make the font huge, change the language to Arabic to check RTL, turn on TalkBack, throttle the network to 3G, clear the app data, take a screenshot. Each one is buried in the emulator's settings or needs an adb shell command you have to look up again.

Oh My Android puts all of them in a floating panel next to the emulator. Every icon shows the real state of the device, and one click changes it. It is a native macOS app for Android developers and QA testers: an Android Emulator GUI, an adb GUI for real phones, a Layout Inspector in dp, an accessibility checker, and an Android MCP server for Claude Code, Codex, Cursor and other AI coding agents.

• ⚡ One click for nearly 50 everyday test actions
• 📱 Emulators and real phones: USB or Wi‑Fi adb
• 🔍 Layout Inspector: measure any view in dp, Figma-style, and overlay your design
• ♿ Accessibility audit: TalkBack order, missing labels, small touch targets
• 🗄️ Data Inspector: SharedPreferences and SQLite of your debug build
• 🤖 MCP server for AI agents: your coding agent can see the screen, tap, switch settings and read logs
• 🪶 Native and light: SwiftUI, Liquid Glass, event-driven (easy on the battery), no Electron, no telemetry
• 🆓 Free and open source (MIT)

How it compares with Android Studio, scrcpy and other tools: docs/COMPARISON.md.

Install

brew install --cask ateymoori/tap/oh-my-android

Or download the zip from the latest release, unzip it, and move Oh My Android.app to Applications. The app is signed and notarized by Apple.

Updates: when a new version is out, a dot shows on the menu bar icon. Click Update to … in the menu, read what's new, and install in one click. The app never updates without asking. It checks once a day; turn it off in Settings → Updates. brew upgrade --cask oh-my-android works too.

Requirements: macOS 26 Tahoe or later, Apple silicon, and the Android SDK from Android Studio (or brew install --cask android-commandlinetools). The app finds the SDK by itself. If yours is in an unusual folder, pick it in Settings → Android SDK.

Use it from Claude Code, Codex or Cursor

brew install --cask ateymoori/tap/oh-my-android

claude mcp add --scope user oh-my-android -- ohmyandroid-mcp   # Claude Code
codex mcp add oh-my-android -- ohmyandroid-mcp                 # Codex CLI
gemini mcp add --scope user oh-my-android ohmyandroid-mcp      # Gemini CLI

For Cursor and VS Code, use the install buttons in AI agents (MCP). Then start an emulator and ask your agent: "Take a screenshot of the emulator and check this screen in dark mode."

Features

Destructive actions (Clear data, Uninstall, Reset permissions) ask before they run.

No more adb commands

Every icon replaces a command you would otherwise type or search for:

Layout Inspector

Freeze the screen and measure it like in Figma. Works with Jetpack Compose and classic Views.

• Hover any element to see its size in dp. Click one, hover another, and see the distance between them (gaps between siblings, paddings inside a parent).
• 8 dp grid, color picker (hex, ⇧⌘C to copy), and an estimated text size in sp.
• Design overlay: drop a Figma PNG export on the window, choose 1× / 2× / 3× or Fit width, set the opacity or use Difference blend, and nudge it with the arrow keys. Compare design and build pixel by pixel.

Accessibility audit

Press ⇧⌘A in the Layout Inspector. Every screen-reader stop gets a number in approximate TalkBack order, with what TalkBack announces and a list of problems: unlabeled buttons, images without a content description, and touch targets smaller than 48 × 48 dp.

Data Inspector

Browse the SharedPreferences (key, type, value) and SQLite databases (tables, first 500 rows) of any debuggable app, with search. It uses adb shell run-as, the same access Android Studio uses, so release builds stay closed. It is read-only: nothing on the device changes.

AI agents (MCP)

Oh My Android includes an MCP server, so your AI coding agent can see and drive the emulator: screenshot, read the UI tree in dp, tap and type, switch to dark mode or RTL, read logcat and the app's database. The agent can build a screen, run it, look at the result, and fix it by itself. The buttons use the Homebrew path /opt/homebrew/bin/ohmyandroid-mcp. With the zip install, use the menu bar setup below.

Set up in one step: menu bar icon → AI Agents → Set Up…, choose your agent, click Copy (or Add to Cursor / Add to VS Code). Or by hand:

claude mcp add --scope user oh-my-android -- ohmyandroid-mcp   # Claude Code
codex mcp add oh-my-android -- ohmyandroid-mcp                 # Codex CLI

{ "mcpServers": { "oh-my-android": { "command": "/Applications/Oh My Android.app/Contents/MacOS/ohmyandroid-mcp" } } }

The JSON works in Cursor, Claude Desktop, Windsurf, Gemini CLI and other agents (VS Code uses "servers"). Homebrew puts ohmyandroid-mcp on your PATH. With the zip install, use the full path above.

Other ways to add it:

• Claude Code plugin: /plugin marketplace add ateymoori/oh-my-android, then /plugin install oh-my-android@oh-my-android
• Claude Desktop extension: open oh-my-android-<version>.mcpb from the latest release
• MCP Registry: listed as io.github.ateymoori/oh-my-android

You stay in control: menu bar icon → AI Agents → Off, Read only or Full control. The server checks it on every call, so a change applies at once. Tools that can lose data are marked destructive, so your agent asks you first.

Ready-made prompts: accessibility_review, ui_matrix (dark mode, large fonts, RTL, pseudo-locales) and debug_crash.

Try asking your agent:

• "Open the app, go to Settings, and check it in dark mode, font scale 2 and Arabic. Fix what breaks."
• "The app crashes when I tap Save. Reproduce it, read the crash, and fix it."
• "Audit the login screen for TalkBack and fix the problems in the code."

Built for models: every position is in dp, like your layout code. Output is compact text: a UI tree is about 10× smaller than the raw uiautomator XML, and all 18 tool definitions take about 3k tokens. The server supports MCP 2026-07-28 and the earlier versions (2024-11-05 to 2025-11-25) over stdio, has no dependencies, and needs no network.

Privacy and security

• 🔒 No analytics, no telemetry, no account. The only network request of its own is the update check: once a day it reads a small feed from this repo's GitHub releases. It sends nothing about you or your devices. Turn it off in Settings → Updates.
• Updates (Sparkle) install only when you choose, and only if they are signed with this project's EdDSA key and the same Developer ID.
• Talks only to the adb of your own Android SDK. Text you type is shell-quoted before it reaches the device.
• Database copies from the Data Inspector are deleted when you reload and when the app quits.
• The MCP server runs only when your AI agent starts it, and only with the access you allow. What it reads (screen, UI, logs, app data) goes to your agent, and from there to the agent's model provider.
• Signed with a Developer ID, hardened runtime, notarized by Apple.

Found a vulnerability? See SECURITY.md.

Troubleshooting

• adb not found: pick your SDK in Settings → Android SDK, or set ANDROID_HOME.
• The agent says there is no device: start an emulator or connect a phone, then ask the agent to run list_devices.
• Agent cannot start ohmyandroid-mcp (zip install): only Homebrew puts it on your PATH. Use the full path /Applications/Oh My Android.app/Contents/MacOS/ohmyandroid-mcp.
• Homebrew says the tap is not trusted: Homebrew 6 and later ask you to trust third-party taps. The full brew install --cask ateymoori/tap/oh-my-android trusts only this cask. For short names, run brew trust --cask ateymoori/tap/oh-my-android first.
• The agent gets "Access is Off": menu bar icon → AI Agents → Read only or Full control.

FAQ

Yes. It is free and open source under the MIT license.

No. It is a companion. It controls Google's emulator and your phones through the Android SDK you already have. It bundles no emulator and no SDK.

Yes, over USB or Wi‑Fi adb. Only the emulator-only blocks (GPS, battery, calls, SMS, snapshots, network speed, screen recording) need an emulator.

Yes. The Layout Inspector and the accessibility audit read the Compose semantics tree through uiautomator, the same as for Views.

Any agent that supports MCP over stdio: Claude Code, Claude Desktop, Codex CLI, Cursor, VS Code (GitHub Copilot), Windsurf, Gemini CLI, JetBrains AI, Zed and more. The app does not have to be open; the agent starts the server when it needs it.

Click the 🌙 icon in the panel. The adb way is adb shell cmd uimode night yes (and no to turn it off).

Pick "العربية (RTL)" or another RTL language from the 🌐 menu, or a pseudo-locale (ar-XB, en-XA) to find hard-coded strings and mirroring bugs. The adb way is adb shell cmd locale set-device-locale ar-EG.

Pick a profile (LTE, HSDPA, 3G, EDGE, GPRS, GSM) from the network menu. The panel sets both speed and latency, the same as adb emu network speed edge and adb emu network delay edge.

Yes. ohmyandroid-mcp ships inside the app. Your agent can take screenshots in dp, read the UI tree, tap, type, switch dark mode, font size or RTL, and read logcat. See AI agents (MCP).

No. The server is one native binary with no runtime; Homebrew puts ohmyandroid-mcp on your PATH.

Not now. It is a native macOS app built with SwiftUI.

Mac App Store apps must run in the App Sandbox, and a sandboxed app cannot start adb. Homebrew and GitHub releases are signed and notarized by Apple instead.

The panel uses Liquid Glass and other APIs that are new in macOS 26 Tahoe.

Build from source

brew install xcodegen
git clone https://github.com/ateymoori/oh-my-android.git && cd oh-my-android
xcodegen generate
open OhMyAndroid.xcodeproj

Needs Xcode 26. Local builds are ad-hoc signed, so you need no Apple Developer account.

Sources/
  App/        entry point, AppDelegate (host actions), Settings, assets
  Core/       no UI, no feature knowledge
    Shell/    ShellRunning: non-blocking Process runner, stopped on timeout or cancellation
    Android/  AndroidSDK, ADBClient, DeviceTracker (adb track-devices), UI hierarchy, app data
    SQLite/, Imaging/
  Features/   one small type per capability, registered in FeatureCatalog (Foundation only)
  MCP/        ohmyandroid-mcp: stdio MCP server built on Core and Features, shipped inside the app
  State/      AppModel (composition root), DeviceStore, FeatureStore, inspector stores
  Windows/    FloatingPanel, emulator window docking, tool windows
  UI/         SwiftUI; FeatureCell renders any feature from its protocol

Dependencies point one way: UI → State → Features → Core. Features talk to the device through the ADBClient protocol and to the Mac through HostActions (file picker, clipboard, Finder), so each one is a small value type. Swift 6 language mode, strict concurrency, zero warnings.

Energy: nothing polls. Device changes come from adb's track-devices stream. Feature values are read in one batched adb shell call when you select a device, after an action, and when the pointer comes back to the panel. Docking uses a 1 Hz timer only while an emulator runs and the panel is visible.

The app and menu bar icons are drawn in code: Scripts/make-icon.swift.

Roadmap

• Compare mode: two devices side by side, mirrored input, pixel diff
• The emulator screen embedded in the panel window
• DataStore (.preferences_pb) support in the Data Inspector
• MCP: start and stop emulators, record the screen

Have an idea? Open a feature request. Adding a feature is one small Swift struct: see CONTRIBUTING.md.

License

MIT © 2026 Royan AB.

Android is a trademark of Google LLC. Oh My Android is not affiliated with or endorsed by Google. The Android robot is reproduced or modified from work created and shared by Google and used according to terms described in the Creative Commons 3.0 Attribution License.