Ext Ops Panel
Open dashboard
Comparison

code-music vs io.github.markswendsen-code/spotify

code-music is a plugin bundle for AI coding tools published by kennethleungty. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.markswendsen-code/spotify is an MCP server published by markswendsen-code. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
Marketplacecode-musicio.github.markswendsen-code/spotify
Claude Code: claude-plugins-community Listed
Version: 1.0.3
Forks (GitHub): 0
Stars (GitHub): 25
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Downloads/month (npm): 156
Downloads/week (npm): 37
Forks (GitHub): 1
Stars (GitHub): 0
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

code-music vs io.github.markswendsen-code/spotify
Factcode-musicio.github.markswendsen-code/spotify
Marketplaces that list it11
Stars (GitHub) (differs)25 (better)0 (worse)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@striderlabs/mcp-spotify)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)3Not published
Parts of the bundle (differs)26Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/kennethleungty/code-musicgithub.com/markswendsen-code/mcp-spotify
Changes in the last 7 days00
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

code-music

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

Enjoy background music while your AI coding agents do the heavy lifting. Stream lo-fi, jazz, classical, ambient, electronic, synthwave, and more—live from the internet, right in your terminal. No setup, no accounts, no ads. Features include an AI DJ that reads your session context and automatically picks the perfect genre, a built-in Pomodoro timer, and 30+ curated stations from the internet. Works on macOS, Linux, WSL2, and Windows.

io.github.markswendsen-code/spotify

In its own words, on Official MCP Registry:

MCP server for Spotify - let AI agents control playback, search music, and manage playlists

How to run each

code-music As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install code-music@claude-community

io.github.markswendsen-code/spotify As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio spotify -- npx -y @striderlabs/mcp-spotify

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: code-music · What it can do: io.github.markswendsen-code/spotify · 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. 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