VIDEO BATCHER / AGENCY / AUTOMATION

Agency automation setup guide

Download videos to use in the editor, or connect your own AI to write captions, create variations and prepare batches. Once you turn on AI access, it can use files anywhere on your computer or drives that you point it to and save new files where you say, or in VideoBatcher Exports. Your originals stay untouched; VideoBatcher does the rendering on your computer.

Requires a verified Agency subscription, eligible Agency trial or invited beta access Back to Agency overview Upgrade an eligible Standard subscription

These instructions are for VideoBatcher 3.10.0 on Windows and Mac. If your AI Connection screen does not show the four AI choices, download the latest installer and update your app. Updating this website does not update your installed app.

What it can do

Ask your AI to write and add captions, create variations, reuse your saved presets and prepare batches. MCP (Model Context Protocol) is the connection that gives a compatible AI client access to VideoBatcher's tools. You choose the presets it may use, where finished files go, and whether each batch needs your review before rendering.

Works with the AI you already use, on Windows and Mac: Claude Desktop connects with a one-click extension, and ChatGPT, Gemini and Perplexity connect by pasting a private VideoBatcher link into the app's connector settings. In VideoBatcher open AI Automation → AI Connection, choose your AI and follow the on-screen steps. Keep VideoBatcher open while your AI works; your files and rendering stay on your computer, and you use your own AI account.

Captions, variations and organized exports

With an updated desktop build, ask your AI to find your media, add captions, make more versions and organize the finished videos in export folders — without typing every folder path.

Everything renders on your machine

VideoBatcher imports and renders on your computer. Optional AI media sharing sends sampled frames through your connected AI client; it is OFF until you enable it.

You choose the AI

Connect your own AI and let it do the work. Use a compatible AI client or local model to prepare and submit batches within your approved settings, with rendering on your computer.

You decide how much oversight

Review first shows you every resolved job before it renders. Automatic runs submitted jobs right away, using your saved presets and limits.

How it works

Claude Desktop starts a separate local companion included with VideoBatcher. ChatGPT, Gemini and Perplexity send requests through your private VideoBatcher link; the open desktop app answers them using the same tools and permissions. No customer-hosted server, terminal or extra AI API key is needed for these four setup options. You bring your own AI account, which makes its own model calls. If you separately allow AI media sharing, it can also request sampled images from a video.

Heads up: the connector keeps media and rendering local, but a cloud AI client may send your brief, filenames, captions and tool results to its provider. That provider is a separate privacy boundary, subject to its own terms. Local rendering does not mean the model runs offline; use a local model/client if that distinction matters for your project.

Download videos without connecting an AI

Downloads requires verified Agency access, but no AI connection or AI permissions. Only download content you own or have permission to use.

  1. Open the dedicated Downloads tab in the desktop sidebar. Paste public Instagram post/Reel links or TikTok video links, one per line, then click Find videos.
  2. Choose from the results using thumbnails or checkboxes. You can multi-select, use Select all, or Clear selection. A single result is selected for you. If a preview is unavailable, the app shows that rather than inventing an image.
  3. Click Choose download folder… to save in your chosen folder, or keep the app's default download folder. Click Download selected; only checked videos are downloaded. Changing the folder affects new batches only.
  4. Select completed files and click Use in editor to repurpose them with your usual effects, captions and presets. This adds them to your media list and opens Effects; nothing renders until you click Generate. You can also follow progress, show a completed file in its folder, or cancel remaining downloads.

To use downloaded files in AI batches later, just tell your AI where they are. Downloads your AI starts go to Downloads › VideoBatcher Imports unless you ask for another folder.

Supported links and platform limits

Use public HTTPS links. Supported shared-link forms include instagram.com/share/reel/…, instagram.com/share/p/…, vm.tiktok.com/…, vt.tiktok.com/… and tiktok.com/t/…. These are link formats, not a promise that every public video can be downloaded.

Instagram account discovery is not supported; use individual post or Reel links. TikTok profile discovery is best effort only. Platforms may block downloads or withhold thumbnails and performance counts. Private content and passwords are not supported. If Instagram asks you to sign in, the Downloads tab offers an optional browser-session setting that you must approve yourself; only Instagram cookies are used locally, not sent to your AI or VideoBatcher's servers. This does not guarantee a download will succeed. Errors are shown rather than guessed, and unavailable metrics cannot reliably tell your AI which video performed best.

