Devilge MCP Server

Devilge is an MCP integration. Android/KMM MCP server: logcat, ADB device control, Compose previews, network, Maestro flows.

Packages and local setup

The published npm package is devilge, version 0.2.3. Its declared MCP transport is stdio.

The package declares DEVILGE_ANDROID_PROJECT_ROOT (required): Absolute path to the Android/KMM project root that devilge inspects (Gradle modules, source files, build outputs).; DEVILGE_OUTPUTS_ROOT: Directory where devilge writes screenshots and UI dumps. Defaults to /.devilge-outputs/.; DEVILGE_DEFAULT_DEVICE_SERIAL: Default ADB serial used when a tool does not specify one. Useful when several devices/emulators are attached.; DEVILGE_FLOWS_ROOT: Directory containing Maestro YAML flows. Defaults to /devilge-flows/.; DEVILGE_MAESTRO_BIN_PATH: Absolute path to the Maestro binary. If unset, devilge resolves it from PATH; if absent, Maestro tools degrade gracefully.; DEVILGE_ALLOW_FLOW_SCRIPTS: Set to 'true' to allow Maestro flows containing 'runScript:' blocks. Default is false; flows with scripts are rejected.; DEVILGE_HTTP_LOG_TAGS: Comma-separated logcat tags scanned for HTTP traffic. Defaults to 'HttpClient,OkHttp' (covers Ktor + OkHttp/Retrofit).; DEVILGE_HTTP_LOG_FORMAT: HTTP log parser to use: 'auto' (default), 'ktor', or 'okhttp'..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.2.3 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.