Android
Let your coding agent drive real Android devices and emulators through ADB for screenshots, UI taps, and logcat while you build or debug mobile apps.
Overview
io.github.martingeidobler/android is a MCP server for the Build phase that controls Android devices and emulators via ADB for screenshots, UI automation, and logcat.
What is this MCP server?
- ADB-backed control of physical devices and emulators from the agent
- Capture screenshots for visual regression or bug reports
- UI automation for flows your agent cannot reach in a browser alone
- Stream or query logcat for crash and ANR diagnosis
- stdio npm package android-mcp-server v1.2.1 with ANDROID_HOME env (auto-detected on macOS at ~/Library/Android/sdk)
- Server schema version 2025-12-11; package version 1.2.1
- Transport: stdio via npm identifier android-mcp-server
- Documented capabilities: screenshots, UI automation, logcat via ADB
What problem does it solve?
Solo mobile builders waste time alt-tabbing between the agent, terminal ADB commands, and emulators when reproducing bugs or capturing device state.
Who is it for?
Indie developers and small teams building Android apps who already have the SDK and want agent-driven device debugging during feature work.
Skip if: Teams that only ship iOS or web, or anyone who needs cloud device farms and parallel matrix testing without local ADB.
What do I get? / Deliverables
Your agent can run ADB operations from one session so device screenshots, taps, and logs land in the same thread as your code changes.
- Device or emulator screenshots attached to agent conversations
- Executed UI automation sequences and readable logcat excerpts for diagnosis
Recommended MCP Servers
Journey fit
Device control and automation sit in Build because they support implementation and verification of mobile products, not launch distribution or production monitoring. Integrations is the right shelf: this MCP wires your agent to the Android SDK/ADB toolchain alongside your repo and CI, not to storefront SEO or analytics.
How it compares
MCP integration for local ADB device control, not a hosted mobile test grid or a Play Store launch skill.
Common Questions / FAQ
Who is io.github.martingeidobler/android for?
Solo and indie builders using AI coding agents to develop Android apps who want screenshots, UI steps, and logcat from real devices or emulators without manual ADB typing.
When should I use io.github.martingeidobler/android?
Use it during Build when you are implementing or fixing mobile UI, verifying flows on emulator or hardware, or pulling logcat after a crash while iterating with your agent.
How do I add io.github.martingeidobler/android to my agent?
Add the npm stdio package android-mcp-server (v1.2.1) in your MCP config, set ANDROID_HOME to your Android SDK path if auto-detect fails, ensure adb is on PATH, then restart Claude Code or Cursor.