Desktop setup

The steps below are identical on macOS and Windows — automation lives inside the same VideoBatcher desktop app you already use.

  1. 1.
    Activate your Agency access. Automation needs verified Agency access, including an eligible Agency trial or invited beta access. Standard alone and the free desktop trial do not unlock it. Activate your license in VideoBatcher, not in your AI chat.
  2. 2.
    Open AI Automation → AI Connection. Use the desktop app to approve access and review jobs. Keep VideoBatcher open while using a private-link connection. Claude Desktop starts a separate local companion, which must stay running for the jobs it owns. There is no always-on background rendering service.
  3. 3.
    Set up AI access once. Click “Set up AI access…” and confirm. Your AI can use files anywhere you point it to and save finished files where you ask—including supported external and synced folders. There are no folder lists to maintain. When you don't say where, files go to VideoBatcher Exports; you can change this default folder in Settings. Originals and hidden, private and system folders stay protected.
  4. 4.
    Choose how batches run. The setup confirmation enables Automatic mode and creates Agency Starter. Valid jobs can then start without per-job approval. To check every job yourself, choose “Review before running” in Settings and save before asking your AI to submit work. You can also change the default folder, presets and limits there. Agency Starter allows small brightness, contrast and saturation adjustments; your AI can add captions per job.
  5. 5.
    Choose your AI and follow its steps. Under “02 / Connect your AI,” choose Claude, ChatGPT, Gemini or Perplexity. Install the Claude Desktop extension or add your private VideoBatcher link in the other app's connector settings. Then ask your AI to call videobatcher_resources. Creating an extension or link does not mean the AI is connected yet.
  6. 6.
    Ask your AI to make a small batch. Use the example request below to find a clip, add captions and make two versions. In Review first, check the job before approving; in Automatic, watch progress directly. Your AI cannot approve a job, change modes or grant itself new permissions.
  7. 7.
    Track, inspect, or cancel. Closing the desktop app cancels the jobs it owns rather than leaving anything rendering unattended.

Note: saving new permissions or configuration cancels any jobs already running and invalidates pending ones — they'll need to be resubmitted.

Connect your AI

In VideoBatcher, open AI Automation → AI Connection → 02 / Connect your AI. Complete Quick setup or review Settings first, then choose your AI. All four options use your saved settings, default folder and job limits. You need your own eligible AI account; provider availability and account rules can change.

Claude Desktop

Use the Claude Desktop app on Windows or Mac, not Claude on the web or phone. It connects directly to your computer—no private link or manual configuration needed. Your organization may restrict custom extensions.

  1. Select Claude in VideoBatcher and click Create Claude extension…. Save the VideoBatcher-Claude.mcpb file.
  2. In Claude Desktop, open Settings → Extensions → Advanced settings → Install Extension, choose the saved file and approve installation.
  3. Start a new Claude chat and ask: “Check my VideoBatcher connection using videobatcher_resources.”

Check Claude connection in VideoBatcher reports whether Claude has reached the tools. Creating the file alone is not a connection. Disable or remove the extension in Claude to disconnect.

ChatGPT

Requires Plus, Pro, Business, Enterprise or Edu with Developer mode available. Create the connector on chatgpt.com; it can then be used in ChatGPT's apps. Workspace restrictions may apply.

  1. Select ChatGPT, create and copy your VideoBatcher link. Keep VideoBatcher open: ChatGPT tests the link immediately.
  2. On ChatGPT's website, open Settings → Apps & Connectors → Advanced settings and turn on Developer mode. Choose Create (or +), name it VideoBatcher, paste your link as the MCP server URL and choose No authentication.
  3. In a new chat, open + → Developer mode and enable VideoBatcher. Ask: “Check my VideoBatcher connection using videobatcher_resources.”
ChatGPT setup and account requirements

Gemini

Google currently limits custom apps to personal accounts (not work or school), age 18+, in the United States, with Keep Activity on. Set it up on the web; Google also supports using connected custom apps on mobile.

  1. Select Gemini, create and copy your VideoBatcher link, and keep VideoBatcher open.
  2. In Gemini on the web, open Settings → Connected Apps → Add a custom app. Paste your link as the MCP server URL and connect it.
  3. In a chat, type @, choose VideoBatcher and ask: “Check my VideoBatcher connection using videobatcher_resources.”
Gemini custom-app requirements

Perplexity

