Devilge MCP Server

What the code does

We read the source, 20 h ago · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

      const child = spawn(this.adbPath, [...args], {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add devilge -- npx -y devilge

{
  "mcpServers": {
    "devilge": {
      "args": [
        "-y",
        "devilge"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.devilge]
command = "npx"
args = ["-y", "devilge"]

{
  "mcpServers": {
    "devilge": {
      "args": [
        "-y",
        "devilge"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "devilge": {
      "args": [
        "-y",
        "devilge"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: DEVILGE_ANDROID_PROJECT_ROOT (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 <projectRoot>/.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 <projectRoot>/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'.). The author declared them in the registry entry; get the values from the project itself.