I gave ChatGPT YouTube transcripts through MCP. Here is how it works

RapidShortsAI — Tue, 22 Sep 2026 17:00:38 +0000

Every few weeks I need to read a lot of YouTube. Not watch, read. A conference channel drops twenty talks, a framework maintainer explains a breaking change on a podcast, a competitor ships something and walks through it on camera. The information is in the audio, and the audio is slow.

For a long time my workaround was the "show transcript" panel on YouTube, copy, paste into ChatGPT, repeat. It works for one video. It falls apart at five. And the pasted text is full of timestamps and line breaks that eat context.

So I built the thing I wanted: an MCP server that hands an AI model clean transcripts, channel search, and playlist listings as tools. It's called BulkTranscripts and this post is how it works under the hood, plus how to wire it into whatever client you use.

What the model gets

The server exposes a small set of tools. The ones I use most:

get_transcript for one video, returned as plain text with no timestamps unless you ask for them
get_transcripts for a batch of video IDs in one call
search_channel to find videos on a channel by topic
get_latest_videos to see what a channel uploaded recently, always free
start_bulk_extract for a whole channel or playlist, up to a thousand videos, running server-side while the model polls get_bulk_status

That last one matters more than it sounds. A model that has to fetch 200 transcripts inline will time out or blow its context. A detached job that fills a library on the server, with the model paging through results afterwards, is the difference between a demo and something you can use on a real channel.

Wiring it up

If your client speaks OAuth (ChatGPT, Claude web and desktop, Claude Code, Cursor, VS Code), you add the endpoint and sign in with Google. No key to manage.

https://bulktranscripts.co/mcp

In Claude Code that's one line:

claude mcp add --transport http bulktranscripts https://bulktranscripts.co/mcp

In ChatGPT it lives under Apps, and the sign-in is a normal Google prompt. Thirty transcripts come free with the account, no card.

For clients without OAuth, or for scripts, you create an API key in the dashboard and send it as a bearer token:

{
  "mcpServers": {
    "bulktranscripts": {
      "url": "https://bulktranscripts.co/mcp",
      "headers": { "Authorization": "Bearer bt_ak_..." }
    }
  }
}

The setup page for each client is in the docs.

The credit rule, because it trips people up

A transcript costs one credit the first time it enters your library. After that, reading it again is free, forever, from any client. Live lookups like channel search cost one credit. get_latest_videos is free so you can poll it on a schedule and only fetch what's new.

Credits follow the account, not the connector. Buying a pack never touches your MCP config. If a batch runs past your balance, you get the transcripts that completed and a clear count of how many were stopped, so the model can tell you instead of silently truncating.

What I actually do with it

The workflow that made me build this: pick one channel, ask for the fifteen most relevant videos on a topic, pull all the transcripts, and have the model produce something structured from them. A changelog digest. A "what did they claim and where" table with video attribution. A playbook from a series of talks.

Here's the prompt shape, in ChatGPT with the connector on:

Look through @channel's recent videos about [topic]. Use the 15 most relevant. Pull the transcripts and build me a practical guide, citing which video each idea comes from.

The model makes a handful of tool calls, thinks for a couple of minutes, and the output is grounded in what was said rather than in what the titles suggest. That grounding is the whole point. Titles are marketing. Transcripts are the talk.

Things I'd warn you about

Transcripts are only as good as YouTube's captions. Auto-generated captions on a heavy accent or a noisy room come through rough. Uploader-provided captions are great. You can't tell which you got until you read it.

Also, don't let the model summarize. Ask it for claims, decisions, and quotes with attribution. Summaries flatten the interesting parts. Claims give you something to check or disagree with.