Product-image-to-ad concept pipelines with MCP

Start with a product truth set, not a generation prompt

A product-image-to-ad pipeline should begin with an approved source package: the exact sellable variant, front and detail photographs, current packaging, approved claims, brand colors, required disclosure text, destination URL, and channel placements. Give each source an asset ID and record which details may not change. The purpose is to separate product truth from creative direction before an agent proposes a scene or motion.

That separation matters at publication time. Google Merchant Center requires the main image to accurately display the product and recommends matching color, pattern, and material to the specific variant. Its current image rules also prohibit promotional overlays in the main product image and require generative-AI source metadata to be retained. Meta's advertising checklist separately says ads must accurately represent the advertised company, product, service, or brand; must not make potentially misleading claims; and must not portray nonexistent functionality.

Choose the static path by fidelity requirement

The published OfflineCreator MCP `generate` tool accepts a model ID, prompt, optional aspect ratio, and wait choice. It does not expose an image input for a text-to-image job. The package's `upload_input` tool is specifically for attaching a source to a reserved image-to-video generation. Therefore, do not describe the current public MCP interface as an image-to-image product compositor.

If exact packaging, typography, proportions, or color are mandatory, keep the approved photographed product pixels and use generated imagery only as a background, lighting reference, or composition sketch. Perform the final composite and live typography in a deterministic editor, then compare it with the truth set. If the deliverable is explicitly an exploratory concept, a fully generated still can remain in the proof set, but label it as a concept and do not use it as evidence of the product's appearance or features.

Preflight the upload and keep provider controls separate

At the MCP client boundary, version 0.1.2 accepts PNG, JPEG, WebP, or GIF bytes and limits decoded input to 10 MiB. A local `filePath` must remain inside the configured upload root, use an allowed extension, point to a regular non-empty file, and contain a recognized image signature. Remote MCP disables local path reading, so it requires `imageBase64`; when a content type is supplied, the client compares it with the detected bytes.

The MCP schemas expose `16:9`, `9:16`, and `1:1`, but no duration field. The underlying fal Kling 2.6 Pro endpoint separately requires a prompt and `start_image_url`, publishes five- and ten-second options, and defaults to five seconds. That provider schema explains the model envelope; it does not add a duration argument to the public MCP tool. Confirm the live MCP model record before spend and never copy provider-only fields into a tool call that does not publish them.

Local MCP

Use filePath inside the configured upload rootThe published client checks path containment, file status, extension, byte count, and recognizable image bytes.

Remote MCP

Use imageBase64The current client disables local path reads for the remote transport.

Duration

Do not invent an MCP duration argumentFive and ten seconds are provider-level options; the published MCP schemas do not expose duration.

Run a reject-first authenticity review

Review the unedited static concept or motion clip against the truth set before adding ad copy. Check the product silhouette, package dimensions, logo and label placement, spelling, colorway, materials, included accessories, quantity, and any visible feature that could change a buyer's understanding. For motion, compare the first frame, several middle frames, and the final hold. Record a specific pass, reject, or escalate reason instead of a general quality score.

Reject a creative when it changes the sellable variant, invents functionality, makes required text unreadable, depicts an unapproved claim, or turns a concept into apparent documentary proof. Minor scene defects can be revised by changing one controlled prompt phrase. Product drift should send the asset back to deterministic compositing or to a different approved source angle; it should not be hidden behind a crop, fast cut, or overlay.

Keep the evidence boundary visible

This page documents a bounded concept pipeline, not an automated ad-production or publishing system. The public MCP artifacts establish the current tool inputs, client-side upload checks, reservation sequence, and output ratios. They do not establish guaranteed product fidelity, advertising approval, conversion lift, channel compatibility, or successful preservation of logos, text, geometry, and color.

The refreshed last30days window returned adjacent third-party MCP ad tutorials and vendor promotions, but zero Offlinecreator-specific practitioner records cleared relevance for adoption or outcome claims, so no community anecdote is used as product evidence. Reddit coverage was partial, X was not configured, and failed or skipped lanes are treated as unknown rather than silence. Before editorial review, refresh the public package, Studio catalog, provider schema, and channel policies; then add an authorized generation and frame-review record if the page is expected to describe observed output behavior.