Claude Code & Cowork + UnrealUGCUGC video, from any Anthropic agent.
Connect Claude Code or Claude Cowork to UnrealUGC via MCP. One config, two agents — generate ultra-realistic UGC video ads from your terminal, your desktop, or both. Same UNREALUGC_API_KEY, same eleven tools.
Add UnrealUGCwith one command
Claude Code's MCP plumbing handles the rest. After the command below, the new generate_video tool is available in your session.
claude mcp add unrealugc \
--env UNREALUGC_API_KEY=usk_live_... \
-- npx -y @unrealugc/mcpWant it project-scoped instead of user-scoped? Drop a .mcp.json into your repo with the same shape — Claude Code picks it up automatically.
Same MCP config.Desktop, not terminal.
Claude Cowork is Anthropic's desktop agent for knowledge work — it reads, edits, and creates files in folders you authorize. The MCP plumbing is identical to Claude Code, so UnrealUGC plugs in the same way.
Cowork settings → Tools & MCP servers → Add server
{
"mcpServers": {
"unrealugc": {
"command": "npx",
"args": ["-y", "@unrealugc/mcp"],
"env": {
"UNREALUGC_API_KEY": "usk_live_..."
}
}
}
}Once added, Cowork can call generate_video in the middle of a longer knowledge-work task — e.g., research a product, draft launch copy in a local file, then ship three UGC ad variations, all in one autonomous run.
A UGC studiowherever Claude lives.
Claude Code is built for terminal-driven agentic work. Cowork brings that same loop to your desktop and local files. UnrealUGC plugs into both.
Generate ads without leaving your terminal
You're in a tmux split shipping code. Ask Claude Code for a new ad. It runs the MCP tool, prints the job id, and pings you when done. No context switch.
Wire UGC into your release pipeline
Claude Code already orchestrates your repo work. Pair it with UnrealUGC and have it auto-generate a launch video the moment you tag a release.
Loop with /loop
Use Claude Code's /loop skill to batch-generate variations. Five creators × three hooks, all running in parallel, results aggregated when complete.
Subagent fan-out
Spawn an agent per ad variation with the Agent tool. Each one calls UnrealUGC, polls, and reports back to your main session.
Knowledge-work pipelines with Cowork
Cowork reads your brand brief from a local folder, drafts launch copy in a Google Doc, then calls generate_video — all in one autonomous task.
One key, both agents
Use the same UnrealUGC API key in Claude Code and Cowork. Switch between terminal-driven and desktop-driven workflows without re-configuring anything.
Example workflow
Launch video on every release
Drop this into a Claude Code skill or as a hook. Every time you tag a release, Claude Code reads the changelog and generates a fresh launch ad.
---
name: release-ad
description: Generate a launch ad whenever a new git tag is pushed.
---
When a new tag is pushed:
1. Read CHANGELOG.md and summarize the headline feature in one line.
2. Use list_creators to pick a creator that matches our brand (filter
gender, age, accent).
3. Call estimate_video_cost first — abort if it exceeds 500 credits.
4. Call generate_video with kling-2.6, useNativeAudio=true, 9:16, 12s.
5. Poll get_video every 30s. When status is COMPLETED, print outputUrl
and post to #launches on Slack via the slack MCP server.MCP. Stdio.Nothing fancy.
Claude Code launches the UnrealUGC MCP server in a child process on demand. It reads your API key from env, exposes 11 tools, and tears down when the session ends.
01
claude mcp add
Claude Code stores the config in ~/.claude/mcp.json (user scope) or .mcp.json in the repo (project scope).
02
Tools auto-register
When you start a session, Claude Code spawns the server and reads the tool catalog. No restart needed for new tools.
03
Ask, generate, ship
Claude Code picks the right tool based on your prompt. Generation runs async; webhook pings you when ready.
Questionsfrom Claude Code users
- Does this work with Claude Code's project-scoped MCP config?
- Yes. Drop a .mcp.json into your repo root and Claude Code loads it automatically when you cd into the project.
- Can subagents call UnrealUGC?
- Yes. The Agent tool spawns subagents that inherit the parent session's MCP servers. Each subagent sees every UnrealUGC tool.
- Will Claude Code burn through credits when I'm not paying attention?
- It can't generate without explicit instruction. UnrealUGC also enforces a 10 generation/minute per-key rate limit. For paranoid usage, create a separate key for Claude Code with a credit pack cap.
- How do I share an UnrealUGC config across my team?
- Commit a .mcp.json with the command + args, but keep UNREALUGC_API_KEY in each developer's local environment via Claude Code's --env flag.
- Can I use this with Claude Code on a remote VM?
- Yes. The MCP server runs via npx wherever Claude Code does. SSH, devcontainer, GitHub Codespaces — all fine.
- Does Claude Cowork need a different API key?
- No. Use the same UnrealUGC API key in Cowork as you do in Claude Code. Tools, rate limits, and credit balance are shared per key.
- Will Cowork see my local files when generating ads?
- Only the folders you authorize. Cowork follows Anthropic's permission model — UnrealUGC itself never reads your files. We only receive the explicit arguments Cowork passes to each MCP tool call.