Ext Ops Panel
Open dashboard
Comparison

youtube vs VIDIA

youtube is a plugin bundle for AI coding tools published by JCodesMore. Marketplaces we read that list it: 1 (Community GitHub marketplaces). VIDIA is an MCP server published by vidia.kr. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-24. 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
MarketplaceyoutubeVIDIA
Community marketplace jcodesmore/jcodesmore-plugins Listed
Version: 0.2.0
Forks (GitHub): 17
Stars (GitHub): 58
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.0
Downloads/month (npm): 424
Downloads/week (npm): 207
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.1.1
Downloads/month (npm): 424
Downloads/week (npm): 207
Forks (GitHub): 0
Stars (GitHub): 0
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 vs VIDIA
FactyoutubeVIDIA
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)58 (better)0 (worse)
Forks (GitHub) (differs)17 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 01, secrets among them: 1
Hooks it runs (differs)1Not published
Parts of the bundle (differs)5Not a bundle
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/jcodesmore/youtube-for-ai-agentsgithub.com/lead788/vidia-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-232026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 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

In its own words, on Community GitHub marketplaces:

YouTube tools — search, transcripts, video info, channel browsing, playlists

VIDIA

In its own words, on Official MCP Registry:

VIDIA AI video production: get quotes, start videos, track progress and download results

How to run each

youtube As a Claude Code plugin

Claude Code
/plugin marketplace add jcodesmore/jcodesmore-plugins
/plugin install youtube@jcodesmore-plugins

VIDIA As a remote MCP server

Claude Code
claude mcp add --transport http vidia https://vidia.kr/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: VIDIA_API_KEY (secret), Authorization header

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

Only VIDIA 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 asks for

  • CLAUDE_PLUGIN_DATA

Only VIDIA asks for

  • VIDIA_API_KEY (secret)

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

What it can do: youtube · What it can do: VIDIA · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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.

Where the data comes from: how the catalog is built