Connect once, then just ask. Claude writes the script, generates the narration and visuals, and hands back a finished video — without you opening a timeline, a browser tab, or this app.
The two ways to use it: on its own, or entirely through Claude.
When you ask Claude for a video, it does not generate one straight away. It first calls
get_video_options and shows you the choices — shape, where the pictures come
from, AI still quality, motion, look, voice and length — with what each one costs.
This matters because the choices are not equally free. Stock footage and stock images cost nothing. AI stills spend your Pollen, one generation per scene. And High or Maximum still quality needs a Pollinations tier that authorises them — having a balance is not the same thing, and a request your tier refuses comes back as a payment error and quietly falls back to stock.
If you have already said what you want — “a vertical one with free stock footage” — or you tell Claude to just get on with it, it will use your answer and sensible defaults rather than asking twice.
Most AI video tools are a website you sit in front of. That is fine for one video. It stops being fine when video is a recurring job — a weekly explainer, a product update, fifty localised clips — because every one of them costs you a context switch.
Talking to Claude removes the app from the loop. You are already in a conversation about the thing the video is about; the video becomes one more sentence in it. And because Claude can call the tools directly, it can do the follow-up work too: check on the render, look at the scenes, drop the one that missed, and re-cut.
https://automatedvideoapp.com/mcp and leave Authentication on its
default.Once connected, these are ordinary sentences, not commands to memorise:
Behind those sentences are ten tools: fetch the film production guide, show the options and what each costs, create a video, check its status, list its scenes, remove scenes, set the end card, re-cut, list the images you have uploaded, and join finished videos into one longer film. The editing ones are the interesting part — editing by conversation rather than by dragging blocks around.
Every video is kept as separate scene clips, each carrying its own picture and its own narration. So removing a scene is a re-stitch of clips that already exist, not a new render. It takes seconds, costs nothing, and the removed scene is kept — ask for it back and the video is rebuilt with it.
Chat is one entry point. The same pipeline runs unattended:
| Schedules | Generate daily or weekly, optionally publishing to your own YouTube channel as each one finishes. |
|---|---|
| Series | Plan a multi-part run — “six parts, one a week”. Each episode knows it is part 3 of 6, so it builds on the last instead of repeating the introduction, and the schedule switches itself off after the final part. |
| REST API | POST /api/videos with your API key, from a script,
Make, Zapier or n8n. Same engine, same metering. |
| Webhooks | Get a signed callback when a render finishes, so your own system can take it from there. |
The point of all of it is the same: the video pipeline should run whether or not anyone is watching it.
Stock footage and stock images are unlimited and free. AI stills, AI-video hybrid and full AI video run on Pollen you connect yourself, so you set your own ceiling with your own provider and we never sit between you and that bill. Nothing here charges per seat.
More guides: vertical video for TikTok, Reels and Shorts · turning a script into a video.