Ext Ops Panel
Open dashboard
Comparison

microsoft-events vs io.github.fetchworks-dev/youtube-transcripts

microsoft-events is a plugin bundle for AI coding tools published by microsoft. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). io.github.fetchworks-dev/youtube-transcripts is an MCP server published by fetchworks-dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
Marketplacemicrosoft-eventsio.github.fetchworks-dev/youtube-transcripts
Copilot CLI: github/awesome-copilot Listed
Version: 1.0.6
Forks (GitHub): 85
Stars (GitHub): 295
Not marked · First seen
Not listed
Official MCP Registry Not listed 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

microsoft-events vs io.github.fetchworks-dev/youtube-transcripts
Factmicrosoft-eventsio.github.fetchworks-dev/youtube-transcripts
Marketplaces that list it11
Stars (GitHub) (differs)295No figure on GitHub
Forks (GitHub) (differs)85No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (learn.microsoft.com/api/mcp)On your machine (fetchworks-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)2Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/microsoft/build-cligithub.com/fetchworks/fetchworks-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno 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

microsoft-events

In its own words, on Copilot CLI: github/awesome-copilot:

Connect your project to Microsoft Build and Ignite sessions — discover relevant talks, explore what's new for your stack, and plan next steps from your development environment.

io.github.fetchworks-dev/youtube-transcripts

In its own words, on Official MCP Registry:

YouTube transcripts for AI agents: videos, channels, playlists, search. Timestamps, SRT, VTT.

How to run each

microsoft-events

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.fetchworks-dev/youtube-transcripts As a local MCP server: npm package

Claude Code
claude mcp add --env "APIFY_TOKEN=<YOUR_APIFY_TOKEN>" --transport stdio youtube-transcripts -- npx -y fetchworks-mcp

Requires: APIFY_TOKEN (secret)

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

The marketplaces of microsoft-events publish no settings it asks for, so we do not compare settings.

What it can do: microsoft-events · What it can do: io.github.fetchworks-dev/youtube-transcripts · Compare two other plugins

Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. 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