Ext Ops Panel
Open dashboard
Comparison

YouTube Transcript & Search MCP Server vs io.github.fetchworks-dev/youtube-transcripts

YouTube Transcript & Search MCP Server is an MCP server published by transcriptout.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.fetchworks-dev/youtube-transcripts is an MCP server published by fetchworks-dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
MarketplaceYouTube Transcript & Search MCP Serverio.github.fetchworks-dev/youtube-transcripts
Official MCP Registry Listed
Version: 1.0.1
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.1.1
Downloads/month (npm): 87
Downloads/week (npm): 10
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

YouTube Transcript & Search MCP Server vs io.github.fetchworks-dev/youtube-transcripts
FactYouTube Transcript & Search MCP Serverio.github.fetchworks-dev/youtube-transcripts
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.transcriptout.com/mcp)On your machine (fetchworks-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/artemchuikin/youtube-mcpgithub.com/fetchworks/fetchworks-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 5 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

YouTube Transcript & Search MCP Server

In its own words, on Official MCP Registry:

YouTube transcripts, search, channels, playlists and bulk transcript jobs for AI agents. 14 tools.

io.github.fetchworks-dev/youtube-transcripts

In its own words, on Official MCP Registry:

YouTube transcripts for AI agents: videos, channels, playlists, search. Timestamps, SRT, VTT.

How to run each

YouTube Transcript & Search MCP Server As a remote MCP server

Claude Code
claude mcp add --transport http youtube-transcript-and-youtube-search https://api.transcriptout.com/mcp

io.github.fetchworks-dev/youtube-transcripts As a local MCP server: npm package

Claude Code
claude mcp add --env "APIFY_TOKEN=<YOUR_APIFY_TOKEN>" --transport stdio youtube-transcripts -- npx -y fetchworks-mcp

Requires: APIFY_TOKEN (secret)

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

Only YouTube Transcript & Search MCP Server has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of YouTube Transcript & Search MCP Server publish no settings it asks for, so we do not compare settings.

What it can do: YouTube Transcript & Search MCP Server · What it can do: io.github.fetchworks-dev/youtube-transcripts · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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