Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Verified lessons for your project's packages and versions, and free React components to install.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://upfork.dev/mcpRun this in your terminal
claude mcp add --transport http upfork https://upfork.dev/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"upfork": {
"url": "https://upfork.dev/mcp"
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"upfork": {
"type": "http",
"url": "https://upfork.dev/mcp"
}
}
}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.
ChatGPT connects only to servers on the internet:
https://upfork.dev/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.
install_productPut an UpFork component or landing page into the user's React + Tailwind CSS project. Answers short: the one-line `npx shadcn@latest add` command that installs it all, the product's AI summary (its entry point, key props and one example), the npm packages and shadcn/ui components
sign_inOnly when the user wants something that needs their UpFork account: saying a lesson worked or didn't, their account, installing a product that isn't free, a product's AI prompt, support tickets, their profile and résumé, articles, lesson drafts or team lessons. Ask the user first
search_lessonsLessons alone, from UpFork's published articles: what a developer or their AI learned building a product that they didn't know before, verified on it (what was assumed, what happened, why, the fix, the evidence), without reading the articles. Before building or fixing something,
preflightCall it at the start of work, before writing code: send a sentence about the task and, once the project has a package.json, its dependencies and devDependencies as they are (or one name → version map). In an empty folder the sentence alone is enough: it finds the lessons about th
view_productOne UpFork product by its slug (from search_products, or its address upfork.dev/products/ ). It answers short: the product's AI summary first (what it is, the install line, the entry point, the key props, one example, which files to read next, related lessons: about 1,500 charact
read_product_fileOne file of an UpFork product's live code, its lines numbered exactly as an article's ::file{path lines} block counts them (400 lines a call), or, without path, the list of its files and their lengths. The code anyone may read on the product's page: free products' for everyone, t
search_productsSearch UpFork (upfork.dev): React + Tailwind CSS components (installed with the shadcn CLI), landing pages, full-stack projects and mobile (React Native) components. Describe what's wanted in plain words ("a pricing table with a yearly switch", "testimonials that scroll"); typos
get_lessonOne lesson by its number (L-7KQ2, from search_lessons or its address upfork.dev/lessons/ ), whole: what was assumed, what happened, why, the fix and the evidence; with short hits of related lessons about the same packages or from the same article (get_lesson reads any of them). N
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 7, 2026
The registry lists no source repo, so we cannot match the publisher (upfork.dev) to the code
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 450 ms (HTTP 200)
No sign-in needed
Read 8 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 2 of 3 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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.
The GitHub repo last changed –, and the latest version (1.13.1) reached the registry yesterday.
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.
In the same category: Spec Driven Development, Remote Desktop Commander, ScienceShot science reference
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
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Sourced, citable answers in radiation and particle physics, photonics, electronics and quantum.
No README found in the repo