Makes the video, the images and the audio, and understands the footage it already has.
Built for: The small studio or solo creator producing more media each month than a manual pipeline can carry.
The button opens the checkout, where the 7 servers and 4 skills are listed one by one. Every member is free, so the checkout lists them and asks for no card.
The reason to buy a stack rather than five listings: each line below needs more than one member connected at the same time.
Transcode and assemble video through an API rather than a local render queue.
Generate images from text and iterate on them without leaving the session.
Watch existing footage — frames and audio — and say what is in it, so an archive becomes searchable.
Drive a game engine or a headless Blender check for the parts of production that are assets rather than clips.
What each part contributes, and why it was picked over the obvious alternative. Prices and permissions are read from the listings, so nothing here can disagree with the catalogue.
Video transcoding as an API call, which is what turns a render queue into a step in a pipeline.
Image generation through Replicate's hosted models, for the visual work that does not need a designer's hand.
Drives the Godot 4.x engine, for studios whose output is interactive rather than linear.
Runs Python inside Blender, a background instance with no window included, so a script catches a broken model before it ships in a build.
Extracts frames and audio so existing footage can be described, which is how an archive becomes something you can search.
Structured YouTube data for the published side: what exists, how it is described, and what the metadata actually says.
Text-to-video and image-to-video generation over an OpenAI-compatible API, for the shots that do not need to be filmed.
Ingests video and audio from files, URLs or live feeds and returns real-time context, which is the searchable-library half of a studio.
Video as React — twenty-nine rules covering animation, captions, audio and transitions — for output that has to be produced the same way every week.
Generates MIDI with real music theory behind it, for the soundtrack that would otherwise be a stock loop.
The calendar and the platform-specific plan, so production serves a schedule instead of producing whatever was interesting that week.
Every member is free, so the monthly figure is $0 whatever you do with the stack: nothing here is billed by the call, and only adding a paid member could change it.
| Part | What you are paying for | Monthly, as quoted |
|---|---|---|
| Ffmpeg Micro | Free | — |
| Replicate Flux | Free | — |
| Godot Mcp Runtime | Free | — |
| Blender Remote | Free | — |
| Claude Video Vision | Free | — |
| YouTube | Free | — |
| Agnes Video | Free | — |
| Skills | ||
| VideoDB | Free · context cost only | — |
| Remotion Video Creation | Free · context cost only | — |
| MIDI Generation | Free · context cost only | — |
| Social Media Strategy | Free · context cost only | — |
| Everything above | $0 of servers plus $0 of skills, the same in a quiet month and a busy one | $0/mo |
Subscriptions at their monthly plan price; one-off licences spread over 12 months.
Install only these and the bill is nothing: 7 servers and 4 skills, and all 40 tools.
Nothing in this stack carries a call allowance, so nothing here can run out before the month does. The bill is decided when you install it, not when you use it.
The spend cap is one figure for the whole account, set in your dashboard and checked when an order is placed. On the call path what stops a retry loop is the plan's call allowance and its rate limit, and a refused call is never billed.
The steps below come before the install lines: what to decide and scope before connecting anything, in the order it matters. The lines themselves follow, part by part, for the client you pick.
npx mcprush@latest stack add media-studio writes all 7 servers into Claude Code’s config in one go — or run the lines below one by one. The 4 skills are not included — add them with lines 08–11.
FFMPEG_MICRO_API_KEY — API key from https://www.ffmpeg-micro.com/dashboard/api-keysREPLICATE_API_TOKEN — Your Replicate API tokenAGNES_API_KEY — Your Agnes API keySet them where you start Claude Code — export FFMPEG_MICRO_API_KEY=… in your shell profile on macOS and Linux, setx FFMPEG_MICRO_API_KEY "…" on Windows, then open a new terminal. Claude Code reads them at start; the config keeps only the names.
# 01 · Ffmpeg Micro
claude mcp add --scope user --env 'FFMPEG_MICRO_API_KEY=${FFMPEG_MICRO_API_KEY}' --transport stdio ffmpeg-micro-mcp '--' npx -y @ffmpeg-micro/mcp-server
# 02 · Replicate Flux
claude mcp add --scope user --env 'REPLICATE_API_TOKEN=${REPLICATE_API_TOKEN}' --transport stdio replicate-flux-mcp '--' npx -y replicate-flux-mcp
# 03 · Godot Mcp Runtime
claude mcp add --scope user godot-mcp-runtime '--' npx -y godot-mcp-runtime
# 04 · Blender Remote
claude mcp add --scope user blender-remote-mcp '--' uvx blender-remote
# 05 · Claude Video Vision
claude mcp add --scope user claude-video-vision-mcp '--' npx -y claude-video-vision
# 06 · YouTube
claude mcp add --scope user youtube-mcp '--' npx -y @kirbah/mcp-youtube
# 07 · Agnes Video
claude mcp add --scope user --env 'AGNES_API_KEY=${AGNES_API_KEY}' --transport stdio agnes-video-mcp '--' npx -y @kira4094/agnes-video-mcp-server
# 08 · VideoDB
npx mcprush@latest skill add video-db/videodb
# 09 · Remotion Video Creation
npx mcprush@latest skill add agenticweb/remotion-video-creation
# 10 · MIDI Generation
npx mcprush@latest skill add tubone24/midi-generation
# 11 · Social Media Strategy
npx mcprush@latest skill add thatrebeccarae/social-media-strategynpx).uvx, docs.astral.sh/uv).Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither.Nothing is connected until you approve it in Claude Code. mcprush is not in the path and meters nothing here.
Installed together, these tool surfaces add up. It is the first thing a security reviewer asks for, so what has been counted — and what nobody has counted yet — is on the page rather than in a PDF.
| Member | Tool surface | Write tools |
|---|---|---|
| Ffmpeg Micro | imported | 6 |
| Replicate Flux | imported | 6 |
| Blender Remote | imported | 3 |
| Claude Video Vision | imported | 2 |
| Agnes Video | imported | 1 |
| Godot Mcp Runtime | not imported | not recorded |
| YouTube | not imported | not recorded |
A stack's blast radius is the union of its members, not the worst of them. That union cannot be taken here, because 2 members of 7 have no imported tool surface — so the figure a review asks for is missing rather than low, and a member marked not imported is one nobody has counted rather than one that cannot write.
A stack is a default, not a verdict. These are the substitutions the maintainer would make, and what each one costs or saves.
A different generation backend with a different look and a different bill; keep the one whose output you actually ship.
The same generated-shot job through another provider, for teams whose access is there rather than to an OpenAI-compatible endpoint.
Written by the maintainer, kept on the page rather than in a support thread.
It cannot clear rights. Generated and ingested media carry licence questions this stack does not answer.
It does not publish on its own. YouTube here is read: metadata and data, not uploads under your name.
Render costs are real. Every video and image member bills per job, and a revision loop is the fastest way to spend a month's budget.
A stack has an owner: whoever keeps it re-checks the combination when a member changes, and the members themselves are published by the people named on each row.
Works inside a Godot project and Blender — scenes, scripts, tests, exports — and play-tests the build instead of guessing.
Tools to inspect code changes, run checks and prepare a pull request review.
Tools to investigate a bug report and work toward a reproducible test case.