Devilge
Let your coding agent drive Android/KMM debugging, device control, Compose previews, and Maestro UI flows from one MCP server.
Overview
devilge is a MCP server for the Build phase that connects coding agents to Android/KMM projects via ADB, logcat, Compose previews, network tools, and Maestro flows.
What is this MCP server?
- stdio npm package devilge v0.2.3 with project-root–scoped Gradle/Android inspection
- ADB device control, logcat streaming, and optional default serial when multiple devices are attached
- Jetpack Compose preview assistance and network debugging from the agent
- Maestro YAML flow execution with configurable flows root and Maestro binary path
- Screenshots and UI dumps written under DEVILGE_OUTPUTS_ROOT (default .devilge-outputs/)
- Server version 0.2.3
- Transport: stdio
- Registry: npm identifier devilge
What problem does it solve?
Debugging Android and KMM from an AI agent usually means copy-pasting logcat, juggling ADB shells, and manually running Maestro—slow when you ship alone.
Who is it for?
Indie mobile developers using Claude Code or Cursor who want agent-driven logcat, device ops, and Maestro checks on a real Gradle tree.
Skip if: Teams building only web or iOS-native (non-KMM) apps with no Android toolchain, or anyone unwilling to expose a full project path to an MCP process.
What do I get? / Deliverables
After registering devilge, your agent can inspect the project, control devices, capture UI state, and run Maestro flows from standardized MCP tools.
- Agent-callable device control, logcat, and network inspection against your project
- Screenshots and UI dumps under configured outputs directory
- Executed Maestro flows from devilge-flows or DEVILGE_FLOWS_ROOT
Recommended MCP Servers
Journey fit
Mobile product work happens in Build when you wire agent tooling to Gradle modules, emulators, and on-device verification—not during launch or growth. Integrations is the right shelf because devilge bridges Claude/Cursor to ADB, logcat, network capture, and Maestro—not app feature code itself.
How it compares
Android dev integration MCP (ADB + Maestro), not a generic browser automation or Play Store listing skill.
Common Questions / FAQ
Who is devilge for?
Solo and small-team Android/KMM builders who use MCP-enabled agents and want first-class device, log, and UI-flow tooling without writing custom scripts.
When should I use devilge?
Use it during active Build work when you need reproducible agent access to logcat, emulators, Compose previews, network traces, or Maestro YAML on your repo.
How do I add devilge to my agent?
Install the npm package devilge, set DEVILGE_ANDROID_PROJECT_ROOT to your project, configure optional ADB/Maestro paths, and register the stdio MCP server in Claude Code, Cursor, or Windsurf.