Integration · WooCommerce

Generate on-model photos for your WooCommerce products

Select products with your assistant, generate a Product page set, then upload the images to WordPress and assign them with the WooCommerce REST API.

Get a demoSet up Uwear MCP
Model wearing a striped camp-collar resort shirt, full-body front on the Pure White studio, generated with nano-banana-pro through the Product page set template
Front hero from the Product page set template: striped resort shirt on the Pure White studio, generated with nano-banana-pro through the Uwear MCP.

Use cases

What can you build?

  • Generate photos by product and variation

    Create white-studio front, upper-body and back views. Keep Woo product, variation and attachment IDs linked to each generated set.[2][3]

  • Build virtual try-on in your storefront

    Prototype through Uwear MCP. Build a WordPress block or use the classic product hooks, then connect a permission-checked backend route to Uwear API. Identify the theme first.[34][35][36][39]

Model wearing the same striped camp-collar resort shirt, full-body back camera edit on the Pure White studio, generated with nano-banana-pro through the Product page set template
Back view from the same Product page set run: a camera edit of the front hero, so the model, light, and studio carry over. Generated with nano-banana-pro through the Uwear MCP.

Assistant workflow

How do you run this from your assistant?

Proposed integration, not a preinstalled connection. Connect WooCommerce’s developer-preview MCP and Uwear MCP, then use assistant-executed REST or a built adapter for media. A dedicated media ability is a proposal.[6][7][8][9][10][11]

  • WooCommerce Model Context Protocol (MCP) Integration

    Uses WordPress MCP Adapter. The inspected woocommerce/products-query, woocommerce/product-create and woocommerce/product-update schemas have no image fields. Read photos and write media through REST.[6][7][8][9][10][11]

    Developer preview. Use a WordPress username and Application Password over HTTPS, or WP-CLI locally with --user; discover the installed tools first.[6][7][8][9][10][11]

  • MCP on WordPress.com

    Its hosted wpcom-mcp-content-authoring tools include media.create and media.update. They upload files and edit metadata, but do not document Woo product-media assignment.[12][13]

    Hosted WordPress.com only, with OAuth 2.1; not a media service for every self-hosted store.[12][13]

  1. Connect and inspect the abilities

    Use WordPress MCP Adapter at /wp-json/mcp/mcp-adapter-default-server. Authenticate with a username and Application Password over HTTPS, or WP-CLI locally with --user. Check the store’s actual schemas.[6][7][11]

  2. Read products and source photos

    Select products with woocommerce/products-query. Read images through GET /wp-json/wc/v3/products/{id} and variations through its variations endpoint. Keep product, variation, SKU and attachment IDs.[2][3][8][11]

  3. Approve the Product page set brief

    Load Product page set on its Pure White studio at 2:3 with the AI reviewer on. Review the costed brief in credits before generating. QA is automatic and toggleable: when on, an AI reviewer compares results with source photos and retries flagged results.

  4. Upload and assign the stills

    Use WordPress REST media upload and alt_text, then Woo REST images with attachment id and alt. WordPress media auth is separate from Woo Consumer Key/Secret auth; preserve the existing image IDs when appending.[2][15][16][17][18][20]

  5. Verify the product and selected variation

    Read attachments and products back, wait for results to be available, and inspect image order, alt text and crops in the storefront. Handle video outside the image payload.[2][3][16][21]

Run it from your assistant

Run this photoshoot from your AI assistant with a Uwear template.

Connect the Uwear MCP server to ChatGPT, Claude, or Codex and ask for the Product page set template. It is a batch workflow that runs once per garment: front, upper-body, and back product-page shots on a white studio background, plus a 360-degree video, from one garment photo. Any Uwear account can load it by name, and the assistant shows a costed brief in credits before generation starts.

Copy this prompt into your assistant

Connect the WooCommerce Model Context Protocol (MCP) Integration through WordPress MCP Adapter and the Uwear MCP server in this session. Inspect the installed abilities, select products with woocommerce/products-query, read photos through Woo REST, and keep product, variation and attachment IDs. Load "Product page set" on its Pure White studio setup at 2:3, turn the AI reviewer on, and show me the costed brief in credits before generating. After I approve, use authorized REST operations or a built adapter to POST /wp-json/wp/v2/media, set alt_text, then PUT /wp-json/wc/v3/products/{id} with images containing attachment id and alt while retaining existing IDs. Wait for readiness and verify product and variation galleries before reporting.

Set up the MCP server

What one run does, per garment

  1. Generate the front hero

    One full-body front photo of the garment on the template model, in the Basic white photoshoot art direction on the Pure White studio location.

  2. Edit to the upper-body crop

    A camera edit that reframes the front result to an upper-body front frame instead of generating a new image, so the crop comes from the same session as the hero.

  3. Edit to the back view

    A second camera edit of the front result to a full-body back frame, so the product page gets the back of the garment from the same session.

  4. Render the 360 turn

    A 5-second Kling 3 Pro video from the front photo: the model turns a slow, full 360 degrees in place, garment readable throughout.

Outputs per garment

  • Full-body front photo, 2K, 2:3
  • Upper-body front photo, 2K, 2:3
  • Full-body back photo, 2K, 2:3
  • 5-second 360-degree video

The setup the template pins

