spotify-ads-api vs Spytrend MCP Skills
spotify-ads-api is a plugin bundle for AI coding tools published by spotify. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community, Community GitHub marketplaces). Spytrend MCP Skills is a plugin bundle for AI coding tools published by Spytrend. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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
| Marketplace | ||
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 1.9.0 Forks (GitHub): 19 Stars (GitHub): 19 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Listed Version: 1.7.0 Forks (GitHub): 19 Stars (GitHub): 19 Not marked · First seen |
Not listed |
| Community marketplace spytrend/spytrend-mcp | Not listed | Listed Version: 1.0.3 No figure published 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 | spotify-ads-api | Spytrend MCP Skills |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 19 | No figure on GitHub |
| Forks (GitHub) (differs) | 19 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.spytrend.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 22 | 7 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/spotify/ads-claude-plugin | github.com/spytrend/spytrend-mcp |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-14 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 41 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
spotify-ads-api
Manage Spotify ad campaigns with natural language. Create campaigns, ad sets, ads, pull reports, and handle OAuth — all through conversation.
Spytrend MCP Skills
Six Spytrend workflows for advertising intelligence, advertiser research, webmaster analysis, website review, keyword search, and shop discovery.
How to run each
spotify-ads-api As a Claude Code plugin
/plugin install spotify-ads-api@claude-plugins-official
Spytrend MCP Skills As a Claude Code plugin
/plugin marketplace add spytrend/spytrend-mcp
/plugin install spytrend-mcp-skills@spytrend-mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Spytrend MCP Skills 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: spotify-ads-api · What it can do: Spytrend MCP Skills · 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 the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.