All servers · Images & design · Maps, location & weather

Uwear

ai.uwear/uwear · v1.0.0

Measured by MCP Station

Description written by the publisher, not verified

AI photoshoot studio: garments, avatars, locations, and art direction

Connect

claude mcp add --transport http uwear https://api.uwear.ai/mcp

{
  "mcpServers": {
    "uwear": {
      "url": "https://api.uwear.ai/mcp"
    }
  }
}

Tools as reported by the server

• request_user_context
  Use this when the user wants a photoshoot and you have no board_id yet. Creates a new, empty Uwear Shoot Board and returns its board_id, which every other Shoot Board tool takes. This client shows no widget: build the shoot with tools (search_uwear_library, modify_shoot_board, propose_brief) and tel
• read_shoot_board
  Use this before modify_shoot_board, propose_brief or update_brief: the user changes the board in the widget at any time. Returns the board's items (Clothing, Models, Outfits, Locations, art directions, files, results) with ids and names, its revision, its linked brief_id, and brief_inputs: the guide
• search_uwear_library
  Use this when the user names Clothing, Models, Locations, art directions, files or past results in chat and you need their ids. Takes a short keyword query (2-5 words, or an exact name, SKU or id) and returns typed ids, names and thumbnails. It finds items; it does not recommend them. Changes nothin
