Ext Ops Panel
Open dashboard
Comparison

save-to-spotify vs PodLearn

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). PodLearn is an MCP server published by blutrich. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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-spotifyPodLearn
Claude Code: claude-plugins-community Listed
Version: 0.1.1
Forks (GitHub): 27
Stars (GitHub): 403
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.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

save-to-spotify vs PodLearn
Factsave-to-spotifyPodLearn
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)403 (better)2 (worse)
Forks (GitHub) (differs)27 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (httiyebjgxxwtgggkpgw.supabase.co/functions/v1/mcp-server-streamable)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not published2
Licence (differs)Apache-2.0AGPL-3.0
Repository (differs)github.com/spotify/save-to-spotifygithub.com/blutrich/podlearn-plugin
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 33 h ago, requires a key

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-community:

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.

PodLearn

In its own words, on Official MCP Registry:

Search 4M+ podcasts & YouTube, transcribe any episode, search transcripts, generate AI lessons.

How to run each

save-to-spotify As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install save-to-spotify@claude-community

PodLearn As a remote MCP server

Claude Code
claude mcp add --transport http podlearn https://httiyebjgxxwtgggkpgw.supabase.co/functions/v1/mcp-server-streamable --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only PodLearn 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: save-to-spotify · What it can do: PodLearn · 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.

Where the data comes from: how the catalog is built