Ext Ops Panel
Open dashboard
Comparison

save-to-spotify vs io.github.JuzzyDee/audio-analyzer

save-to-spotify is a plugin bundle for AI coding tools published by spotify. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Community GitHub marketplaces). io.github.JuzzyDee/audio-analyzer is an MCP server published by JuzzyDee. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-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
Marketplacesave-to-spotifyio.github.JuzzyDee/audio-analyzer
Claude Code: claude-plugins-official Listed
Version: 0.2.0
Forks (GitHub): 26
Stars (GitHub): 403
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 12
Stars (GitHub): 66
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 io.github.JuzzyDee/audio-analyzer
Factsave-to-spotifyio.github.JuzzyDee/audio-analyzer
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)403 (better)66 (worse)
Forks (GitHub) (differs)26 (better)12 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (https://github.com/JuzzyDee/audio-analyzer-rs/releases/download/v1.0.0/audio-analyzer-darwin-arm64.mcpb)
Transport (differs)Not statedstdio
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/juzzydee/audio-analyzer-rs
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11

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.

io.github.JuzzyDee/audio-analyzer

In its own words, on Official MCP Registry:

Gives LLMs ears. Spectral, harmonic, rhythm, stereo, and structural audio analysis.

How to run each

save-to-spotify As a Claude Code plugin

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

io.github.JuzzyDee/audio-analyzer

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: io.github.JuzzyDee/audio-analyzer · 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 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.

Where the data comes from: how the catalog is built