Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Turn a brand brief into deliverables, shot lists, and the right UGC format, catching scope traps.
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 …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"ugc-brief": {
"command": "npx",
"args": [
"-y",
"ugc-brief-mcp"
]
}
}
}Run this in your terminal
claude mcp add ugc-brief -- npx -y ugc-brief-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"ugc-brief": {
"command": "npx",
"args": [
"-y",
"ugc-brief-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": {
"ugc-brief": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"ugc-brief-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.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
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.
Runs on your computer; the tool list appears in your AI app after you install it.
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 name was verified with the GitHub account closermethod, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Georgia MCP
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.
An MCP server for Georgian public data, read from the organizations that publish it.
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.
The production layer for UGC creators. Turn a brand brief into deliverables, shot lists, and the right format, and catch the traps before you shoot.
Disclaimer. Structured UGC-production frameworks from documented creator practice. Confirm deliverables, usage, and revisions in writing before shooting. This server plans the work; it never sets or quotes rates.
You landed the deal. Now what do you actually shoot? Most creators (and their AI assistants) jump straight to filming and end up with the wrong format, undefined deliverables, and a "quick revision" that becomes ten. This MCP reads the brief like a pro: what you deliver, in what format, to what spec, and where the scope traps are.
| Tool | What it returns |
|---|---|
interpret_brief | Detected deliverables/specs/usage/disclosure + red flags + the exact questions to confirm in writing |
get_brief_checklist | The 10 fields every brief must answer before you shoot |
get_ugc_formats | The 7 UGC ad formats (testimonial, problem/solution, unboxing, demo, GRWM, comparison, hook-test-pack) with structure |
build_shot_list | A beat-by-beat shot list for a format + coverage rules (shoot the hook 3 ways) |
scope_deliverables | The fields to lock so nothing is left open to interpretation, plus a confirm-message shape |
check_brief_red_flags | Scan for unlimited revisions, perpetual usage, spec work, raw-file grabs, vague deliverables, scope creep |
get_full_pack | Everything in one payload |
npx ugc-brief-mcp
{ "mcpServers": { "ugc-brief": { "command": "npx", "args": ["ugc-brief-mcp"] } } }
Land it (outbound-engine-mcp) → price it (creator-deals-mcp) → produce it (this one) → repurpose it (content-repurposing-mcp). Full catalog: MCP Hub
Elisabeth Hitz — 10+ years enterprise sales, reverse-engineered for creators.
License: MIT