
ClipUGC
io.github.clipugcPublished by GitHub account clipugcv1.4.2Updated Oct 24, 2026
UGC videos for your app with AI influencers who keep the same face. Hosted (OAuth) or local.
Overview
ClipUGC lets an assistant create AI influencers, generate consistent looks and silent reaction clips, and merge them with an app screen recording into finished
- What you can do
- Create and list AI influencer characters, each with a fixed face built from a description and first look, and generate new looks of the same person in different settings, outfits and lighting, then list them. Animate a look into a short silent reaction clip, including motion-control and scene-replace variants. Merge a clip with your app screen recording, a hook text overlay and optional music into a finished 9:16 video, then fetch or download it. Check credit balances and browse hook ideas, with prompts and resources for the pipeline order and pricing.
- When to use it
- Useful for mobile app marketers and creators who want a recurring AI influencer with the same face across many short UGC-style videos, produced from a chat client or terminal instead of a video editor. The hosted server offers a free starting point that makes a few videos from an app store link.
- Requirements
- Hosted option: remote endpoint at clipugc.com with OAuth sign-in, no API key, works on the free plan. Local option: Node.js 20 or newer, the clipugc npm package run via npx, and either a prior auth login or a CLIPUGC_API_KEY from the dashboard; API keys are on paid plans. CLIPUGC_API_BASE_URL only for self-hosted instances. Network access to clipugc.com.
Installation
In SourceWeft
- Open ClipUGC in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.clipugc%2Fclipugc/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"clipugc": {
"type": "http",
"url": "https://clipugc.com/mcp"
}
}
}README
ClipUGC CLI
ClipUGC makes UGC videos for mobile apps with an AI influencer who keeps the same face in every video, with your app's screen recording inside the finished 9:16 video. This repo is its official CLI, local MCP server and Claude Code plugin. Create AI influencers, generate photorealistic looks of the same person, turn them into silent-reaction clips, and put your app recording into a ready-to-post UGC video. Nothing renders locally.
Three ways in:
The hosted server is also the quickest free start: give it an App Store or Google Play
link and its first_videos tool makes three finished videos at no cost.
Requires Node.js >= 20. Create an API key in the ClipUGC dashboard (API keys section). API keys are available on paid plans (Professional and Business). The hosted MCP server needs no key.
Use it with Claude Code
The fastest way in: this repo ships three Claude Code skills, so you describe what
you want instead of learning flags. clipugc drives the CLI conversationally,
ugc-director turns an app idea into a complete UGC video plan, and persona-account
runs an ongoing AI creator account.
Installed as a plugin, the skills are namespaced under it:
(Cloning the repo instead? Claude Code reads .claude/skills/ directly and the
skills are unprefixed, /ugc-director, /persona-account, /clipugc.)
See docs/skills.md for what each skill knows.
Prefer flags? Everything below works standalone, the skills just drive the same CLI.
Hosted MCP server: Claude.ai, ChatGPT, Claude Code, Cursor, VS Code, Gemini CLI
These use the hosted ClipUGC server at https://clipugc.com/mcp (39 tools, OAuth 2.1
sign-in, works on every plan including free). Nothing runs on your machine and there
is no API key to copy: the first call opens a browser so you can sign in with your
ClipUGC account.
Claude Code
Claude.ai: Settings > Connectors > Add custom connector. Name it ClipUGC, paste
https://clipugc.com/mcp, and sign in when Claude asks.
ChatGPT: Settings > Apps (Connectors on older versions) > Advanced > turn on Developer mode > Create. Name ClipUGC, the same URL, authentication OAuth. Developer mode is on Plus and Pro and not yet offered in the EEA, Switzerland or the UK. Step-by-step guide.
Gemini CLI
This adds the hosted server, a short guide (GEMINI.md) and the skills.
Cursor
Once the ClipUGC plugin is listed in the Cursor Marketplace, install it there to
get the server and the skills. Until then, add the server by hand in
Settings > MCP or .cursor/mcp.json:
VS Code (GitHub Copilot agent mode)
Or search @mcp clipugc in the Extensions view once it shows up in the gallery.
Local MCP server (API key): Claude Code, Cursor, Claude Desktop
[smithery badge] Listed on the MCP Registry and Smithery.
The CLI is also a local MCP server with 12 tools, for when you would rather run it on
your machine with an API key than sign in to the hosted one. clipugc mcp speaks the
Model Context Protocol over stdio, so any MCP client can create characters, looks, clips and finished videos as tools,
without shelling out to the commands above.
Log in once so the server has a key (it reads the same ~/.config/clipugc/config.json
the CLI uses):
Claude Code
@latest matters: without it npx reuses any clipugc already installed on
your machine, and a global install older than 1.2.0 has no mcp command, so
Claude Code reports "Connection closed". If you still see that, update the old
install with npm i -g clipugc@latest, or run npx -y clipugc@latest mcp once in
a terminal so the download finishes (Ctrl+C after "12 tools ready"). Do not add
it from inside a checkout of this repo: there npx resolves clipugc to the
local project instead of the npm package.
Cursor (Settings > MCP, or .cursor/mcp.json in your project)
If you would rather not run clipugc auth login on that machine, add an env block
with CLIPUGC_API_KEY set to a key from the dashboard.
Claude Desktop
Claude Desktop installs the server as an extension, so there is no config file to edit and no Node install needed beyond the app itself:
- Download clipugc.mcpb from the latest GitHub release.
- Double-click the file, or open Claude Desktop, go to Settings > Extensions, and choose Install Extension (Advanced settings on some versions).
- Paste your ClipUGC API key when asked. Create one in the dashboard under API Keys.
The extension runs the same clipugc mcp server as above. To build the bundle
yourself, run npm run build:mcpb (see "Local development").
Prompts: make_ugc_video, new_ai_influencer, hook_ideas (ready-made starts for the
common jobs). Resources: clipugc://pipeline (the order of calls) and clipugc://pricing
(documented credit costs; get_credits has the live table).
Tools: list_characters, create_character, generate_image, list_images,
create_clip, create_motion_clip, create_scene_replace_clip, merge_ad, get_video,
download_video, get_credits, list_hooks. Arguments follow the CLI flags (--per-page becomes
per_page). Generation tools return the job id right away, like the CLI without
--wait; poll with get_video (clips and finished videos) or list_images (looks) until the
status is completed. Every tool reports its credit cost in its description, and
get_credits returns the live prices.
What it produces
One character, cast once. Every picture below is the same person, only the setting, outfit and lighting change, because each look is generated from the character's base image rather than from the description again:
Then any look becomes a silent reaction clip. Mouth closed throughout, lip-sync from a still image is the giveaway that a video is AI, so the format is a held expression plus a text hook, not talking:
[A silent reaction clip, the AI influencer glances down at the phone, back up to the lens, and a suppressed smirk forms, mouth closed throughout]Note the shape of that prompt: an arc in beats (glance down → back up → smirk
forms), an explicit no-talking clause, and ambient motion. Ask for a state instead
of a progression, "she smirks", and the face morphs. The full library of ~30
reactions across nine emotion families lives in the
ugc-director skill.
Adding your screen recording and a hook to that clip is free, so the last step costs nothing and you can test as many hooks as you like.
How it works
Every look after the first is generated from the character's base image, so the face stays the same person across an entire campaign or grid. That consistency is the point of the product.
Full pricing: image 2 · clip 7 (5s) / 13 (10s) · motion control 3 per second of
driver video, 2 on --engine wan (capped at 30s) · putting your AI influencer into your own
video (videos replace) 3 per second (capped at 30s) · scene-staged clip 9 (5s) / 15 (10s)
· finished video free.
Charges are duration-aware and refunds return the exact amount charged. Check live
values with clipugc credits.
Quickstart (plain CLI)
Add --json to any command for machine-readable output, and --wait to any
generation command to poll with a spinner until it completes.
Example prompts
The prompt is the product. Below is one of each kind; the full libraries are in
docs/casting.md (9 nationalities) and the
ugc-director skill (~30 reactions across 9 emotion families).
Casting: concrete features → an explicit attractiveness claim → directed makeup and lighting → a realism anchor. All four parts, or the result looks like AI:
Blonde Scandinavian: the fastest way to see what this tool does
Russian: ash-blonde, high broad cheekbones, cool and reserved
Ukrainian: honey-brown, soft oval face, warm and open
Looks: never re-describe the person; the base image carries the face. Change only the setting, outfit and light:
Reactions: an arc in beats, a held ending, ambient motion, and an explicit no-talking clause every time:
Smirk: "I know something you don't"
Jaw-drop: the result reveal
Dreamy cheek-rest: the soft beat a persona grid runs on
Head-shake: "why did nobody tell me"
Hooks: the text burned over the clip. A new hook on the same clip is free, so ship 2-3 variants of every video and let the platform pick:
How it compares
ClipUGC is one of several ways to make UGC-style videos from an AI agent. Two dated comparisons, written by us and with a "skip it if" for each tool, ClipUGC included:
- Best MCP servers for AI UGC videos: ClipUGC, agent-media, VidGuy, UnrealUGC, UGC Copilot and EzUGC on hosting, sign-in, tool count, free use and price.
- Best AI UGC video generators for mobile apps: eight tools, including ReelFarm, Fastlane, UGCdrop, MakeUGC, Creatify and Arcads.
In short: pick ClipUGC when you want one AI influencer with the same face across every video and your app on screen, made from a terminal or a chat, from $14.99 a month with a free plan to start. It does not post for you and has no product-page-to-video flow for online shops.
Documentation
Local development
manifest.json and icon.png at the repo root describe the Claude Desktop
extension. The build script stages dist/, package.json and a production-only
node_modules/ in dist-mcpb/stage/, validates the manifest and packs the bundle.
Its version, name and tool list must match package.json and the MCP server; the
tests check that.
Privacy Policy
This CLI and the Claude Desktop extension do not collect anything themselves. There is no analytics, no telemetry and no crash reporting in the code.
What leaves your machine: your prompts and tool arguments, the files you choose
to upload (photos, app screen recordings, driver videos) and your API key. They are
sent only to clipugc.com over HTTPS, and only to run the request you made. The
API key is stored in ~/.config/clipugc/config.json (CLI) or in Claude Desktop's
extension settings, and is never sent anywhere else.
How the ClipUGC service stores and handles that data, including retention and the AI providers it uses to render videos, is described in the ClipUGC privacy policy: https://clipugc.com/privacy-policy?utm_source=github-readme&utm_medium=integration&utm_campaign=agent-directories.
Questions or deletion requests: [email protected].
License
MIT
Source: README.md at commit 5aef139
Tools
0Version history
5- v1.4.2LatestOct 12, 2026
- v1.4.0Oct 4, 2026
- v1.3.1Oct 2, 2026
- v1.3.0Oct 1, 2026
- v1.2.2Sep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts