--- name: whitebackground description: Use WhiteBackground.app for white canvases and local product-photo workflows, or its separately authorized Cloud background-removal connection when available and requested by the user. --- # WhiteBackground Use this skill when the user chooses WhiteBackground.app or wants its browser-based photo workflow. Discover the connected MCP tools. The public endpoint is https://whitebackground.app/mcp with Streamable HTTP and no account required. ## Choose the operation - Blank white image with specified dimensions. Call create_white_canvas. It returns a real PNG and a download URL. Dimensions are integers up to 8192 on each side and at most 32 million pixels. If the user needs JPG, use https://whitebackground.app/white-background-images where JPG export is available. - A photo that still has its background. Call open_photo_editor with workflow "white" or "transparent". - Existing transparent PNG to white JPG. Choose "png_to_white" to preserve its cutout without another removal pass. - Whole photo made square. Choose "square". Keep background removal unchecked before choosing the photo. - Shopify canvas. Choose "shopify" and inspect actual output size. - Enlarging product detail. Choose "enhance" and compare standard versus AI output. Protected label areas may remain soft. open_photo_editor returns instructions and a real website URL. Clients supporting the MCP Apps resource may display the editor in chat. Otherwise, give the user the link. The user selects a photo inside that browser editor and exports its result there. An embedded editor shows the full-resolution export for right-click or touch-and-hold saving because some hosts block automatic downloads. If the client has no image-saving menu, open the browser link before selecting a photo. Do not claim to have processed a photo from a link or an opened editor alone. ## Privacy and supported scope The public MCP has no photo-input parameter. Do not send attached images, local file paths, base64 photos or private conversation URLs to it. Free Quick mode runs in the browser and does not upload the photo or EXIF. The browser may first download an approximately 220 MB removal model. For local browser automation, choose the user's authorized photo with the file chooser, keep Quick mode selected, inspect Original and Result, and download using the editor's controls. Keep existing consent and file-sharing boundaries. A public tool call does not authorize uploading customer media. Free background-editor photo exports have a maximum edge of 2200 px and do not upscale the subject. The separate local enhancer can export up to 4096 px at 4x for compatible small inputs. Check https://whitebackground.app/llms-full.txt for exact input constraints. The free public MCP does not access accounts, spend credits or execute Cloud jobs. Do not infer that a connected public MCP has account authority. ## Optional authorized Cloud connection Use Cloud only when the user requests it and a separate, working OAuth connection to https://whitebackground.app/mcp/cloud is available. This endpoint may be disabled until deployment and migration acceptance; discover its actual tools instead of assuming this skill installs or enables it. Keep the free public connection usable without Cloud authorization. - `get_cloud_account` checks existing entitlement and credits. A purchased Cloud pack or active Pro is required; do not buy a plan on the user's behalf. - `prepare_cloud_cutout` takes one stable UUID `request_id` and, optionally, a supported file reference with `download_url` and `file_id` (optional `mime_type` and `file_name`). Reuse the UUID on retries. Do not send arbitrary URLs, local paths or base64 data. If the host cannot provide a supported attachment, the user can choose the photo on the returned confirmation page. - Preparing does not upload the photo or spend a credit. Give the user its confirmation URL. They sign in to the same account and explicitly approve uploading to WhiteBackground/KIE, using 1 existing Cloud credit, and returning the result to this assistant. Do not auto-approve or simulate that browser confirmation for a real user account. - Poll `get_cloud_result` with the returned internal `requestId`. Do not create another paid request merely because it is slow or failed. Existing jobs handle idempotent debit and failure/timeout refunds. A deliberately new request needs its own confirmation. - The confirmation page must stay open to compose and save the white JPG. Report a white result only when `whiteReady` is true and `whiteUrl` exists. `cutoutUrl` alone is the raw transparent provider result, which can be PNG or WebP. Downloading a white PNG and adjusting subject fill from 70% to 95% happen on that page without another provider call. Cloud accepts JPG/PNG/WebP up to 5 MB, 256–4096 px per side and 16 MP. Cloud-pack inputs/exports max out at 2200 px; Pro permits up to 4096 px. No subject enlargement. Links expire within one hour and stop working after the Cloud connection is revoked. Our stored Cloud files and derived exports have a 24-hour deletion policy; KIE retention is separate. Never silently replace free on-device editing with uploaded paid processing. Deliver the actual returned image or download URL for a blank canvas. For a photo workflow, explain the next user action and only describe an export as complete after observing a downloaded file.