Turn a brand brief into deliverables, shot lists, and the right UGC format, catching scope traps.
Connect Ugc to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Turn a brand brief into deliverables, shot lists, and the right UGC format, catching scope traps. The ugc mcp server is what makes that connection.
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.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
interpret_brief — Detected deliverables/specs/usage/disclosure + red flags + the exact questions to confirm in writingget_brief_checklist — The 10 fields every brief must answer before you shootget_ugc_formats — The 7 UGC ad formats (testimonial, problem/solution, unboxing, demo, GRWM, comparison, hook-test-pack) with structurebuild_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 shapecheck_brief_red_flags — Scan for unlimited revisions, perpetual usage, spec work, raw-file grabs, vague deliverables, scope creepget_full_pack — Everything in one payloadugc-brief-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Ugc's toolset — interpret_brief, get_brief_checklist, get_ugc_formats and 4 more — is a fair guide to whether it matches your workflow. It is maintained by closermethod; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| 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 |
```json
{ "mcpServers": { "ugc-brief": { "command": "npx", "args": ["ugc-brief-mcp"] } } }Configuration as documented by the project. Restart the client after saving.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.