Turn a brand brief into deliverables, shot lists, and the right UGC format, catching scope traps.
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
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y ugc-brief-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-closermethod-ugc-brief-mcp": {
"command": "npx",
"args": [
"-y",
"ugc-brief-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceugc-brief-mcpnpmio.github.closermethod/ugc-brief-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.