Custom connectors are available in Perplexity's web and Windows/Mac desktop apps. Organization accounts may need an admin to allow custom connectors.

  1. Select Perplexity, create and copy your VideoBatcher link, and keep VideoBatcher open.
  2. Open Account settings → Connectors → + Custom connector. Name it VideoBatcher, paste the link as the MCP server URL, choose Authentication: None and save.
  3. Enable the connector and ask: “Check my VideoBatcher connection using videobatcher_resources.”
Perplexity custom-connector help

Your private link is a password

One VideoBatcher link can be used with ChatGPT, Gemini and Perplexity. Add it in the AI app's connector settings—not in a chat message. Anyone with the link can use your VideoBatcher tools with the same file access as your AI. Do not share it publicly or send it to support. Creating a new link replaces the old one; reconnect any apps that used it. Click Stop sharing this link in VideoBatcher to revoke it.

Requests and tool results travel over encrypted connections through VideoBatcher's link service. Delivered messages are deleted; your media files and rendering stay on your computer. Cloud AI providers still handle prompts and tool results under their own terms. Optional media sharing remains off until you approve it.

Check the connection before running a batch

Creating a link is not the same as connecting your AI. Listening means the desktop app can reach the link service; it does not prove your AI has used the tools. The status shows when an AI app last reached VideoBatcher. Ask it to call videobatcher_resources before trying a batch. If tools are missing, check your account eligibility, the connector's settings and that VideoBatcher is open with Agency access. Do not ask the AI to guess file paths.

AI workflows are still being tested. Native builds and automated connection tests do not prove that every provider account or region works. If Gemini rejects the link or asks for unsupported authentication, contact us with the error instead of sharing credentials.

What you can ask your AI

  • “Check my VideoBatcher connection and tell me my default folder and which saved settings I can use.”
  • “Make 5 variations of every video in my Clips folder with my Reels settings, each with a different caption about our summer sale.”
  • “Download these two public TikTok videos, then create 3 captioned variations of each for Instagram.”
  • “Write 10 short, upbeat captions for a gym promotion and run them across the videos in my Promo folder; let me review before rendering.”
  • “Show me the status of my last job and tell me where the finished videos were saved.”
  • “Cancel the running job and explain what was already finished.”

Replace folder and preset names with your own. You can copy these from “03 / What you can ask your AI” in VideoBatcher. To require approval for every batch, choose Review before running in Settings first; the AI cannot change your mode.

Advanced / other AI clients: manual MCP & Codex setup

These manual settings are optional. Claude Desktop can use the extension above. ChatGPT, Gemini and Perplexity use the private link, not this local configuration. Codex is a separate product from ChatGPT.

MCP is how your AI client talks to the VideoBatcher companion running on your computer. Open AI Automation → AI Connection → Show Advanced / other AI clients in the desktop app, choose Generic JSON or Codex TOML, then copy its generated configuration into the matching AI client's MCP settings using Copy MCP config. The app supplies the real executable path from your installation; the examples below are only illustrations. Your AI client must support local stdio MCP servers.

Generic JSON (for clients that use mcpServers):

{ "mcpServers": { "videobatcher": { "command": "/absolute/path/to/VideoBatcherAutomation", "args": ["mcp"] } } }

Codex (~/.codex/config.toml; on Windows, the equivalent file in your user profile):

[mcp_servers.videobatcher] command = "/absolute/path/to/VideoBatcherAutomation" args = ["mcp"]

On Windows the packaged companion is VideoBatcherAutomation.exe; on macOS copy the exact companion path shown in the desktop app. Running from source instead uses Python and the automation script as arguments. After adding the configuration, restart or reload your AI client. Click Test local MCP in VideoBatcher to check the companion executable and handshake. A successful local test does not mean Codex or another client has loaded that config. Check the client's MCP tool list next. Visiting this website or giving its URL to your AI will not connect the local tools. No network port, VideoBatcher API key or model credential is needed by the local connector.

Example instruction to give your AI client

“List your VideoBatcher tools. Call videobatcher_resources, then browse_media to find my videos in Downloads. Make two versions of one clip with a short caption using Agency Starter, save them under VideoBatcher Exports, validate the job, then submit it. Show me the job status. If the tools are missing, tell me the connection failed instead of guessing folder paths.”

A client that only accepts a remote server URL cannot use this local stdio connection directly. Generic JSON is for clients that accept the mcpServers format; it is not a universal config for every AI app. Use your client's documented MCP settings, not its chat box.

