MCP

AI-agent format

Ship captions and subtitles without the grind

Pull SRT/VTT files and clean transcripts in one step — accessibility and search indexing in the same pass.

ProducerContent Strategy & Creatorsrun_youtube_toollibrary_import_youtube_videoget_youtube_transcript
The use case

The problem

Captions are the deliverable everyone agrees matters and nobody budgets for. They serve deaf and hard-of-hearing viewers, the majority who watch muted, the translators who need source files, and the search engines that index text — four audiences from one artifact. Yet in most production pipelines, captioning is the step that slips: auto-captions stay unedited (and their errors become your brand's typos), SRT files get made once for the big launch video and never again.

The grind is the reason — per-video, per-format file wrangling across a back catalog of dozens or hundreds of uploads. It's exactly the kind of mechanical volume work that shouldn't touch a human's week.

The mechanics

How veridive MCP helps

run_youtube_tool's srt-vtt-downloader produces the caption files — standard SRT/VTT from any public video's URL, ready for your player, your translators, or your re-upload pipeline. Batch it across the catalog and the captioning backlog becomes an afternoon.

library_import_youtube_video plus get_youtube_transcript supply the companion artifact: the clean, timestamped transcript — the master text your captions, blog embeds, and site search all derive from (pulls are free once imported). And for spoken-word content that needs a fresh transcription pass, stt-transcription runs speech-to-text through the same entry point. One workflow, every text artifact a video owes the world.

Step by step

How to run it

  1. 1
    Connect veridive MCP

    One-time setup: add the veridive MCP server to Claude, ChatGPT, Cursor or any MCP client and generate your API key. Takes about two minutes.

  2. 2
    Pull the caption files

    SRT/VTT per video, straight from URLs — batchable across the whole catalog.

    Get the SRT and VTT caption files for these videos: <video URLs> — use veridive's run_youtube_tool.
  3. 3
    Build the master transcripts

    Import the catalog and pull clean timestamped transcripts — the source text for pages, embeds and search.

    Import these videos into my library and pull each one's full transcript with timestamps: <video URLs>
  4. 4
    Feed the downstream uses

    Translators get the SRTs, the site gets transcript pages, and accessibility review gets a readable text pass.

    From these transcripts, flag anything a caption editor should review — unclear passages, likely mis-transcriptions, speaker changes.
Before vs after

Problems it solves

  • Captioning slips in every pipeline because it's per-video file grind nobody budgets.
  • Unedited auto-captions publish their errors under your brand's name.
  • Translators wait on source SRT files that take a week to materialize.
  • The back catalog — often hundreds of videos — never gets captioned at all.
The payoff

Why it's valuable

  • Four audiences (accessibility, muted viewers, translators, search) served by one batched pass.
  • The back-catalog backlog collapses from a quarter's grind to an afternoon.
  • Master transcripts unlock the SEO layer: transcript pages that make video content indexable.
  • The review step focuses human time where it matters — corrections, not transcription.
Copy & paste

Example prompts

SRT + VTT files for these videos: <URLs> — use veridive's run_youtube_tool.
Import these and pull full timestamped transcripts: <URLs>
Flag passages a caption editor should review in these transcripts.
Questions

FAQ

Which tools cover which artifact?

srt-vtt-downloader (via run_youtube_tool) produces the caption files from any URL; import + get_youtube_transcript produce the clean master transcript (free once imported); stt-transcription handles fresh speech-to-text passes when needed.

Are the caption files edit-ready?

They're standard SRT/VTT — load them into any caption editor for the human review pass. The workflow eliminates the extraction and formatting grind; editorial judgment on the text stays yours.

Does this help SEO beyond accessibility?

Substantially — transcript pages and caption files are how search engines (and AI assistants) read your video content. The same pass that serves accessibility makes your catalog indexable.

Keep going

Related use cases

Run this in your own assistant

Connect the veridive MCP server to Claude, ChatGPT or Cursor and paste the prompts above — setup takes about two minutes.