pickfit

BrowseMCP servers

YouTube Transcript MCP Server

An MCP server that fetches transcripts and metadata of YouTube videos for LLM clients, with pagination and proxy support.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: uv
  • Needs the network
  1. uv tool install git+https://github.com/jkawamoto/mcp-youtube-transcript

    uv tool install git+https://github.com/jkawamoto/mcp-youtube-transcript

Check that it works

mcp-youtube-transcript --help

The output should contain “YouTube Transcript MCP server.”.

Add it to your agent

claude mcp add mcp-youtube-transcript -- mcp-youtube-transcript
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "mcp-youtube-transcript": {
      "command": "mcp-youtube-transcript",
      "args": []
    }
  }
}

Add the server to your MCP client's configuration so it runs mcp-youtube-transcript; the client then lists the get_transcript, get_timed_transcript, get_video_info and get_available_languages tools.

What it does

  • Get transcripts, timestamps and video details
    Not tested
  • Read long transcripts in pages
    Not tested
  • Send requests through residential or HTTP proxies
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 0 of 3 features work
  4. Works offline

Good for

  • get the plain-text transcript of a YouTube video
  • list available transcript languages for a video
  • fetch video title and channel metadata

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

An MCP client connects and lists its tools

  • Replayed from scratch
  • Works offline
  • Checked on 15 Nov 2026
  • Version 0.8.4

An MCP client handshake over stdio listed 4 tools.

Differences the test machine hit

  • README: Launch with uvx --from git+https://github.com/jkawamoto/mcp-youtube-transcript mcp-youtube-transcript
    In the test: uv tool install git+https://github.com/jkawamoto/mcp-youtube-transcript puts mcp-youtube-transcript on PATH, so it starts without fetching anything at launch

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.