Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    ADB Pilot: Android Control for MCP Agents

    1

    Give your AI agent safe, structured control of Android devices and emulators over MCP — screenshots, logcat, installs, and UI taps behind approval gates.

    Free

    0 installsSecurity scanned
    ADB Pilot: Android Control for MCP Agents

    ADB Pilot: Android Control for MCP Agents

    Example session with this skill installed

    I'm building a mobile app and I want my agent to verify it on the emulator instead of me typing adb commands all day. Repo is at ~/projects/mobile-app, the debug build is /tmp/app-debug.apk, and emulator-5554 is running. Help me configure an ADB Pilot MCP server for Cursor using stdio transport, show which safety layers to enable before I expose shell access, then walk me through a crash-triage run: start com.acme.mobile, capture ten seconds of logcat, and summarize the failure.

    • Read your context and instructions
    • Compiled the adb pilot

    Summary

    ADB Pilot is now wired into Cursor over stdio with the approval-gating policy enabled. The crash-triage run on emulator-5554 reproduced the failure and pinpointed a null cart session in PaymentFragment.onResume().

    CheckBeforeAfter
    ADB accessmanual adb typingadb-pilot --transport stdio in mcp.json
    Device targetingguessed device namesserial emulator-5554 required per call
    Risk gatingnonereboot / uninstall / clear-data approval-gated
    Crash causeunknownNPE at PaymentFragment.kt:87, logged 14:32:07
    FATAL EXCEPTION: main
java.lang.NullPointerException: getSession(...) must not be null
  at com.acme.mobile.PaymentFragment.onResume(PaymentFragment.kt:87)

    Next steps

    • Guard CartRepository.session in onResume with a recreate-or-return path, then reinstall /tmp/app-debug.apk
    • Add the default denylist (/system, /vendor, su, raw pm writes) before enabling the shell tool
    • Re-run the UI smoke-test recipe to confirm the payment screen renders after the fix
    • Keep one clean emulator profile reserved for regression runs
    in mcp.json

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

    About this skill

    Controlling Android devices via AI agents often results in flaky execution or dangerous shell access. ADB Pilot provides a structured bridge using the Model Context Protocol (MCP) to give agents safe, granular control over physical devices and emulators. It replaces raw terminal commands with typed tools for UI automation, diagnostic retrieval, and app management.

    What it does

    • Device Management discovers connected hardware, identifies serials, and monitors connection health.
    • UI Automation executes precise taps, swipes, and text input using coordinate or hierarchy-based targeting.
    • Diagnostic Capture retrieves logcat streams, crash reports, ANR files, and memory dumps for triage.
    • App Operations handles APK installation, permission grants, and application lifecycle management.
    • File Transfer manages file round-trips between the host machine and device storage paths.
    • Visual Verification captures screenshots and screen recordings to verify agent actions.

    How it works

    1. Bridge Setup involves connecting a device via USB or TCP/IP and starting the MCP server on the host.
    2. Tool Invocation allows the agent to call specific functions like install_apk or tap_ui through the MCP client.
    3. Safety Gating enforces a risk-based approval model, requiring human confirmation for destructive actions like reboots or deletions.
    4. Result Normalization converts raw ADB output into structured JSON for the agent to process.

    Frameworks & tools

    This skill utilizes the Model Context Protocol (MCP), Android Debug Bridge (ADB), and Python. It supports local execution via stdio or remote access through SSE/HTTP transports.

    Why this beats prompting it yourself

    Writing raw ADB shell commands through an LLM is error-prone and lacks safety boundaries. This skill provides a schema-validated interface that prevents shell injection, enforces device targeting, and categorizes operations by risk level.

    Use cases

    • Automate UI smoke tests on physical devices during CI/CD cycles.
    • Triage application crashes by automatically pulling logs and screen states.
    • Manage large emulator fleets for parallel app testing and data collection.
    • Perform remote device surveys to verify hardware specs and battery health.

    Known limitations

    Requires ADB to be pre-installed and available on the system PATH. Containerized deployment requires complex host USB mapping. Destructive operations on system partitions are blocked by default.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 1 day ago

    • Free to download with an account

    Listed1 day ago

    What's inside

    Frequently Asked Questions