BricksID
BricksID connects Claude to your BricksID account so you can identify LEGO items and keep track of what you own. Identify: send a photo of a minifig, set, or part and get ranked candidates with a confidence level (high, medium, or low) plus BrickLink IDs and prices when the catalog has them. Photos are not attached in chat. Claude creates a short-lived upload link you open on your phone or computer, then identifies the image you took. You can also pass a public image URL. Collection: list and query your collection, add items with condition, quantity, and what you paid, edit them, and remove them. Removed items stay recoverable on the BricksID inventory page for 30 days. Collector and Pro plans add a collection summary (counts, estimated value, breakdowns by theme, year, and condition) and structured queries. Export and sell: Collector and Pro plans can download the collection as CSV, Excel, or JSON. Pro plans can build a Whatnot Seller Hub CSV and mark items as uploaded. BricksID does not call Whatnot for you. Plans and limits: free accounts get a daily scan allowance and store 50 items. Collector and Pro raise the scan limit and collection size. Call get_account to see your tier, remaining scans, and collection cap. Sign in with your BricksID account (Google, Apple, or email) when Claude asks. Access uses OAuth, and you choose which permissions to allow. Identifications suggest the right item. Confirm the BrickLink ID when it matters.
Connection details
13 tool names reported
Source-declared tools. Availability can depend on the connection and permissions; these are not runtime test results.
Claude connector directory ↗ · Observed 2026-11-01 · Completeness not established
add_to_collectioncollection_summaryconfirm_uploadedcreate_upload_linkexport_collectionexport_whatnot_csvget_accountget_upload_statusidentify_itemlist_collectionquery_collectionremove_collection_itemupdate_collection_item
Sources and provenance
- Claude connector directoryClaude tier: community · Observed
Grouping basis: endpoint. Exact endpoints or package sets can be grouped automatically; other relationships require evidence review. This does not verify publisher affiliation, connection health, or equivalent capabilities.