Each case says what you have in front of you, what you do, and which part of the app does it.
You built half a set years ago and do not know what is missing.
Open the copy and run Set Inspector against its inventory. The shortfall becomes a list you can act on, with a count of how far along the copy is.
Boxes of sorted loose parts, and several unfinished sets.
Part Runner lists the missing parts you can pull for the sets you tick, in your sort order, so one pass through the drawers serves many sets. Matchmaker shows which copies your stock finishes outright.
A BrickLink order arrives.
Import it from your account, paste the confirmation email or upload the order XML; a line already imported is never added twice. Count what comes out of the bag and allocate it to the sets that need it.
Several sets are short. Which are worth finishing?
Wishlist, Prices and Complete sets rank repairs by value gained per euro. Part-out values show only when at least 90% of a set’s lines have a price; one action fetches the missing prices.
A set is broken down into bags. Which box is it in?
Every set, copy, part and box has a storage location. Look up a part and see how many you have and where they are.
$ brickwork import-bricktracker old/app.db --plan-only Read-only import Plan and summary first Old database unchanged
Your collection lives in another tracker.
Run the read-only importer on the old tracker database, review the plan and what it leaves out, then apply it. One import is one event that Undo takes back. The old database is never changed.
You want an answer without opening the app.
Connect an assistant over MCP and ask which sets are closest to complete or what is stored in a box. It reads with a read-only token; write tools stay off unless you enable them, and every change gets an Undo link.
$ docker compose exec brickwork \
brickwork token create \
--name export --scope read
You want a spreadsheet export, or sets added from a script.
Hook the collection into your own tools with the versioned REST API. Creates need an idempotency key, so a retried request cannot add twice.