android-app-debug-mcp

Drive an Android emulator from your LLM. Build, install, launch, and test a feature end-to-end — get a unified logcat-and-actions timeline back.

---

android-app-debug-mcp is a Model Context Protocol server that turns one structured test task ("verify the login screen rejects an empty password") into one auditable debug run — APK built, AVD booted, app launched, UI driven through adb, logcat captured, screenshots saved, verdict written.

Every UI action lands as a typed MCP tool call, so the entire decision trail is visible in your LLM client's chat history and reproducible from trace.jsonl and logcat.log on disk.

Highlights

• Build → boot → launch → drive → verdict, in one session. Gradle, AVD, install, launch, logcat, and the Marvis UI-tree parser are all orchestrated behind a single start_debug_session call.
• Unified timeline. Every action writes an inline <<< MARVIS_DEV ... >>> marker into the live logcat stream, so cause and effect sit next to each other in timeline.md.
• Auditable by default. Every captured frame, every action, and every UX observation lands under <project_root>/android-app-debug/<timestamp>/.

Install

As a Claude Code plugin (recommended)

# Inside Claude Code:
/plugin marketplace add /path/to/android-app-debug-mcp
/plugin install android-app-debug-mcp@FCLab.SKKU

The bundled plugin manifest registers the MCP server automatically via ${CLAUDE_PLUGIN_ROOT}/scripts/server.py.

As a standalone MCP server

claude mcp add marvis-dev -- uv run --project /absolute/path/to/android-app-debug-mcp python /absolute/path/to/android-app-debug-mcp/scripts/server.py

Or copy .mcp.json.example to .mcp.json in your project root and edit the path.

Prerequisites

• on — manages Python and dependencies automatically ( or ).