yt-mem-ai vs BibiGPT
yt-mem-ai is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑22.
yt-mem-ai is a plugin bundle for AI coding tools published by dasein. No marketplace we read lists it any more. BibiGPT is an MCP server published by JimmyLv. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-25. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |   BibiGPT | |
|---|---|---|
| Community marketplace dasein108/yt-mem-ai | Removed on 2026-10-22 Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 9 Stars (GitHub): 131 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
| Fact | yt-mem-aino longer listed · | BibiGPT |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 7 | 131 |
| Forks (GitHub) (differs) | 0 | 9 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (bibigpt.co/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 9 | 5 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/dasein108/yt-mem-ai | github.com/jimmylv/bibigpt-skill |
| Changes in the last 7 days | 2 | 2 |
| First seen | 2026-10-13 | 2026-10-13 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-25 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of yt-mem-ai
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Local YouTube memory: transcribe, embed and search videos, with summaries and highlights.
-
Transcribe YouTube via Whisper. Summaries, chapters, semantic-search across your corpus.
-
recapfy io.github.pedrot95dev/recapfy
Ask about a YouTube video or fetch its transcript. Paid per call in USDC on Solana via x402.
-
Turn a YouTube video into a faithful-capture literature note in an Obsidian vault (transcript + canonical visual scenes + structured extraction)
-
Convert YouTube videos into structured docs, summaries, audio, and visual assets for easier discovery.
-
Extract subtitles/transcripts from YouTube videos via CLI or browser automation
What each says it does
yt-mem-ai
A local YouTube memory: fetches transcripts (captions, Whisper fallback), keeps them searchable on your machine, and writes summaries, timestamped highlights, Q&A, decks and daily digests. Ships the yt + yt-agent skills and /yt-* commands; no API key.
BibiGPT
Summarize, transcribe and search YouTube, Bilibili, TikTok, podcasts and other videos with AI.
How to run each
yt-mem-ai
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
BibiGPT As a remote MCP server
claude mcp add --transport http bibigpt https://bibigpt.co/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only BibiGPT 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
Neither one's marketplaces publish the settings it asks for.
What it can do: yt-mem-ai · What it can do: BibiGPT · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.