• modify_shoot_board write/delete
  Use this when the user asks in chat to change what is on the open Shoot Board. add puts items on it; set replaces the whole item list (to remove items, send the ones to keep); clear empties one type, or without type starts a new shoot on the same board (its brief is unlinked; photos stay in the libr
• show_in_shoot_board
  Moves a Shoot Board that is open in a widget to a view (board, brief, automation, results, brief_history). This client shows no widget, so it changes nothing the user sees: read the board, brief or results with read_shoot_board, get_brief or get_generation_results and tell the user.
• add_chat_photos_to_board
  Use this when the user attaches images in this chat and wants them in Uwear, on the Shoot Board or in a shoot: clothing, a Model, a Location or a reference. Put each attachment in its own field, image_file_1, image_file_2, ... in attachment order, as the chat provides it: ChatGPT passes the file its
• set_garment_side
  Use this when a garment's photo shows its back but Uwear has it as the front (or the other way round): you saw the photo in this chat, or the user says so. side back makes the photo the garment's back, so back shots run from it; front undoes that. Call it yourself and continue (confirm_brief if the
• save_art_direction
  Use this when the user asks to create, write or save an art direction, or the board's New art direction asks for one: write it from their words, the chat and the board, and save it in the same turn. Saves it to the library and makes it the board's one art direction, replacing the previous one (which
• propose_brief
  Saves a new brief and shows it on the board: the looks to shoot, their direction and their shots. The previous brief is kept (one that ran stays in Brief History). Returns the saved brief, or the problems to fix.
• update_brief
  Use this when the user asks in chat to change the board's brief: its looks, Models, outfits, Locations, references, name, shots and steps, AI model or art direction. Send the complete replacement look list with the brief_id it replaces, keeping each unchanged look's key. Shots or steps: recipe with
• get_brief
  Use this when you need a Shoot Board brief by brief_id: its looks, automations, credit quote (quote.total_credits), status and revision. Shows it on the board; spends nothing.
• confirm_brief write/delete
  Generates the photos and videos of brief brief_id. Spends credits at the brief's quote. This client may show no approval prompt, so call it only when the user agreed in chat to run the brief: their message asking to generate or run it is that agreement, a request to change the brief is not one; othe
• list_briefs
  Use this to find a past shoot when the user refers to one ("run the same as last week") or asks what ran: the account's briefs, newest first, 10 by default (limit up to 25; before: next_before for older ones; status ran for generated ones only; automation_workflow_id for the runs of one Automation).
• list_automations
  Lists the user's Automations, most recently used first, one row each. 10 per page (limit up to 25; cursor: next_cursor for more). Changes nothing.
• mcp_brief_runs
  Use this after confirm_brief or when the user asks how a shoot is going: each look's run of brief_id with its status, credits, results (generation_result_id, kind, url) by step and the error of every step that failed (failures lists them all). Read it again until done is true; while it runs, say so
• get_generation_status
  Use this to check one generation job by generation_id: its status, credits and, when it failed, a safe error_message. A brief's runs are read with mcp_brief_runs. Changes nothing.
• get_generation_results
  Use this to show results in chat: generation_result_id (from mcp_brief_runs) for one result, generation_id for a job's results, or query, filters and dates to find past ones. Returns image previews to show as they are (never Markdown-embed result URLs); url is the original. Changes nothing.
• list_garments
  List user's garments with structured filters or query for hybrid name/SKU/metadata/image-attribute search. body_zone expands to categories and is ORed with category when both are given. With a category or body_zone filter and include_uncategorized=false, uncategorized_count reports garments hidden b
• upload_garment_from_public_url
  Upload Clothing from public HTTP(S) image URLs. Queues a recoverable batch upload and returns an operation immediately; retry with the exact same arguments to read its state (a retry creates no second upload). Photos are stored as uploaded, without background removal; processing_mode is ignored. Pre
• list_avatars
  List the user's Models: the reusable people who wear the Clothing (not the AI models; for those, use mcp_list_model_catalog). Supports structured filters or query for hybrid name/metadata/image-attribute search. Set include_image_url=true when the Model's image itself is needed.
• upload_avatar_from_chat_file
  Batch upload reusable Models from person photos the user attached in chat. Each photo becomes the upper_body_front identity anchor. Keep names and optional user-given age_range, build, and height_cm in avatars[], then pass top-level image_file_1, image_file_2, etc. in the same order. Traits are neve
• list_outfits
  List user's outfits (saved garment combinations). Filter by garment IDs, active status, date range, or query against contained garments.
• list_locations
  List reusable location/scene reference images by structured filters or query: IDs, tags, date range, and sort. Use when the user wants to pick a saved background/location reference for a generation.
• create_location
  Create a reusable location/scene reference from an image URL. If no description is supplied, the backend analyzes the image. Use the returned location_id in propose_brief/update_brief.
• create_tag
  Create a new tag for organizing assets (garments, models, outfits, files, results, locations). Requires an active company workspace.
• queue_generation_result_qa write/delete
  Default tool for generation-result QA. Use this whenever the user asks to QA, quality check, validate, review, inspect for defects, approve/reject, or assess already-created generation results. Do not substitute view_image for QA unless the user explicitly asks for a manual visual critique instead o
• read_generation_result_qa
  Read official Uwear QA status, decision, and structured QA JSON for existing generation results. Call this after queue_generation_result_qa when the user asks to QA/check/validate/review generated outputs; summarize the structured decision and issues, not a manual view_image opinion.
• set_generation_result_favorite write/delete
  The result viewer's star. Marks one of the user's own generation results as a favorite (favorite true) or removes the mark (false); deletes nothing and spends no credits.
• propose_montage
  ONLY for video montage/stitching/export workflows. Use when the user explicitly asks to create a montage, stitch clips, make a reel, export a video sequence, make video clips from images, or combine images/videos into one final video. Never use this for a photoshoot, lookbook, product shoot, collect
• update_montage_proposal
  Patch the latest MontageProposal already shown in the UI. Use only for an existing video montage/reel/stitched sequence proposal; do not use this to modify a photoshoot brief. For photoshoot brief changes, call update_brief instead. Prefer `operations`, an ordered list of typed montage edits such as
• get_user_credits
  Get user's current credit balance.
• list_tags
  List available tags for the user's company. Use this to resolve user-provided tag names like 'summer26' before selecting garments, outfits, models, files, generations, or locations. For no-UI MCP flows, find the tag ID here, then call get_items_by_tag or the relevant list_* tool with tag_ids.
• save_reference_file_from_chat_file
  Batch save reference images from chat attachments into the Files library. Keep file metadata in files[] and pass top-level image_file_1, image_file_2, etc. in the same order. No base64, no local paths. Use for mood boards, backgrounds, and other reference images that are not Clothing or Models.
• list_art_directions
  List selectable ArtDirections as compact summaries: visible system ArtDirections plus company ArtDirections. Use query to match exact names and natural-language creative requests. Use this as the catalog step before choosing an art_direction_id for a brief; if there is no clear match, fall back to t
• get_art_direction
  Get a selectable ArtDirection by ID.
• list_templates
  List canonical company templates, optionally filtered by kind, scope, command use case, or public t-xxxx share code. Templates persist canonical commands but do not execute generations. System templates named `Demo — …` are worked examples of the canonical command language; read one with `get_templa
• mcp_get_context
  Read the Uwear Shoot Board.
• mcp_replace_context write/delete
  Replace the Uwear Shoot Board items.
• mcp_add_context
  Append items to the Uwear Shoot Board.
• mcp_clear_context write/delete
  Clear all Shoot Board items, or only one context type.
• mcp_list_files
  List uploaded (reference) files for the Uwear MCP workspace files tab and the Shoot Board's References tab.
• mcp_save_retouch
  Save an edited image (image_base64) as a new child result of parent_generation_result_id. Changes no existing result.
• mcp_export_montage write/delete
  Export montage clips as one stitched video. Spends credits: call it only after the user confirmed the clips and their order in chat. Returns the generation_id to poll with get_generation_status.
• mcp_generate_clip write/delete
  Queue an image-to-video generation for one montage clip. Spends credits: call it only after the user agreed in chat. Returns the generation_id to poll with get_generation_status.
• mcp_intake_files
  Sort photos dropped on the Shoot Board into garment, avatar, location or reference (or unsure with two candidates) and report duplicates within the drop and in the library. Saves nothing. A photo the call had no time left for comes back with error deferred: send it again.
• mcp_commit_intake
  Save sorted Shoot Board photos to the library as garments, avatars, locations or reference files, skip ones already saved, and add them to the Shoot Board at expected_revision; a board that changed is refused before anything is saved (revision_conflict with the current board).
• mcp_reclassify_board_item write/delete
  Move a Shoot Board photo between the Clothing, Models and Locations piles. Saves the same image as the new kind and swaps it on the board; the old asset is deleted only if intake saved it in the last 24 hours and nothing uses it, otherwise it stays in the library. Asking for a move that already happ
• mcp_add_garment_view write/delete
  A Clothing card dropped on another. The photo of from_garment_id becomes the back, side or detail view of garment_id, and from_garment_id leaves the board (deleted only when it is a fresh drop nothing else uses). Or a photo put in the brief's missing-photo slot: image_url instead of from_garment_id,
• mcp_upload_intake_photo
  Store one photo dropped on the Shoot Board, sent inline as base64, for a host that cannot upload files itself. Returns a receipt (sha256, size, stored, image_url, image_url_expires_at); pass image_url to mcp_intake_files and mcp_commit_intake. Without data, stores nothing and returns the receipt of
• mcp_edit_brief
  Edit the Shoot Board's brief by hand: add, remove or change looks, or run looks through another automation. Saves a new brief linked to the board and returns the board, the brief, its quote and the credit delta; dry_run only quotes.
• mcp_recipe_history
  An automation's past runs, newest first: one row per Shoot Board Generate (its looks) or per run started on Uwear, with when, how it went, credits and covers.
• mcp_brief_list
  The account's Shoot Board briefs, newest first: every brief that ran (on any Shoot Board) and this board's draft, each with its status, looks, automations, credits and covers.
• mcp_recipe_list
  The company's shoot automations (and other automations to copy).
• mcp_recipe_open
  Open the brief's automation in the builder: its draft, or once Generate published it its live version (saving an edit of it makes a new automation); another automation opens read-only.
• mcp_recipe_preflight
  Validate and price the automation being edited.
• mcp_recipe_save_draft write/delete
  Save the automation's draft.
• mcp_recipe_copy
  Copy an automation as a new automation for this shoot.
• mcp_workflow_assets
  The automation builder reads library items (Clothing, Models, Locations, ...) of one kind by id to show them on its cards. Read-only.
• mcp_workflow_gallery
  The automation builder's picker: one page of the user's library items of one kind, filtered by search text, tags or category. Read-only.
• mcp_workflow_tags
  The account's tags, for the automation builder's tag filters. Read-only.
• mcp_workflow_garment_categories
  The garment categories, for the automation builder's category filters. Read-only.
• mcp_workflow_cameras
  The camera views (front, side, back, crops) a shot or camera edit can use, for the automation builder. Read-only.
• mcp_workflow_contract
  The automation format (step kinds and their settings) the automation builder edits against. Read-only.
• mcp_read_generation_result
  One generation result as GET /generation-result/{id} returns it (tags, review verdict, QA, prompt, model), for the widget's result viewer.
• mcp_read_generation
  One generation with its results as GET /generation/{id} returns it (prompt, model, settings, inputs), for the result viewer's Info panel.
• mcp_review_generation_results write/delete
  The result viewer's review rail. Sets the user's verdict on their own results to approved or rejected, or clears it (decision null), replacing any verdict they had; deletes nothing and spends no credits.
• mcp_extract_video_frame
  Save a still frame of a video result as a new image result, as POST /generation-result/{id}/extract-frame. The result viewer's Save frame.
• mcp_set_generation_result_tags write/delete
  Replace a result's tags with tag_ids (empty removes all), as PUT /generation-result/{id}/tags. The result viewer's tag tray. A tag that starts one of the user's automations starts it, as on the platform.
• mcp_update_tag write/delete
  Rename or recolor one of the company's tags, as PATCH /tag/{id}. The result viewer's tag tray.
• mcp_delete_generation_results write/delete
  Delete the user's results and their stored images, as the platform's Delete. Cannot be undone: call it only after the user confirmed in chat which results to delete.
• mcp_list_model_catalog
  The active AI models with their capabilities and pricing rules, as GET /models returns them, for the widget's model pickers.
• uwear_settings_read
  Read the user's saved photoshoot defaults (aspect ratio, camera, resolution) with every allowed value. Backs the plugin settings page.
• uwear_settings_update write/delete
  Save changed photoshoot defaults (aspect ratio, camera, resolution). Send only the settings that changed; returns every current value. Defaults never authorize a paid generation.

Tool changes

• 2026-10-24: request_user_context, read_shoot_board, search_uwear_library, modify_shoot_board, show_in_shoot_board, add_chat_photos_to_board, set_garment_side, save_art_direction, propose_brief, update_brief, get_brief, confirm_brief
• 2026-10-23: request_user_context, read_shoot_board, search_uwear_library, modify_shoot_board, show_in_shoot_board, add_chat_photos_to_board, set_garment_side, save_art_direction, propose_brief, update_brief, get_brief, confirm_brief
• 2026-10-22: request_user_context, read_shoot_board, search_uwear_library, modify_shoot_board, show_in_shoot_board, add_chat_photos_to_board, set_garment_side, save_art_direction, propose_brief, update_brief, get_brief, confirm_brief
• 2026-10-16: request_user_context, read_shoot_board, search_uwear_library, modify_shoot_board, show_in_shoot_board, add_chat_photos_to_board, save_art_direction, propose_brief, update_brief, list_garments, upload_garment_from_public_url, list_avatars

Website · JSON · Text for agents · Registry updated 2026-08-01