If no VideoBatcher tools appear, check that the installed companion exists, use Test local MCP, paste the matching config into your AI app, and restart that app. If a job fails validation, ask the AI to show the exact error; try one supported clip first. Local MCP works only while its companion is running.

Available tools

Tool Purpose
videobatcher_resourcesShows the setup status, default folder, presets, limits, and job schema
videobatcher_browse_mediaLists supported media in any folder you point it to, one folder at a time; never hidden, private or system folders
videobatcher_create_output_folderCreates a new folder where you ask your AI to save finished files
videobatcher_delivery_manifestReturns verified completed local files for your AI's upload connector. Does not upload or confirm cloud delivery.
videobatcher_discover_mediaDiscovers supported public video links and available metadata. Instagram profile discovery is currently unsupported: use individual post/Reel links. TikTok profile discovery and performance counts are not guaranteed.
videobatcher_start_importStarts a local batch download. Never accepts social passwords or cookies from the AI; an optional Instagram session must be approved in the desktop app.
videobatcher_list_imports / import_status / cancel_importTracks import batches, completed input files and errors; cancels remaining work.
videobatcher_inspect_videoReturns timestamped sampled frames after separate AI media sharing consent. Not full video or audio analysis.
videobatcher_validateChecks a proposed job without starting rendering
videobatcher_submitStarts a job in Automatic mode, or queues it for your desktop approval in Review first
videobatcher_jobsLists jobs
videobatcher_statusShows the status of one job
videobatcher_previewGenerates local previews and returns local file paths only
videobatcher_cancelCancels a job

There is no tool to delete originals, run shell commands, approve a job, change modes, or grant permissions. Browse and export access stays inside the scope you confirm on the desktop.

Automatic vs. Review first

Review first

Every job waits for you to check its files, save folders, captions, and local previews in the desktop app before it renders. Choose “Review before running” in Settings while you're getting comfortable. Guided setup starts in Automatic, so change and save this before submitting your first job if you want to review it.

Automatic

Valid jobs start rendering as soon as they're submitted, using the presets you've already approved — no per-job click needed. Uses the same safety checks, cancellation handling, and renderer restrictions as Review first.

Previews are capped at the first 24 outputs per job. In Review first, larger jobs will flag that the remaining outputs weren't visually previewed — keep jobs smaller if you want every output checked before approval.

Advanced: job format (multi-folder example)

You do not need to type JSON or folder paths for the guided setup: ask your AI to call resources and browse_media, then use the real paths it returns. For advanced manual setups, a job describes sources, where finished files go, and caption settings. The example below is illustrative; your AI must replace every path and preset with values returned by your installed app.

{ "version": 1, "preset_id": "My approved preset", "sources": [ {"path": "C:/Clients/A/Raw/clip.mp4"}, {"path": "C:/Clients/B/Raw", "discover": true, "recursive": false} ], "routes": [ {"source_root": "C:/Clients/A/Raw", "destination": "C:/Clients/A/Exports"}, {"source_root": "C:/Clients/B/Raw", "destination": "C:/Clients/B/Exports"} ], "variations": 2, "seed": 42, "captions": { "texts": ["One small change. A different perspective.", "Make your next idea happen."], "selection": "sequential", "style": { "size": 0.06, "min_size": 0.025, "width": 0.84, "margin": 0.04, "anchor": "bottom-center", "wrap": true } } }

Say “Save 10 versions in D:/Clients/Summer.” The AI can create the destination without a settings step. Each job writes a new dedicated subfolder, leaving originals and earlier outputs untouched.

For “Upload the finished versions to my connected Drive folder,” your AI needs its own authenticated connector that can upload local files. VideoBatcher supplies a delivery manifest marked local_ready_not_uploaded; it does not include built-in Drive/Dropbox OAuth or upload support. The AI must obtain the provider's confirmation before saying “uploaded.” Saving in a synced folder also does not prove cloud synchronization.

Prefer the command line?

CLI is the command-line option for the same automation, useful for scripts. Run it from source or use the packaged VideoBatcherAutomation executable:

python -m agency_automation --help python -m agency_automation resources python -m agency_automation validate job.json python -m agency_automation submit job.json --idempotency-key campaign-001 python -m agency_automation jobs python -m agency_automation status JOB_ID python -m agency_automation preview JOB_ID python -m agency_automation cancel JOB_ID

