Android ADB Control

    1

    Debug and inspect a connected Android device over ADB: logcat, UI hierarchy, packages, and safe read-only shell commands.

    Free

    1 useSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Android ADB Control

    Example session with this skill installed

    My Android app crashes right after launch. Dump the last 200 logcat lines filtered to errors, then show me the current UI hierarchy so I can see which screen is up.

    • Read your context and instructions
    • Compiled the android adb control

    Logcat (last 200 lines, level E)

    E AndroidRuntime: FATAL EXCEPTION: main
    E AndroidRuntime: Process: com.example.demo, PID: 12345
    E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method
    E AndroidRuntime:     'java.lang.String com.example.demo.User.getName()' on a null object reference
    E AndroidRuntime:     at com.example.demo.ProfileActivity.onCreate(ProfileActivity.java:42)
    

    UI hierarchy (current screen)

    <hierarchy rotation="0">
      <node class="android.widget.FrameLayout" bounds="[0,0][1080,1920]">
        <node class="android.widget.TextView" text="Profile" bounds="[40,120][300,180]" />
        <node class="android.widget.EditText" text="" hint="Name" bounds="[40,240][1040,320]" />
      </node>
    </hierarchy>
    

    What I found

    • Crash: NullPointerException in ProfileActivity.onCreate (line 42) — a User.getName() call on a null object.
    • Screen: ProfileActivity is the visible screen; the "Name" field is empty when the crash triggers.

    Next steps

    1. Guard the User object in ProfileActivity.onCreate before calling getName().
    2. Reproduce and re-check with a fresh logcat capture (adb_clear_logcat then trigger the flow again).
    3. Use adb_dump_hierarchy after the fix to confirm the screen renders.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Inspect and debug a connected Android device or emulator directly from your AI agent, through the free open-source Android MCP server (@neem2004/android-mcp-server).

    What it does

    • Reads the logcat buffer, with optional line, tag and level filters
    • Clears the log buffer before a clean capture
    • Dumps the current UI hierarchy (XML) to understand the visible screen
    • Lists installed packages, filtered or including system apps
    • Runs safe, read-only shell commands allowlisted to getprop, dumpsys and pm list

    Why it is safe

    Commands run via execFile with no intermediate shell; command chaining (&&, ||, ;, |) and injection metacharacters are rejected, and no root is requested.

    Requirements

    Add the MCP server to your agent (npx -y @neem2004/android-mcp-server), have Node.js 18+, and connect a device with USB debugging enabled (adb devices shows device).

    Requires @neem2004/android-mcp-server setup. Read-only shell access restricted to getprop, dumpsys, and pm list. No support for shell command chaining or write operations.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    • Free with an Agensi account

    Requires

    GitHub
    Android
    @neem2004/android-mcp-server
    Node.js 18+
    Android platform-tools (adb)
    Node.js
    macOS

    Permissions

    Network Access

    Allowed Hosts

    github.com
    developer.android.com

    File Scopes

    android-adb/**
    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This skill eliminates the need to manually run terminal commands and parse raw logs. It allows your AI agent to instantly retrieve filtered stack traces, inspect UI hierarchies, and query system properties directly within your workflow.

    It requires the `@neem2004/android-mcp-server` to be configured in your MCP-compatible client. You must also have the Android Debug Bridge (ADB) installed and a device or emulator connected with USB debugging enabled.

    For security, the skill is restricted to read-only diagnostic commands like `logcat`, `dumpsys`, and `getprop`. It cannot perform write operations, install new APKs, or execute unauthorized shell scripts.

    Yes, you can target specific diagnostic data by providing package names, log tags, or search strings. This ensures the AI agent only analyzes the logs and UI elements relevant to the specific bug you are investigating.

    The skill works with any AI agent or platform that supports the Model Context Protocol (MCP). As long as your client is connected to the Android MCP server, the agent can call these debugging tools.

    New in Mobile Development