Ext Ops Panel
Open dashboard
Comparison

YouTube transcripts, comments & videos vs AutoClip

YouTube transcripts, comments & videos is an MCP server published by wulfcare. Marketplaces we read that list it: 1 (Official MCP Registry). AutoClip is an MCP server published by zhouxiaoka. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). 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

Where each is published
MarketplaceYouTube transcripts, comments & videosAutoClip
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.5.7.post1
Downloads/month (PyPI): 0
Downloads/week (PyPI): 122
Forks (GitHub): 1 833
Stars (GitHub): 10 396
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 1.5.7.post1
Downloads/month (PyPI): 0
Downloads/week (PyPI): 122
Forks (GitHub): 1 833
Stars (GitHub): 10 396
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 transcripts, comments & videos vs AutoClip
FactYouTube transcripts, comments & videosAutoClip
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)10 396 (better)
Forks (GitHub) (differs)0 (worse)1 833 (better)
Last release (differs)Not published2026-10-28
Where it runs (differs)Remote server (mcp.apify.com)On your machine (autoclip-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)github.com/wulfcare/scrapersgithub.com/zhouxiaoka/autoclip
Changes in the last 7 days (differs)20
First seen (differs)2026-11-102026-10-12
Endpoint at the last check (differs)Responded 9 h ago, requires authenticationno 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 transcripts, comments & videos

In its own words, on Official MCP Registry:

YouTube transcripts/subtitles, comments + replies, Shorts and video/channel data.

AutoClip

In its own words, on Official MCP Registry:

Clip long videos into short clips with covers and captions. Local CLI and MCP.

How to run each

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

AutoClip As a local MCP server: PyPI package

Claude Code
claude mcp add --env "AUTOCLIP_API_KEY=<YOUR_AUTOCLIP_API_KEY>" --transport stdio autoclip-mcp -- uvx autoclip-mcp

Requires: AUTOCLIP_API_KEY (secret)

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

Only YouTube transcripts, comments & videos 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 transcripts, comments & videos publish no settings it asks for, so we do not compare settings.

What it can do: YouTube transcripts, comments & videos · What it can do: AutoClip · Compare two other plugins

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