Ext Ops Panel
Open dashboard
Comparison

AWS Bedrock Data Automation vs spotify-ads-api

AWS Bedrock Data Automation is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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). 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
MarketplaceAWS Bedrock Data Automationspotify-ads-api
Docker MCP Catalog Listed
Version: sha256:ca5c8e3d1bf0
Forks (GitHub): 1 808
Pulls (Docker Hub): 14 351
Stars (Docker Hub): 0
Stars (GitHub): 9 782
Not marked · First seen
Not listed
Claude Code: claude-plugins-official Not listed Listed
Version: 1.9.0
Forks (GitHub): 19
Stars (GitHub): 19
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.7.0
Forks (GitHub): 19
Stars (GitHub): 19
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

AWS Bedrock Data Automation vs spotify-ads-api
FactAWS Bedrock Data Automationspotify-ads-api
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)9 782 (better)19 (worse)
Pulls (Docker Hub) (differs)14 351No figure on Docker Hub
Forks (GitHub) (differs)1 808 (better)19 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/aws-bedrock-data-automation-mcp-server)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)3Not published
Environment variables it asks for (differs)3, secrets among them: 0Not published
Hooks it runs (differs)Not published1
Parts of the bundle (differs)Not a bundle22
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/awslabs/mcpgithub.com/spotify/ads-claude-plugin
Changes in the last 7 days (differs)02
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

AWS Bedrock Data Automation

In its own words, on Docker MCP Catalog:

Analyze documents, images, videos, and audio.

spotify-ads-api

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

Manage Spotify ad campaigns with natural language. Create campaigns, ad sets, ads, pull reports, and handle OAuth — all through conversation.

How to run each

AWS Bedrock Data Automation As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio aws-bedrock-data-automation -- docker run -i --rm mcp/aws-bedrock-data-automation-mcp-server

spotify-ads-api As a Claude Code plugin

Claude Code
/plugin install spotify-ads-api@claude-plugins-official

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

Tools each declares

The marketplaces of spotify-ads-api publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of spotify-ads-api publish no settings it asks for, so we do not compare settings.

What it can do: AWS Bedrock Data Automation · What it can do: spotify-ads-api · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.

Where the data comes from: how the catalog is built