io.github.fetchworks-dev/youtube-transcripts vs TranscriptAPI — YouTube transcripts (transcriptapi.io)
io.github.fetchworks-dev/youtube-transcripts is an MCP server published by fetchworks-dev. Marketplaces we read that list it: 1 (Official MCP Registry). TranscriptAPI — YouTube transcripts (transcriptapi.io) is an MCP server published by transcriptapi.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
| Marketplace |  io.github.fetchworks-dev/youtube-transcripts | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 Downloads/month (npm): 87 Downloads/week (npm): 10 Not marked · First seen |
Listed Version: 0.1.1 No figure published 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
| Fact | io.github.fetchworks-dev/youtube-transcripts | TranscriptAPI — YouTube transcripts (transcriptapi.io) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (fetchworks-mcp) | Remote server (api.transcriptapi.io/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/fetchworks/fetchworks-mcp | Not stated |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-17 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
io.github.fetchworks-dev/youtube-transcripts
YouTube transcripts for AI agents: videos, channels, playlists, search. Timestamps, SRT, VTT.
TranscriptAPI — YouTube transcripts (transcriptapi.io)
YouTube transcripts, search, channels and playlists for AI agents, by transcriptapi.io.
How to run each
io.github.fetchworks-dev/youtube-transcripts As a local MCP server: npm package
claude mcp add --env "APIFY_TOKEN=<YOUR_APIFY_TOKEN>" --transport stdio youtube-transcripts -- npx -y fetchworks-mcpRequires: APIFY_TOKEN (secret)
TranscriptAPI — YouTube transcripts (transcriptapi.io) As a remote MCP server
claude mcp add --transport http youtube-transcript https://api.transcriptapi.io/mcp --header "Authorization: Bearer <YOUR_API_KEY>"Requires: TRANSCRIPTAPI_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only io.github.fetchworks-dev/youtube-transcripts asks for
APIFY_TOKEN (secret)
Only TranscriptAPI — YouTube transcripts (transcriptapi.io) asks for
TRANSCRIPTAPI_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.fetchworks-dev/youtube-transcripts · What it can do: TranscriptAPI — YouTube transcripts (transcriptapi.io) · 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.