brickproof-adb MCP Server

What the code does

We read the source, 1 d ago · rules 995398eba69f

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

      if (tmp && tmp.dir) fs.rmSync(tmp.dir, { recursive: true, force: true });

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    execFile(bin, ['version'], { timeout, windowsHide: true }, (err, stdout) => {

      const out = path.join(dir, file);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add brickproof-adb -- npx -y brickproof-adb

{
  "mcpServers": {
    "brickproof-adb": {
      "command": "npx",
      "args": [
        "-y",
        "brickproof-adb"
      ]
    }
  }
}

[mcp_servers.brickproof-adb]
command = "npx"
args = ["-y", "brickproof-adb"]

{
  "mcpServers": {
    "brickproof-adb": {
      "command": "npx",
      "args": [
        "-y",
        "brickproof-adb"
      ]
    }
  }
}

{
  "servers": {
    "brickproof-adb": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "brickproof-adb"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: BRICKPROOF_ADB (Path of the adb executable; optional, default adb on PATH), BRICKPROOF_FILE_ROOTS (Host directories adb_push, adb_pull and adb_install may use, separated by ; on Windows and : elsewhere; optional), BRICKPROOF_CONFIG (Path of the JSON config file; optional).