AWS Bedrock Data Automation vs music-metadata-mcp
AWS Bedrock Data Automation is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). music-metadata-mcp is an MCP server published by stevebirring-star. Marketplaces we read that list it: 1 (npm registry (MCP servers)). As of our marketplace pass on 2026-11-11. 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 |  AWS Bedrock Data Automation |  music-metadata-mcp |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ca5c8e3d1bf0 Forks (GitHub): 1 867 Pulls (Docker Hub): 15 256 Stars (Docker Hub): 0 Stars (GitHub): 9 899 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Not listed | Listed Version: 2.20.2 Downloads/month (npm): 1 517 Downloads/week (npm): 344 Forks (GitHub): 0 Stars (GitHub): 3 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 | AWS Bedrock Data Automation | music-metadata-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 899 (better) | 3 (worse) |
| Pulls (Docker Hub) (differs) | 15 256 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 867 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-11-09 |
| Where it runs (differs) | On your machine (mcp/aws-bedrock-data-automation-mcp-server) | On your machine (music-metadata-mcp) |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | Not published |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/awslabs/mcp | github.com/stevebirring-star/music-metadata-mcp |
| Changes in the last 7 days (differs) | 0 | 5 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
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
Analyze documents, images, videos, and audio.
music-metadata-mcp
MCP server for the FreqBlog Music API — 25 tools covering audio features, plain-language search by description, seedless discovery by tempo/key/genre/year, similar-sounding tracks from several seeds, honestly-labelled tags, recommendations (Spotify /recom
How to run each
AWS Bedrock Data Automation As a local MCP server: Docker image
claude mcp add --transport stdio aws-bedrock-data-automation -- docker run -i --rm mcp/aws-bedrock-data-automation-mcp-servermusic-metadata-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of music-metadata-mcp publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of music-metadata-mcp publish no settings it asks for, so we do not compare settings.
What it can do: AWS Bedrock Data Automation · What it can do: music-metadata-mcp · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.