Uwear

できること

このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。

• 接続方法: クラウドで動く
• トランスポート: Streamable HTTP
• カテゴリ: 旅行・地図・天気

インストール

使っているAIアプリを選んで、設定をコピーしてください。

必要なもの

• クラウドで動くインストール不要。インターネット経由でつながります

どのアプリを使っていますか？

https://api.uwear.ai/mcp

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

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

{
  "servers": {
    "uwear": {
      "type": "http",
      "url": "https://api.uwear.ai/mcp"
    }
  }
}

https://api.uwear.ai/mcp

選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。

この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。

できること

ツールの名前と説明は、サーバーが2026年11月10日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。

• 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, pr

• 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 bri

• 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

• modify_shoot_board

  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; pho

• 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 us

• 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

• 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. When the board holds the same ga

• 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

• plan_shoot_image

  Add 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 brief and quote. No media generation, credit charge or library c

• plan_shoot_edit

  Append 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 brief and quote. No media generation, credit charge or librar

• plan_shoot_camera_change

  Append 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 and quote. No media generation, credit charge or library chang

• plan_shoot_upscale

  Append 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 quote. No media generation, credit charge or library change.

• plan_shoot_background_removal

  Append 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 and quote. No media generation, credit charge or library cha

• plan_shoot_video

  Append 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 and quote. No media generation, credit charge or library ch

• remove_shoot_image

  Remove 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 brief and quote. No media generation, credit charge or library

• remove_shoot_step

  Remove 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 a new brief and quote. No media generation, credit charge o

• get_automation

  Read 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 flow null when it uses unsupported workflow nodes. Changes no

• save_automation

  Save 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_automation

  Publish 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 snapshots remain unchanged. No media generation or charge.

• propose_brief

  Saves 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 problems to fix.

• update_brief

  Revise 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 and quote. No media generation, credit charge or reusable-libr

• 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

  Executes 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 brief: their message asking to generate or run it is that agr

• 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

• 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; wh

• 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. Chang

• 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 repor

• 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_

• 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 or

• 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

  Run or re-run official Uwear QA on existing generation results. Every image generate/edit result already gets a free AI check after delivery, so when the user asks to QA, quality check, validate, review or inspect results, first call read_generation_result_qa and use the existing

• read_generation_result_qa

  Read the official Uwear QA check of existing generation results. Call this first when the user asks to QA/check/validate/review generated outputs: most image results already have a free AI check. ai_qa gives the state (checking, passed, issues, unavailable, not_checked, not_suppo

• set_generation_result_favorite

  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, pr

• 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 m

• 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

• 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 Clot

• 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 m

• get_art_direction

  Get a selectable ArtDirection by ID.

• list_templates

  List canonical company templates, optionally filtered by kind, scope, command use case, creator, or public t-xxxx share code, with usage sorting. Keeps identify which values apply. Templates persist canonical commands but do not execute generations. System templates named `Demo —

• mcp_get_context

  Read the Uwear Shoot Board.

• mcp_replace_context

  Replace the Uwear Shoot Board items.

• mcp_add_context

  Append items to the Uwear Shoot Board.

• mcp_clear_context

  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

  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. Prefer export_montage for a saved montage the user can open in Uwear.

• mcp_generate_clip

  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. Prefer generate_montage_clips for a saved montage the user can open in Uwear.

• 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

  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 mo

• mcp_add_garment_view

  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

• 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 ret

基本チェックi

誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月10日にチェック

• ! 注意

  作者とリポジトリが一致

  レジストリにソースのリポジトリが載っていないため、公開者（uwear.ai）とコードを照合できません

• … 未チェック

  今もメンテナンスされている

  このリポジトリはまだGitHubから読み取っていません

• … 未チェック

  ライセンスがある

  このリポジトリはまだGitHubから読み取っていません

• ✓ 合格

  エンドポイントが応答する

  294ミリ秒で応答（HTTP 200）

• – 対象外

  OAuthでサインイン

  サインイン不要

• ✓ 合格

  ツールの説明に隠れた指示がない

  60件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした

旅行・地図・天気のほかのサーバーとの比較i

• このカテゴリのほかの1794件のうち0%よりスターが多い
• このカテゴリのほかの1794件のうち21%より最近レジストリに公開
• 基本チェックの結果が、このカテゴリのほかの1794件のうち53%と同じかそれ以上

レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。

代わりの候補

同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。

カードの見方：↓ 週あたりのダウンロードi★ GitHubスターi3つの柱：レビュー · チェック · 利用状況i更新＝最新バージョンをレジストリに公開した日i

作者のREADME

リポジトリにREADMEが見つかりません