Ext Ops Panel
Open dashboard
Comparison

youtube-kit vs YouTube Data

youtube-kit is an MCP server published by eukosh. Marketplaces we read that list it: 1 (Official MCP Registry). YouTube Data is an MCP server published by kirbah. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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-kitYouTube Data
Official MCP Registry Listed
Version: 0.7.1
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Listed
Version: 1.1.15
Downloads/month (npm): 2 872
Downloads/week (npm): 1 076
Forks (GitHub): 16
Stars (GitHub): 32
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-kit vs YouTube Data
Factyoutube-kitYouTube Data
Marketplaces that list it11
Stars (GitHub) (differs)3 (worse)32 (better)
Forks (GitHub) (differs)0 (worse)16 (better)
Last release (differs)2026-10-21Not published
Where it runs (differs)On your machine (youtube-kit)Remote server or your machine
Transport (differs)stdiostdio, Streamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 12, secrets among them: 2
LicenceNot statedNot stated
Repository (differs)github.com/eukosh/youtube-kitgithub.com/kirbah/mcp-youtube
Changes in the last 7 days (differs)50
First seen (differs)2026-10-182026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (5 days ago)

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-kit

In its own words, on Official MCP Registry:

YouTube CLI and MCP server: search and read public YouTube, and manage your own channels.

YouTube Data

In its own words, on Official MCP Registry:

YouTube MCP server for token-optimized, structured data using the YouTube Data API v3.

How to run each

youtube-kit As a local MCP server: PyPI package

Claude Code
claude mcp add --env "YOUTUBE_API_KEY=<YOUR_YOUTUBE_API_KEY>" --transport stdio youtube-kit -- uvx youtube-kit mcp

Requires: YOUTUBE_API_KEY (secret)

YouTube Data As a local MCP server: npm package

Claude Code
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-youtube

Requires: MDB_MCP_CONNECTION_STRING (secret), YOUTUBE_API_KEY (secret)

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

Only YouTube Data 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

Only youtube-kit asks for

  • YOUTUBE_CHANNEL

Only YouTube Data asks for

  • MDB_MCP_CONNECTION_STRING (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: youtube-kit · What it can do: YouTube Data · 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