On the packaged install, replace python -m agency_automation with the full path to VideoBatcherAutomation (.exe on Windows). There are deliberately no approve, configure, or enable commands — permissions and approval always happen in the desktop app.

An Automatic CLI submission keeps that command running until rendering stops; do not close it mid-batch. In Review first it queues the job for desktop approval. Download, folder-browsing and inspection tools are available through MCP, not as additional CLI subcommands.

Presets & supported features

Guided setup provides Agency Starter so you can try a simple batch without creating a preset. It enables bounded brightness, contrast and saturation adjustments (−3 to +3); ask your AI to add captions in the job. For advanced results, save and approve your own preset in the desktop app. Jobs carry its supported video/image settings:

VideoBatcher 3.10.0 also supports these features from an approved saved preset. Configure them manually in VideoBatcher first:

  1. Configure the features in the desktop app and save a preset.
  2. In Automation, approve that preset. Its audio, logo and font files are used wherever you saved them.
  3. Ask your AI client to use that preset by name. Start with a small job in Review first mode.

Turning a feature on in the manual workspace alone does not apply it to MCP jobs: automation starts from the saved preset, not unsaved controls. Your AI can adjust supported audio, watermark, and device-profile settings for a job using the preset's assets. Enabled features stay on; the AI cannot switch them off or enable disabled features. Each job records the resolved settings for review and checks its referenced files again before execution.

Per-job adjustments (feature_overrides)

A job can nudge the approved preset's audio, watermark, and device-profile settings for that job only — without changing what's saved on the preset itself:

{ "feature_overrides": { "audio_pool": {"mode": "mix", "volume": 65, "duck": 30, "selected_track_indexes": [0]}, "watermark": {"image": {"opacity": 80, "position": "bottom-right"}}, "device_profile": "Apple iPhone 15 Pro" } }

Overrides can only stay inside what the preset already enabled — they can't turn a disabled feature on, turn an enabled one off, or swap in a new logo/audio file.

Let your AI use a caption pool

Ask your AI to write several captions and rotate them sequentially or randomly across outputs, or explicitly use the selected captions saved in your approved preset. It can also assign captions to particular outputs. This does not edit your desktop caption library. Omitting captions means no caption is added.

Caption timing

By default a caption stays visible for the whole final video. For video jobs, captions.timing can instead show it for just a range or the final few seconds of the finished output (after any trim/speed changes) — useful for a call-to-action that should only appear near the end:

{"timing": {"mode": "last", "duration": 3}}

{"mode": "range", "start": 2, "duration": 3} shows the caption for a specific window instead. Timing is video-only — a job cannot request non-whole timing for a still image, and images ignore this field.

Example request

“Read my approved preset resources. Keep audio, watermark, and device profiles enabled. Lower the background music, adjust the watermark position, and choose a supported device profile. Write a pool of five captions, rotate them across the variations, and show the caption only for the last 3 seconds of each video. Validate the job and show me the resolved settings before submission.”

Update older builds: VideoBatcher 3.10.0 supports approved saved presets with audio pools, watermarks and Device Metadata Profiles through automation. Older builds may reject these features. Install the latest version before following this guide.

Audio pools cannot be applied to still images; use a separate preset without audio for image jobs. Missing assets and unsupported settings produce an error, rather than silently dropping a feature. Your normal manual desktop workflow is unchanged.

Still images with Device Metadata Profiles enabled export as JPEG to retain device EXIF metadata; images with profiles off remain PNG. Previews are still images, so they do not play audio. Video previews apply the saved effects before extracting a frame and may take longer to generate.

A few other things automation doesn't do yet: video/audio-only effects (zoom, trim, speed, pitch) on image inputs, or characters outside the current default/emoji fonts — both return an explicit error instead of a silent workaround.

Safety & things to know

Does connecting an AI unlock Agency?

No. Installing an extension or creating a private link does not grant a subscription or file access. Automation requires online verification of eligible Agency access (including an eligible Agency trial) or valid beta access granted by the team, as well as your desktop-approved permissions. The free desktop trial or Standard license alone does not unlock MCP automation. Never paste a license key into your AI chat; activate it in VideoBatcher.

Getting help

Update to VideoBatcher 3.10.0 first. If tools do not appear, follow the connection checks above. If something still fails, contact us with your app version, operating system, AI app and the exact error. Never send your license key, private connection link or account credentials.