adb

This MCP server exposes a suite of Android Debug Bridge (ADB) tools through the MCP interface, enabling AI models to manage devices, install apps, capture logs, transfer files, and interact with the UI. The server starts with npx adb-mcp and registers a set of commands such as adb_devices, adb_shell, adb_install, adb_logcat, adb_pull, adb_push, adb_dump_image, and adb_inspect_ui. To use these tools, ensure your host machine has ADB installed and at least one device or emulator connected and authorized. The server acts as a bridge, converting model prompts into ADB commands and returning results that can be interpreted by your MCP client. This makes it possible to automate device testing, app deployment, and UI analysis directly from an AI workflow.

Prerequisites:\n- Node.js (v16+ recommended).\n- npm (installed with Node.js).\n- ADB installed and in PATH.\n- A device or emulator connected with USB debugging enabled.\n\n1) Manual installation:\nbash\n# Clone the repository (or install via npm if available in your setup)\ngit clone https://github.com/srmorete/adb-mcp.git\ncd adb-mcp\n\n# Install dependencies\nnpm install\n\n# Build TypeScript sources (if the project uses TS)\nnpm run build\n\n# Run the server locally (using npx as described in the MCP docs)\nnpx adb-mcp\n\n\n2) Optional Smithery installation (automated):\nbash\n# Install via Smithery to be used with Claude Desktop (example)\nnpx -y @smithery/cli install @srmorete/adb-mcp --client claude\n\n\n3) Quick start after installation:\nbash\n# Start the MCP server for adb\nnpx adb-mcp\n\n\nNotes:\n- If you need to use a non-default adb path, export ADB_PATH before starting the server:\nbash\nexport ADB_PATH=/path/to/adb\nnpx adb-mcp\n

Tips and common issues:\n- Ensure ADB is accessible in your PATH or set ADB_PATH to the exact executable.\n- If a device shows as unauthorized, re-check the prompt on the device to authorize debugging.\n- Use LOG_LEVEL=3 npx adb-mcp for verbose logs during debugging.\n- If commands fail, verify the server is running and that the device is connected with adb devices.\n- This MCP supports a broad range of ADB operations (shell, install, package manager, activity manager, logcat, pull/push, screenshot, and UI inspection).\n- For production usage, consider pinning versions of adb-mcp and ADB tools to avoid breaking changes.\n- On Windows, you may need to ensure a compatible shell environment; the project targets POSIX-compatible environments, so WSL or similar is recommended for Windows users.\n- Review the MCP client documentation to understand the exact invocation format for each tool (e.g., adb_shell, adb_install, adb_logcat).