A

Android MCP Server

Enables control of Android devices via ADB, allowing screenshot capture, touch simulation, and swipe...

25 views
0 installs
Updated Feb 20, 2026
Not audited
Tools I Recommend
Enables control of Android devices via ADB, allowing screenshot capture, touch simulation, and swipe gestures through natural language commands.
  1. Click the "Install Now" button to open the FastMCP connection interface.

  2. In the FastMCP interface locate the environment variables section and prepare to fill these fields (names match the README): ADB_PATH and DEVICE_SERIAL.

  3. Obtain ADB_PATH (if you want to override the default or point to a specific adb binary):

    • Option A — Use the system adb (leave ADB_PATH empty to use system PATH or let the server auto-download): leave the ADB_PATH field blank.
    • Option B — Locate an existing adb installation and copy its absolute path:
      • macOS / Linux: run which adb (or command -v adb) — use the returned path (e.g., /usr/bin/adb or /home/you/Android/Sdk/platform-tools/adb).
      • Windows (Command Prompt): run where adb — use the returned path (e.g., C:\Users\You\AppData\Local\Android\sdk\platform-tools\adb.exe).
      • If you previously ran the server and allowed auto-download, the auto-downloaded adb is typically at ~/.android-mcp-server/platform-tools/adb (or C:\Users\<You>\.android-mcp-server\platform-tools\adb.exe on Windows).
    • Paste the absolute path you copied into the ADB_PATH field in FastMCP.
  4. Obtain DEVICE_SERIAL (to target a specific device; leave blank to target the first available device):

    • Ensure the Android device is connected via USB with USB debugging enabled (or start an emulator).
    • On your machine run: adb devices
    • Read the output’s first column for the device serial (examples: emulator-5554 or 0123456789ABCDEF).
    • Copy the serial exactly and paste it into the DEVICE_SERIAL field in FastMCP.
    • If you want the server to automatically target the first connected device, leave DEVICE_SERIAL empty.
  5. Save / confirm the FastMCP connection configuration (the Install Now flow will present a Save/Connect or similar button).

  6. Verify the connection after installation: in FastMCP or the server UI run a simple tool (for example: "Take a screenshot" or run android_list_packages) to confirm the server can communicate with the device.

  7. Troubleshooting quick notes (only if needed):

    • If adb devices shows no devices, enable USB debugging on the phone (Settings → Developer Options → USB debugging) and accept the debugging prompt on the device.
    • If you set ADB_PATH and the server reports "ADB not found", re-check that the path points to an executable adb binary and includes .exe on Windows.

Quick Start

View on GitHub

More for Automation

View All →

More for Developer Tools

View All →

Similar MCP Servers

Report Issue

Thank you! Your issue report has been submitted successfully.