Template kind
Batch workflow: runs once per garment row
System key
demo_full_pdp_test_white_studio
Art direction
Basic white photoshoot (system art direction)
Location
Pure White (system studio location)
Model
The Uwear system model by default; the assistant can swap in one of your saved models when it proposes the brief
Image model
nano-banana-pro, 2K, 2:3
Video model
Kling 3 Pro, 5 seconds
QA
Optional. With the AI reviewer on, each result is checked against the source product photo and flagged results are retried
Approval
The assistant shows a costed brief in credits before anything generates

Pure automation

How does API delivery work?

POST /wp-json/wp/v2/media with file bytes, Content-Type and Content-Disposition filename. Write alt_text through POST /wp-json/wp/v2/media/{id}, then PUT /wp-json/wc/v3/products/{id} with images entries containing attachment id, name and alt. Retain existing IDs: the submitted array replaces the featured/gallery assignment.[2][16][17][20]

  1. Receive product events

    A worker receives Woo product webhooks, validates the hash and keeps the product/variation mapping. Deduplicate events and ignore gallery updates caused by the worker itself.[40]

  2. Run generation without an assistant

    Submit Uwear REST API jobs and receive completion webhooks or poll. A published Production Automation can also start when a garment is processed, a tag is added or an outfit is created. These are Uwear workspace triggers; platform delivery still needs an adapter.

  3. Upload and assign through REST

    Use WordPress Application Password authentication for media uploads and authorized Woo REST product updates for attachment assignment. Read back the final image list.[2][15][16][18]

Platform requirements

What image specifications apply?

WooCommerce: What image specifications apply?
SpecificationRequirement or guidance
Source dimensionsWoo recommends at least 800 × 800 px; this is not a mandatory upload minimum.[21]
Ratio and cropSquare, custom and uncropped display options depend on the theme. They do not require a square source image.[22]
File limitsThere is no verified universal WooCommerce byte ceiling. Check the host and PHP upload_max_filesize setting.[23]
FormatsConfirm the site’s allowed MIME types before selecting JPEG, PNG, WebP or AVIF; allowed types can be filtered.[24]
Variation imagesUse image for the featured attachment and gallery_image_ids for additional attachments where supported. Check the installed version.[3]
VideoThe documented core gallery-video beta uses the editor and excludes REST, CSV and variation galleries. Use a separately tested video display path.[21]

Existing options

Which AI image tools are already available?

Documented features from the linked sources. These are not independent quality tests.

  • AI Product Image Generator for WooCommerce, W7S

    A fit for quick concept images in the editor. Its FAQ says only the text prompt is sent to Gemini. The listing shows $39 for one year, plus separate API usage; currency and plugin-specific review totals were not verified.[26]

  • Fotogenic AI – AI Image Studio

    A fit for existing-photo catalog work inside WordPress, including gallery publishing. The directory shows fewer than 10 active installations and 5/5 from one rating. Eligible accounts receive trial credits, not a verified number of free generations.[27]

  • VividCart – AI Product Images for WooCommerce

    A fit for source-photo editing with direct OpenAI or Gemini billing and an apply-to-product action. The plugin is free; provider usage is separate. Fewer than 10 active installations and no reviews were shown.[29]

  • AnyDress – AI Virtual Try-On for WooCommerce & AI Product Photos

    A fit for teams that want shopper try-on and an Admin Virtual Photoshoot dashboard in one plugin. Requires an AnyDress API licence. Fewer than 10 active installations and no reviews were shown; fit and returns claims were not validated.[30]

  • AI Virtual Try On for WooCommerce, Addify

    A fit for shopper photo/camera try-on with placement and usage controls. The listing showed $59 for one year and localized to CAD $83 on direct fetch; confirm checkout currency. No own review total was verified.[32]

Frequently asked questions

Yes, with Uwear MCP and authorized WordPress/Woo REST operations or a built adapter. The inspected Woo MCP product abilities have no image fields. WordPress.com media.create is hosted-only and does not assign Woo product media; a dedicated media ability must be built.[2][6][11][12][13][16]

The shared MCP endpoint uses a WordPress username and Application Password over HTTPS, or local WP-CLI with --user. WordPress REST media can use Application Passwords. Woo REST Consumer Key/Secret permissions are separate; a Woo key does not establish WordPress media access.[6][15][18]

The REST schema includes image and gallery_image_ids. Variation galleries were opt-in in 10.9; the current migration guide says 11.1 enables them for all stores. Confirm the installed version and theme before assigning extra views.[3][4][5]

The inspected core gallery-video beta guide excludes REST, CSV and variation-gallery support. Keep the clip separate and test the editor route or a custom video block.[21]

Uwear uses credits at $0.10 per credit; model rates are on /models. The assistant shows a costed brief before generation. QA is automatic and toggleable: when on, an AI reviewer compares results with source photos and retries flagged results.

Yes. Generate in Uwear Studio, download the results, then use WooCommerce’s Product image and Product gallery controls. Check the theme crop and image order.[21][22]

Research

Sources and access dates

  1. [2]
  2. [3]
  3. [4]
  4. [5]
  5. [6]
  6. [7]
  7. [8]
  8. [9]
  9. [10]
  10. [11]
  11. [12]
  12. [13]
  13. [15]
  14. [16]
  15. [17]
  16. [18]
  17. [20]
  18. [21]
  19. [22]
  20. [23]
  21. [24]
  22. [26]
  23. [27]
  24. [29]
  25. [30]
  26. [32]
  27. [34]
  28. [35]
  29. [36]
  30. [39]
  31. [40]

Next step

Connect your catalog to Uwear.

Start with an assistant-led test, then build the API delivery your catalog needs.

Get a demoSet up Uwear MCP