brickproof-adb MCP server

brickproof-adb

Let an AI assistant look after your own Android devices — TV boxes first, phones and tablets too — over ADB, without bricking them.

brickproof-adb is an MCP server. It gives Claude (or any MCP client) the screen, the input and the package manager of your devices, and puts guard rails where a careless call would hurt: every package change is a dry run first, the packages a device cannot live without are read off the device and refused, a package that serves something on your network right now is not touched, and everything applied goes into a snapshot that one call rolls back.

It runs on Windows, macOS and Linux, in Docker, and as a Home Assistant app; devices connect over USB or the network.

What it looks like

Finding the TV.

You: Find my TV.

Claude calls adb_devices discover=true. Nothing is connected yet; the search looks for devices that announce debugging and for port 5555 on the home network:

Found:

192.0.2.50:5555 (port 5555 open, network debugging) - adb_connect host=192.0.2.50:5555; if this computer is new to the device, it asks on its screen to allow debugging

Claude: I found one device at 192.0.2.50. Shall I connect? The TV will ask whether to allow debugging.

You: Yes.

Claude calls adb_connect host=192.0.2.50:5555; you confirm the prompt to allow debugging on the TV screen, with "Always allow" checked. The address is remembered and connected again whenever the server starts.

Installing what you just downloaded.

You: Install on the TV the app I just downloaded.

Claude calls adbinstall without a path and gets the newest installable files of your Downloads folder, then adbinstall with the first one: a report of what would be installed on which device. After your yes, the same call with dry_run=false installs it.

Cleaning up a TV box.

You: The box is slow. Turn off the preinstalled junk, but nothing it needs.

Claude calls adbapp action=list filter=system, picks five packages and calls adbapp action=disable with them. That is a dry run by default: the plan comes back with the rollback path of each package — and one package refused, because the box uses it as its launcher:

REFUSED: the list contains protected packages - com.example.launcher.

com.example.launcher — launcher, roles (HOME)

The full set with every source: adb_app action=protected

Nothing was applied. Remove them from the list by hand; the tool has no override.

Claude drops it, runs the plan for the other four, then repeats it with dry_run=false. The account count and the launcher are checked after the batch, and the four packages are recorded in the snapshot.

You: The voice remote stopped working.

Claude calls adbapp action=restore, reads the plan and repeats it with dryrun=false: the four packages are enabled again in one call.

Seeing the screen and tapping.

You: Open the network settings on the phone.

Claude calls adb_screenshot, gets the picture and the line under it:

screen 1080x2340 -> image 473x1024 · scale 2.283/2.285 · pass coords="screenshot" to adbtap/adbswipe

and taps the "Network & internet" row it sees, with adbtap coords="screenshot", in the image's own coordinates. On a TV box without a touchscreen it uses adbfindandtap text="Network", which walks the focus there with the remote's keys.

Install it where your AI is

Details, other setups and checks: docs/installation.md. An AI app without MCP support cannot use this server.

Shortened. The full README is on GitHub.