Maintain your own Android devices and TV boxes over ADB with dry runs, guards and rollback
Connect Runs on your machine
claude mcp add brickproof-adb -e BRICKPROOF_ADB=<BRICKPROOF_ADB> -e BRICKPROOF_FILE_ROOTS=<BRICKPROOF_FILE_ROOTS> -e BRICKPROOF_CONFIG=<BRICKPROOF_CONFIG> -- npx -y [email protected]{
"mcpServers": {
"brickproof-adb": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"BRICKPROOF_ADB": "<BRICKPROOF_ADB>",
"BRICKPROOF_FILE_ROOTS": "<BRICKPROOF_FILE_ROOTS>",
"BRICKPROOF_CONFIG": "<BRICKPROOF_CONFIG>"
}
}
}
}{
"mcpServers": {
"brickproof-adb": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"BRICKPROOF_ADB": "<BRICKPROOF_ADB>",
"BRICKPROOF_FILE_ROOTS": "<BRICKPROOF_FILE_ROOTS>",
"BRICKPROOF_CONFIG": "<BRICKPROOF_CONFIG>"
}
}
}
}{
"servers": {
"brickproof-adb": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"BRICKPROOF_ADB": "<BRICKPROOF_ADB>",
"BRICKPROOF_FILE_ROOTS": "<BRICKPROOF_FILE_ROOTS>",
"BRICKPROOF_CONFIG": "<BRICKPROOF_CONFIG>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
BRICKPROOF_ADBOptional | Path of the adb executable; optional, default adb on PATH |
BRICKPROOF_FILE_ROOTSOptional | Host directories adb_push, adb_pull and adb_install may use, separated by ; on Windows and : elsewhere; optional |
BRICKPROOF_CONFIGOptional | Path of the JSON config file; optional |
Details
| Package | [email protected] (NPM, stdio) |
| First published | 21 Oct 2026 |
| Last updated | 21 Oct 2026 |
| Registry name | io.github.st412m/brickproof-adb |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.