This MCP server provides tools for interacting with Android devices through the Android Debug Bridge (ADB). It enables AI assistants to perform
This MCP server provides tools for interacting with Android devices through the Android Debug Bridge (ADB). It enables AI assistants to perform common Android development and testing operations. Exposed over MCP by the android mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
A Model Context Protocol (MCP) server that enables AI assistants to interact with Android devices through the Android Debug Bridge (ADB). This server bridges the gap between AI capabilities and Android device management, allowing for seamless automation of Android development and testing operations.
Everything the assistant can do here goes through one of these:
adb_devices — List connected devicesadb_shell — Execute shell commandsadb_install — Install APK filesadb_uninstall — Uninstall applicationsadb_list_packages — List installed packagesadb_pull — Pull files from deviceadb_push — Push files to devicelaunch_app — Launch an applicationtake_screenshot_and_save — Take and save screenshottake_screenshot_and_copy_to_clipboard — Take screenshot to clipboard@landicefu/android-adb-mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Android's toolset — adb_devices, adb_shell, adb_install and 7 more — is a fair guide to whether it matches your workflow. It is maintained by landicefu; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| adb_devices | List connected devices |
| adb_shell | Execute shell commands |
| adb_install | Install APK files |
| adb_uninstall | Uninstall applications |
| adb_list_packages | List installed packages |
| adb_pull | Pull files from device |
| adb_push | Push files to device |
| launch_app | Launch an application |
| take_screenshot_and_save | Take and save screenshot |
| take_screenshot_and_copy_to_clipboard | Take screenshot to clipboard |
{
"mcpServers": {
"android-adb": {
"command": "npx",
"args": ["-y", "@landicefu/android-adb-mcp-server"],
"env": {},
"disabled": false,
"alwaysAllow": []
}
}
}Configuration as documented by the project. Restart the client after saving.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.