video-transcoder vs CueFrame
video-transcoder is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
video-transcoder is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. CueFrame is an MCP server published by cueframe.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 |  CueFrame | |
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.2.0 Forks (GitHub): 0 Stars (GitHub): 2 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 | video-transcoderno longer listed · | CueFrame |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | 2 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | Remote server (api.cueframe.ai/v1/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) | 2 | Not a bundle |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | github.com/cueframe-ai/cueframe-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-22 |
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 video-transcoder
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
qencode com.qencode/qencode
Video pipeline for AI agents: analyze with AI, transcode to MP4/HLS/DASH, edit, protect and deliver.
-
Transcode, host and caption video from a prompt. Fifteen tools, nine read-only, nothing deletes.
-
web-video
Encode a video for the web with a bundled ffmpeg script — AV1, HEVC, and H.264 MP4s plus a poster, or VP9 WebM and HEVC with alpha for transparent video — and embed it with the…
-
FFmpeg as a service for AI agents: typed video editing tools, async jobs, downloadable outputs.
-
ffmpeg
Use this skill for local FFmpeg/FFprobe media inspection, remuxing, transcoding, filtering, evidence-bounded video review, transcript-assisted editorial plans, edit decision…
-
Local video editing for AI agents: cut, caption, analyse, reuse viral formats. FFmpeg, no cloud.
What each says it does
video-transcoder
Generate video transcoding pipeline configs
CueFrame
Turn footage into finished video: reframing, captions behind the subject, motion graphics, renders.
How to run each
video-transcoder
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
CueFrame As a remote MCP server
claude mcp add --transport http cueframe https://api.cueframe.ai/v1/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only CueFrame 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: video-transcoder · What it can do: CueFrame · 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.