Agent skills
Install repeatable Uwear workflows or read the machine-readable manifest before connecting a tool.
Product · MCP
Turn every fashion brief into a reusable production workflow.
Bring the AI assistant and subscription you already use, whether that is Claude, ChatGPT, Codex, or another compatible client. Drive Uwear production tools through MCP and carry one brief through art direction, generation or edits, automatic QA, and repeatable runs. For runs that should start themselves, Production Automation picks up the same chain.
0:37One chat, start to finish: upload the collection folder, set the art direction, run the photoshoot. Watch on YouTube
Agent Mode is retired; conversational production now happens through Uwear MCP, inside the AI assistant you already use, with your Uwear assets and production history connected. For runs that should start themselves, the same chain lives on the Production Automation canvas: build it once, publish a version, and let triggers rerun it.
Install
Connect your assistant. Build the workflow once.
Bring the AI assistant and subscription you already use, whether that is Claude, ChatGPT, Codex, or another client that supports remote MCP servers. With the Uwear tools available through MCP, your assistant can prepare the brief, shape art direction, start generation or edits, and run automatic QA when enabled. You keep approval points where you need them. Production Automation carries the same production chain into a published workflow that reruns on its own.
Find Uwear in the official MCP Registry under ai.uwear/uwear. Use it as an additional discovery path; the remote server URL and client setup steps stay the same.
Start with a local agent if you can. Claude Code and Codex read garments straight from your folders and write finished images back to disk, exactly where your pipeline expects them. Chat workspaces take a short trip through Settings.
One command, then authenticate. A local agent reads your product folders and writes results back to disk.
- 1
Add the server:
claude mcp add --transport http uwear https://api.uwear.ai/mcp
- 2
Run /mcp inside Claude Code and complete the OAuth login with your Uwear account.
- 3
Ask for a Uwear photoshoot plan. The brief comes back for approval before any run.
The full agent surface
The MCP endpoint is the action layer. Skills, UWEAR.md, llms.txt, the JSON blog API, and the REST API help agents discover Uwear, learn the production contract, and choose the right way to work.
Agent-readable docs
UWEAR.md documents the production contract. llms.txt gives AI crawlers a concise map of the product.
JSON content API
A public, structured feed lets agents discover Uwear product guides and updates without scraping pages.
REST API
No MCP client? The same production over REST, with webhooks, QA, and metadata traceability.
See the workflow from prompt to costed brief in How to run an AI fashion photoshoot without leaving ChatGPT or Claude.
The toolkit
Ask for work, not for features.
Each of these is one message in the chat where you installed Uwear. Every generation stops at a costed brief before credits are spent.
01
One prompt becomes a costed brief.
0:11
02
Local agents read your files.
0:11drops/s26/
line-sheet.csv · 24 SKUs
flats/ · 24 images
plan
24 looks · one image per SKU
estimated 96 credits
✓ brief ready for review
03
QA comes back with reasons.
0:11
Rejected: five buttons
Approved on retry04
Results land where you work.
0:12assets/pdp/
DJ-2026-BLU_front.jpg
DJ-2026-BLU_detail.jpg
SK-2026-TPE_front.jpg
...
✓ 12 files written
05
Every top meets its best bottom.
0:12
Enterprise
Built for catalog work that starts outside Uwear.
Use the MCP when production begins in a conversation, a shared folder, a product feed, or an agentic workflow.
Creative teams
Turn one seasonal direction into consistent PDP, editorial, and video outputs.
Ecommerce teams
Prepare SKU-level production runs from product data without rebuilding briefs by hand.
Technical teams
Let Codex organize folders, CSVs, and briefs, then route approved work through Uwear MCP.
One platform, three ways in
The same production infrastructure, reached your way.
Studio, API, and the MCP share one model library, one clothing workspace, and one generation history. Pick the access path that fits the work, and move between them as the job changes.
Programmatic access
API
A REST API for async generation, edits, video, and identity. Wire production workflows into your catalog, DAM, and storefront.
ExploreOperator interface
Studio
The visual workspace for creative production. Batch catalogs, consistent models, edits, backdrops, video, and upscaling in one surface.
ExploreIn your own tools
MCP
Connect Uwear to Claude, ChatGPT, or any MCP client and run photoshoots from the tools your team already uses.
You are here
MCP FAQ
What enterprise teams usually ask about the MCP app.
A remote MCP server that turns your AI assistant into a fashion photoshoot tool. Inside ChatGPT, Claude, or Codex, the assistant browses your clothing and models, assembles looks, and prepares a costed photoshoot brief that you review and approve before anything runs.
Yes. Connect the Uwear MCP server and ask for a shoot in plain language. The assistant does the work on your behalf: it reads your garments, picks models, plans the looks, and shows you the itemized cost. Generation runs on Uwear once you confirm, and the finished product photos land in your workspace.
Because you never leave the chat. The assistant already has your context, from folders and CSVs to line sheets and earlier messages, so there is nothing to re-upload or re-explain. It handles the production steps for you, and the brief-approval gate keeps every credit spend under your control.
ChatGPT and Claude connect through their app and connector settings. Claude Code and Codex connect with one command plus an OAuth login. Any client that supports remote MCP servers works with the same URL, and agents can also read uwear.ai/llms.txt or UWEAR.md directly.
Ask it to. A bounded brief is the whole job: the SKU list or line sheet, the views per SKU, the saved art direction, QA on, and a spend cap. The assistant prices it first — SKUs × views × credits per image, at $0.10 a credit — and nothing runs until you confirm. Run a pilot of 10 to 20 SKUs, read the QA rejections, then release the rest in batches; the schedule follows the measured pilot, not a promise. Approved files land in your workspace, named by SKU.
No. Every run goes through brief review first: the itemized looks, the request count, and the exact credit cost. Generation only starts after you confirm.
In your Uwear workspace, in the same library Studio uses. You can review and QA them in Studio, keep iterating in chat, or pull them through the API.
No. MCP authenticates with your existing Uwear account. Studio, the API, and MCP all use the same credits and asset workspace.
Run the first collection brief.
Install the MCP in your workspace, or bring one catalog workflow and we will run it with you.
Existing customer? Log in to Studio
Pairs with Studio · API · Batch workflows
