Ext Ops Panel
Open dashboard
Comparison

save-to-spotify vs FFmpeg

save-to-spotify is a plugin bundle for AI coding tools published by spotify. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-official). FFmpeg is an MCP server published by pollinations. 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
Marketplacesave-to-spotifyFFmpeg
Claude Code: claude-plugins-official Listed
Version: 0.2.0
Forks (GitHub): 25
Stars (GitHub): 401
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 1 192
Stars (GitHub): 5 209
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

save-to-spotify vs FFmpeg
Factsave-to-spotifyFFmpeg
Marketplaces that list it11
Stars (GitHub) (differs)401 (worse)5 209 (better)
Forks (GitHub) (differs)25 (worse)1 192 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (gen.pollinations.ai/mcp/ffmpeg)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/spotify/save-to-spotifygithub.com/pollinations/pollinations
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

save-to-spotify

In its own words, on Claude Code: claude-plugins-official:

Create polished audio episodes with TTS narration, rich timelines, cover images, and save them to Spotify via the save-to-spotify CLI.

FFmpeg

In its own words, on Official MCP Registry:

Trim, convert, resize, compress, and remix audio and video.

How to run each

save-to-spotify As a Claude Code plugin

Claude Code
/plugin install save-to-spotify@claude-plugins-official

FFmpeg

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

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

Neither one's marketplaces publish the settings it asks for.

What it can do: save-to-spotify · What it can do: FFmpeg · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-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