{
  "markdown": "# Uproad plugin for Claude Code\n\nTake a client brief to a link the client can actually open — without leaving Claude Code.\n\n[Uproad](https://uproad.design) hosts HTML prototypes behind private links that need no account to view, and lets the person reviewing click anywhere on the page to leave a pinned comment. This plugin wires that into your session: two skills that cover the round trip, and the MCP connection set up for you.\n\n## Install\n\n```\n/plugin marketplace add naruto1031/uproad-plugin\n/plugin install uproad@uproad\n```\n\nYou will be asked for an Uproad API token. Create one at [uproad.design/settings/tokens](https://uproad.design/settings/tokens) (workspace admins only) — it starts with `up_`. It is stored in secure storage, not in a settings file, and the plugin uses it to connect to Uproad's MCP server for you. There is no `claude mcp add` step.\n\n## What it does\n\n### `/uproad:new`\n\nFrom meeting notes, a Slack paste, or a one-line idea — with **two stops for you** along the way:\n\n1. **Interviews you** one question at a time, each with a recommended answer, until the requirements stop moving. It reads what it can find instead of asking about it.\n2. Writes a spec in Japanese — 背景・目的 / 対象ユーザー / 画面と導線 / 機能要件 / **確認事項** — then **stops so you can correct it**.\n3. Builds a self-contained prototype, serves it locally, and **stops so you can look at it**. Stays in that loop until you approve.\n4. Asks whether this goes out **公開** (a share link the client opens without an account) or stays **非公開**\n   (visible only to signed-in members of your workspace), then pushes both to Uproad.\n\nThe stops are the point. A spec you have not corrected produces a prototype built on the wrong assumptions, and a prototype you have not seen should not reach a client.\n\nThe visibility question is asked before the push, not after: publishing through the MCP tools only goes one way, and taking a design back down is a toggle in the app.\n\nThe 確認事項 section is what earns a reply: every assumption made on the client's behalf is written back as a question the client can answer.\n\nThe prototype and the spec hang off the same design, so one link reaches both — the client sees the screens, and whoever implements it later sees what it was supposed to do.\n\n### Where files land\n\nOne directory per design, so several sit side by side:\n\n```\ndesigns/\n  acme-lp/\n    index.html\n    spec.md\n  billing-dashboard/\n    index.html\n    spec.md\n```\n\nThe local server runs from `designs/`, so every design is browsable at once.\n\n### `/uproad:review`\n\nWhen the comments come back:\n\n1. Reads the unresolved comments, including where on the page they were pinned\n2. Applies the change requests, and updates the spec if the behaviour changed\n3. Serves the fixes locally and **stops so you can check them** — the client's link is already in their inbox, so a wrong fix would reach them at once\n4. Pushes a new version — **the share link does not change**\n5. Marks resolved only what was actually done\n\nQuestions and out-of-scope requests are handed back to you instead of being silently closed. The MCP tools cannot reply to a comment, so answering happens in the app.\n\n## Requirements\n\n- Claude Code with plugin support\n- An Uproad workspace (the free tier is enough to start)\n\nGuest pinned comments are a Team-plan feature; on Free and Personal the client still opens the link, just without commenting on the page.\n\n## Underneath\n\nThe plugin talks to Uproad's MCP server at `https://uproad.design/mcp` (Streamable HTTP, stateless, bearer auth). The same tools are available to any MCP client — see the [MCP docs](https://uproad.design/docs/mcp) if you want to use them directly, or [`npx uproad`](https://www.npmjs.com/package/uproad) for the command line.\n\n## License\n\nMIT\n",
  "bytes": 3760,
  "sha": "6b2f888ae2d5f1067bd6042375558ff2767d881da6e79eea17d4f0fc8419c6f8",
  "repo_slug": "naruto1031/uproad-plugin",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_design_uproad_uproad_b200a564/readme"
}