YouTube Data vs YouTube transcripts, comments & videos
YouTube Data is an MCP server published by kirbah. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). YouTube transcripts, comments & videos is an MCP server published by wulfcare. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. 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 |  YouTube Data |  YouTube transcripts, comments & videos |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.16 Downloads/month (npm): 5 163 Downloads/week (npm): 1 818 Forks (GitHub): 17 Stars (GitHub): 34 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 1.1.16 Downloads/month (npm): 5 163 Downloads/week (npm): 1 818 Forks (GitHub): 17 Stars (GitHub): 34 Not marked · First seen |
Not listed |
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 | YouTube Data | YouTube transcripts, comments & videos |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 34 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 17 (better) | 0 (worse) |
| Last release (differs) | 2026-11-01 | Not published |
| Where it runs (differs) | Remote server or your machine | Remote server (mcp.apify.com) |
| Transport (differs) | stdio, Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 2 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/kirbah/mcp-youtube | github.com/wulfcare/scrapers |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-10 |
| Endpoint at the last check (differs) | Answered with HTTP 404 (8 h ago) | Responded 8 h ago, requires authentication |
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 Data
YouTube MCP server for token-optimized, structured data using the YouTube Data API v3.
YouTube transcripts, comments & videos
YouTube transcripts/subtitles, comments + replies, Shorts and video/channel data.
How to run each
YouTube Data As a local MCP server: npm package
claude mcp add --env "MDB_MCP_CONNECTION_STRING=<YOUR_MDB_MCP_CONNECTION_STRING>" --env "YOUTUBE_API_KEY=<YOUR_YOUTUBE_API_KEY>" --transport stdio mcp-youtube -- npx -y @kirbah/mcp-youtubeRequires: MDB_MCP_CONNECTION_STRING (secret), YOUTUBE_API_KEY (secret)
YouTube transcripts, comments & videos
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of YouTube transcripts, comments & videos responded at the last daily 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 transcripts, comments & videos publish no settings it asks for, so we do not compare settings.
What it can do: YouTube Data · What it can do: YouTube transcripts, comments & videos · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.