Ext Ops Panel
Open dashboard
Comparison

CaptionPipe vs io.github.jkawamoto/mcp-youtube-transcript

CaptionPipe is an MCP server published by captionpipe.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.jkawamoto/mcp-youtube-transcript is an MCP server published by jkawamoto. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-19. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceCaptionPipeio.github.jkawamoto/mcp-youtube-transcript
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.8.0
Forks (GitHub): 76
Stars (GitHub): 490
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:90eefb484754
Forks (GitHub): 76
Pulls (Docker Hub): 302 396
Stars (Docker Hub): 19
Stars (GitHub): 490
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

CaptionPipe vs io.github.jkawamoto/mcp-youtube-transcript
FactCaptionPipeio.github.jkawamoto/mcp-youtube-transcript
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub490
Pulls (Docker Hub) (differs)No figure on Docker Hub302 396
Forks (GitHub) (differs)No figure on GitHub76
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.captionpipe.com/mcp)On your machine (https://github.com/jkawamoto/mcp-youtube-transcript/releases/download/v0.8.0/mcp-youtube-transcript.mcpb)
Transport (differs)Streamable HTTPstdio
Tools it declares (differs)Not published4
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/jkawamoto/mcp-youtube-transcript
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 2 days agono remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

CaptionPipe

In its own words, on Official MCP Registry:

One call burns captions into your video. Hosted, prepaid, no subscription. MP4 plus SRT and VTT.

io.github.jkawamoto/mcp-youtube-transcript

In its own words, on Official MCP Registry:

An MCP server retrieving transcripts of YouTube videos

How to run each

CaptionPipe As a remote MCP server

Claude Code
claude mcp add --transport http captionpipe https://api.captionpipe.com/mcp

io.github.jkawamoto/mcp-youtube-transcript As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio youtube-transcript -- docker run -i --rm mcp/youtube-transcript

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only CaptionPipe has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of CaptionPipe publish no list of tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: CaptionPipe · What it can do: io.github.jkawamoto/mcp-youtube-transcript · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built