Uwear MCP server
Which servers in the official MCP registry are Uwear's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-13
- Registry nameai.uwear/uwearverified in the MCP registry
The registry name sits under uwear.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-13
- Tools70
- Server calls itselfuwear
- Server version2.0.0
- Protocol version2025-06-18
On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 245 ms.
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 shoot with tools…
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) with ids and names…
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, names and…
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 starts a new shoot on…
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_shoot_board, get_brief…
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_2, ... in…
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 library and makes it…
propose_briefUse this when the user describes a shoot. Saves a brief, the looks to shoot and the automation they run through, and links it to the board in place of the current one. Nothing runs or is charged: show the user the looks and the credit…
update_briefUse 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…
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 filter and…
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 stored as…
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 include_image_url=true…
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 pass top-level…
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.
get_generation_statusCheck generation job status. Completed results may include labeled native ImageContent previews; use them directly and never Markdown-embed result URLs. They are display previews, not originals: url/download_url are originals, preview_url…
get_generation_resultsLook up generation results by exact IDs, filters, or hybrid image/name/SKU search. Returns labeled native ImageContent previews; use them directly and never Markdown-embed result URLs. They are display previews, not originals…
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_image for QA unless…
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 structured…
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 one final video…
update_montage_proposalPatch 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…
get_user_creditsGet user's current credit balance.
list_tagsList 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…
save_reference_file_from_chat_fileBatch 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…
list_art_directionsList 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…
get_art_directionGet a selectable ArtDirection by ID.
list_templatesList 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…
mcp_get_contextRead the Uwear Shoot Board.
mcp_replace_contextReplace the Uwear Shoot Board items.
mcp_add_contextAppend items to the Uwear Shoot Board.
mcp_clear_contextClear all Shoot Board items, or only one context type.
mcp_list_filesList uploaded (reference) files for the Uwear MCP workspace files tab and the Shoot Board's References tab.
mcp_save_retouchSave an edited image (image_base64) as a new child result of parent_generation_result_id. Changes no existing result.
mcp_export_montageExport 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_clipQueue 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_filesSort 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…
mcp_commit_intakeSave 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…
mcp_reclassify_board_itemMove 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…
mcp_add_garment_viewA 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…
mcp_upload_intake_photoStore 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_edit_briefEdit 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.
get_briefRead one of the account's Shoot Board briefs by brief_id: its looks, automations, credit quote and status. Changes nothing.
confirm_briefGenerate a Shoot Board brief: publishes its automation drafts, then starts one workflow run per look, charged per run. Spends credits: call it only after the user has seen the brief's looks and credit quote (get_brief) and agreed in chat…
mcp_brief_runsEvery look's run of a generating brief (brief_id), or runs by id (workflow_run_ids, each with the look its cards held): status, results by step, credits.
mcp_recipe_historyAn 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_listThe 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_listThe company's shoot automations (and other automations to copy).
mcp_recipe_openOpen 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_preflightValidate and price the automation being edited.
mcp_recipe_save_draftSave the automation's draft.
mcp_recipe_copyCopy an automation as a new automation for this shoot.
mcp_workflow_assetsThe automation builder reads library items (Clothing, Models, Locations, ...) of one kind by id to show them on its cards. Read-only.
mcp_workflow_galleryThe 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_tagsThe account's tags, for the automation builder's tag filters. Read-only.
mcp_workflow_garment_categoriesThe garment categories, for the automation builder's category filters. Read-only.
mcp_workflow_camerasThe camera views (front, side, back, crops) a shot or camera edit can use, for the automation builder. Read-only.
mcp_workflow_contractThe automation format (step kinds and their settings) the automation builder edits against. Read-only.
The first 60 of 70, as the server listed them.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"uwear": {
"type": "http",
"url": "https://api.uwear.ai/mcp"
}
}
}Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.