Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Uproad
Overview
Description from the maker (original English)
Share prototypes as private links clients open without an account, attach specs, read comments.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Other
- You need to fill in: Authorization
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- You fill in yourself:
Authorization
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http uproad https://uproad.design/mcp --header 'Authorization: your-value'Fill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"uproad": {
"url": "https://uproad.design/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"uproad": {
"type": "http",
"url": "https://uproad.design/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
Authorizationsecret required HTTP headerBearer . Create a token at https://uproad.design/settings/tokens (workspace admins only).
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain uproad.design (the registry checks domain ownership)
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Otheri
- More stars than 0% of the other 18386 servers in this category
- Published to the registry more recently than 18% of the other 18386 servers in this category
- Basic checks equal to or better than 100% of the other 18386 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Uproad safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: Authorization
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 3 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, Tethered Trust
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated 2 days ago
Install
Tethered Trust
by tetheredtrust.com
Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.
Runs in the cloudUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Uproad plugin for Claude Code
Take a client brief to a link the client can actually open — without leaving Claude Code.
Uproad 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.
Install
/plugin marketplace add uproad-design/uproad-plugin/plugin install uproad@uproad
Nothing to paste. The first time a skill needs Uproad, Claude Code asks you to sign in: run /mcp, pick uproad, choose Authenticate, and a browser tab opens Uproad's consent screen. Log in, pick which workspaces the connection may reach (all of them by default — /uproad:new asks which workspace a new design goes to only when there is more than one), and you are back in the session. There is no claude mcp add step and no token to copy.
The connection shows up at uproad.design/settings/personal-tokens as Claude Code（claude.ai）. Revoke it there to disconnect; Claude Code will ask you to sign in again the next time.
Updating from 0.5 or earlier: the stored API token is no longer used. Run /mcp → uproad → Authenticate once after updating. (Tokens still work for CI through the CLI and the GitHub Action.)
What it does
/uproad:new
From meeting notes, a Slack paste, or a one-line idea — with two stops for you along the way:
- 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.
- Writes a spec in Japanese — 背景・目的 / 対象ユーザー / 画面と導線 / 機能要件 / 確認事項 — then stops so you can correct it.
- Builds a self-contained prototype, serves it locally, and stops so you can look at it. Stays in that loop until you approve.
- Asks whether this goes out 公開 (a share link the client opens without an account) or stays 非公開 (visible only to signed-in members of your workspace), then pushes both to Uproad.
The 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.
The 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.
The 確認事項 section is what earns a reply: every assumption made on the client's behalf is written back as a question the client can answer.
The 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.
Where files land
One directory per design, so several sit side by side:
designs/acme-lp/ index.html spec.md billing-dashboard/ index.html spec.md
The local server runs from designs/, so every design is browsable at once.
/uproad:review
When the comments come back:
- Reads the unresolved comments, including where on the page they were pinned
- Applies the change requests, and updates the spec if the behaviour changed
- 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
- Pushes a new version — the share link does not change
- Marks resolved only what was actually done
Questions 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.
Requirements
- Claude Code with plugin support
- An Uproad workspace (the free tier is enough to start)
Guest pinned comments are a Team-plan feature; on Free and Personal the client still opens the link, just without commenting on the page.
Underneath
The plugin talks to Uproad's MCP server at https://uproad.design/mcp (Streamable HTTP, stateless). Sign-in is OAuth 2.1: Uproad is its own authorization server, identifies Claude Code by its Client ID Metadata Document, and hands back a personal token as the access token — so nothing about permissions or workspaces differs from a token you would have pasted by hand. The same server can be added to claude.ai as a custom connector, and the same tools are available to any MCP client — see the MCP docs, or npx uproad for the command line.
License
MIT