save-to-spotify vs DJ Claude
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-community). DJ Claude is an MCP server published by p-poss. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-20. 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
| Marketplace |  save-to-spotify |  DJ Claude |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.1.1 Forks (GitHub): 27 Stars (GitHub): 405 Not marked · First seen |
Listed Version: 0.1.18 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 0.1.6 Downloads/month (npm): 267 Downloads/week (npm): 57 Forks (GitHub): 2 Stars (GitHub): 36 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 | save-to-spotify | DJ Claude |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 405 (better) | 36 (worse) |
| Forks (GitHub) (differs) | 27 (better) | 2 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (dj-claude) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | Not published | 2 |
| Parts of the bundle (differs) | Not published | 23 |
| Licence (differs) | Apache-2.0 | AGPL-3.0-or-later |
| Repository (differs) | github.com/spotify/save-to-spotify | github.com/p-poss/dj-claude |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-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
Save spoken audio to Spotify and listen from any device. Using Claude Code, you can create and manage your own audio episode, create shows, track episode readiness, and build rich in-player timelines with chapters, companion images, deep links, and Spotify entity cards. Includes a guided production pipeline that orchestrates end-to-end episode creation: from scripting and editorial structure through to upload and timeline assembly. Powered by a local CLI that handles OAuth, file upload, and the Save to Spotify API.
DJ Claude
Agents can now live code music for you, themselves, and each other while they work.
How to run each
save-to-spotify As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install save-to-spotify@claude-communityDJ Claude As a local MCP server: npm package
claude mcp add --transport stdio dj-claude -- npx -y dj-claudeCommands 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: DJ Claude · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.