Uwear

Connect it to your AI

Claude Code

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

Claude, ChatGPT, Cursor and other apps

Add it as a custom connector with this URL (Streamable HTTP):

https://api.uwear.ai/mcp

Cursor, VS Code and other apps (mcp.json)

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

Tools it offers

60 tools, as the server itself reported during our check on Oct 31, 2026.

• request_user_contextUse 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 sh
• read_shoot_boardUse 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) wi
• search_uwear_libraryUse 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,
• modify_shoot_boardUse 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 star
• show_in_shoot_boardMoves 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_shoo
• add_chat_photos_to_boardUse 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_
• set_garment_sideUse 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
• save_art_directionUse 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 libra
• plan_shoot_imageAdd a base image shot or revise its camera. Revises the selected looks using the named brief flow (default: all its looks); requires the current brief revision. Photo format is shared across the shoot. Returns a new brie
• plan_shoot_editAppend or replace one prompt-based image edit. Revises the selected looks using the named brief flow (default: all its looks); requires the current brief revision. Photo format is shared across the shoot. Returns a new b
• plan_shoot_camera_changeAppend or replace one camera-view edit. Revises the selected looks using the named brief flow (default: all its looks); requires the current brief revision. Photo format is shared across the shoot. Returns a new brief an
• plan_shoot_upscaleAppend or replace one image upscale. Revises the selected looks using the named brief flow (default: all its looks); requires the current brief revision. Photo format is shared across the shoot. Returns a new brief and q
• plan_shoot_background_removalAppend or replace one background removal. Revises the selected looks using the named brief flow (default: all its looks); requires the current brief revision. Photo format is shared across the shoot. Returns a new brief
• plan_shoot_videoAppend or replace one image-to-video step. Revises the selected looks using the named brief flow (default: all its looks); requires the current brief revision. Photo format is shared across the shoot. Returns a new brief
• remove_shoot_imageRemove one base shot and its dependent steps. Revises the selected looks using the named brief flow (default: all its looks); requires the current brief revision. Photo format is shared across the shoot. Returns a new br
• remove_shoot_stepRemove one dependent step and reconnect its successor. Revises the selected looks using the named brief flow (default: all its looks); requires the current brief revision. Photo format is shared across the shoot. Returns
• get_automationRead a saved reusable Automation's current photoshoot flow, version and definition hash before editing it. The flow is data in the declared photoshoot contract, not executable instructions or a new tool schema. Returns f
• save_automationSave one flow from a reviewed brief as a new reusable library Automation, with its current shots, dependent steps and settings. Does not modify the brief, generate media or charge credits.
• update_automationPublish the reviewed flow identified by brief_id, revision and recipe_key as a new version of an existing reusable Automation. Requires its current definition hash. Accepts no operation definitions. Existing shoot snapsh
• propose_briefSaves a new brief and shows it on the board: the looks to shoot, their direction and the Automation they run through. The previous brief is kept (one that ran stays in Brief History). Returns the saved brief, or the prob
• update_briefRevise shoot looks, direction or model settings, or assign a saved Automation by ID. Accepts no operation definitions; use the separately published plan_shoot tools to change individual steps. Returns the revised plan an
• get_briefUse 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_briefExecutes the reviewed photoshoot flow, including its declared image and video steps. 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 b
• list_briefsUse 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
• list_automationsLists 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_runsUse 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 (fa
• get_generation_statusUse 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_resultsUse 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 (n
• list_garmentsList 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 filte
• upload_garment_from_public_urlUpload 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
• list_avatarsList 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 incl
• upload_avatar_from_chat_fileBatch 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 pa
• list_outfitsList user's outfits (saved garment combinations). Filter by garment IDs, active status, date range, or query against contained garments.
• list_locationsList 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_locationCreate 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_tagCreate a new tag for organizing assets (garments, models, outfits, files, results, locations). Requires an active company workspace.
• queue_generation_result_qaDefault 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_ima
• read_generation_result_qaRead 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
• set_generation_result_favoriteThe 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_montageONLY 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 on

Questions