com.jojapi/spotify vs Spotify
com.jojapi/spotify is an MCP server published by jojapi.com. Marketplaces we read that list it: 1 (Official MCP Registry). Spotify is an MCP server published by jamiew. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  com.jojapi/spotify |  Spotify |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.7.0 Downloads/month (PyPI): 836 Downloads/week (PyPI): 101 Forks (GitHub): 3 Stars (GitHub): 11 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 | com.jojapi/spotify | Spotify |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 11 |
| Forks (GitHub) (differs) | No figure on GitHub | 3 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.jojapi.com/spotify) | On your machine (spotify-mcp-jamiew) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 2 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/jamiew/spotify-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days ago | no remote endpoint we check |
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
com.jojapi/spotify
Spotify: Spotify Data API for Millions of songs & podcasts, artists, albums, playlists and more.
Spotify
MCP server connecting LLMs to Spotify, with smart-batching and large-playlist tools
How to run each
com.jojapi/spotify As a remote MCP server
claude mcp add --transport http spotify https://mcp.jojapi.com/spotifySpotify As a local MCP server: PyPI package
claude mcp add --env "SPOTIFY_CLIENT_ID=<YOUR_SPOTIFY_CLIENT_ID>" --env "SPOTIFY_CLIENT_SECRET=<YOUR_SPOTIFY_CLIENT_SECRET>" --env "SPOTIFY_REDIRECT_URI=<YOUR_SPOTIFY_REDIRECT_URI>" --transport stdio spotify-mcp -- uvx spotify-mcp-jamiewRequires: SPOTIFY_CLIENT_ID (secret), SPOTIFY_CLIENT_SECRET (secret), SPOTIFY_REDIRECT_URI
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.jojapi/spotify 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
The marketplaces of com.jojapi/spotify publish no settings it asks for, so we do not compare settings.
What it can do: com.jojapi/spotify · What it can do: Spotify · Compare two other plugins
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.