check-adb-speedLABSCO SUMMARY
The ADB commands you look up every time, as tools.
Uninstall, clear data, force-stop and the immersive flag are the operations a developer runs constantly and remembers the syntax for never — and the speed check settles whether the cable is the reason a deploy takes two minutes.
What it is
The MCP server built into the ADB Friend CLI, shipped with its recent releases. It drives a device over ADB — package management, per-package state and a transfer speed check — through the same adb connection you would use by hand.
What you get
- Connected devices listed, so the right one is targeted when more than one is attached
- Installed packages listed, and packages uninstalled by name
- App data and cache cleared for an installed package
- A running process force-stopped
- The immersive full-screen flag applied to a package
- ADB transfer speed measured, which is how a sub-par cable gets identified rather than suspected
Requirements
Install with Homebrew from mikepenz/tap, or take a prebuilt binary; the server runs as adbfriend mcp server. ANDROID_HOME has to be in the environment, or the adb server started manually first — without either, the connection throws. And an Android device attached over ADB.
Setup effort
One command — brew install mikepenz/tap/adbfriend
USE CASES
01
Resetting an app to a clean state before a test
Clear its data and cache, then force-stop it, so the next launch is a first launch.
02
Clearing test builds off a device
List what is installed, and uninstall the ones that should not still be there.
03
Working out which device you are talking to
List the connected devices first — the check that stops a command landing on the wrong handset.
04
Finding out whether the cable is the problem
Measure ADB transfer speed instead of guessing why a deploy crawls.
05
Setting a device up for a demo
Apply the immersive flag to the package so the system bars stay out of the way.
19 tools
Listed in project docs. Your client may show a different list.
clear-installed-packageset-immersive-full-for-packageforce-stop-processuninstall-packageget-connected-devicesget-installed-packageslist_allowed_directorieslist-filesread-fileread_multiple_fileswrite-filecreate-directorydeletesearch-filesmove_filecopy-file-to-hostcapture-screenshotinstall-apkBEFORE YOU INSTALL
What to know first
Tools you get
19 tools named in the project's documentation.
INSTALLATION
Connect your client
Server setup
TERMINAL
brew install mikepenz/tap/adbfriendMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"adb-friend": {
"command": "/opt/homebrew/bin/adbfriend",
"args": [
"mcp",
"server"
],
"env": {
"ANDROID_HOME": "<YOUR_ANDROID_HOME>"
}
}
}
}Set ANDROID_HOME to the folder of your Android SDK. If you leave it out, the adb server has to be started by hand before the client launches this one — otherwise the connection throws.
Debug with MCP Inspector (SSE)
DEBUG WITH MCP INSPECTOR (SSE) · TERMINAL
adbfriend mcp server --sse true
