Assetlib

Assetlib updates a mobile app's images without an app release. An engineer integrates the Assetlib SDK and ships one app release; after that, compatible images in the placements the app declares are published through signed releases, and the app keeps bundled fallbacks that always render. This connector links Claude to one Assetlib workspace (one app). Claude can: - read each placement (key, screen, aspect ratio, states, light and dark variants) and the image it shows in draft, staging and production, with code references and small previews; - read the image library, release history, setup progress and the SDK setup steps; - with your permission, assign library images to placements as a draft or clear a draft assignment, and create a one-time upload link for a new image file, then give you the console link to review the draft. It cannot publish, promote, restore, approve releases, archive or delete images, create placements, or change members, tokens or settings. Publishing stays with a person in the Assetlib console. Placements come from the app's repository (assetlib.catalog.json, registered by assetlib sync in CI), not from this connector. You sign in with your Assetlib account (GitHub) and choose the workspace and whether Claude may draft changes. Disconnect it any time in the console under Settings › Profile › Agent connections. Reading a workspace is free; uploads count toward the workspace's storage. Assetlib is a developer preview.