AWS Bedrock Data Automation vs media-pipeline
AWS Bedrock Data Automation is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). media-pipeline is a plugin bundle for AI coding tools published by Claude Image Gen. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-20. 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 | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ca5c8e3d1bf0 Forks (GitHub): 1 817 Pulls (Docker Hub): 14 432 Stars (Docker Hub): 0 Stars (GitHub): 9 798 Not marked · First seen |
Not listed |
| Community marketplace guinacio/claude-image-gen | Not listed | Listed Version: 1.2.3 Forks (GitHub): 9 Stars (GitHub): 77 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 | media-pipeline |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 798 (better) | 77 (worse) |
| Pulls (Docker Hub) (differs) | 14 432 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 817 (better) | 9 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-bedrock-data-automation-mcp-server) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | 6, secrets among them: 2 |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/awslabs/mcp | github.com/guinacio/claude-image-gen |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-20 |
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.
media-pipeline
Media asset processing plugin with skills for visual content creation.
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-servermedia-pipeline As a Claude Code plugin
/plugin marketplace add guinacio/claude-image-gen
/plugin install media-pipeline@media-pipeline-marketplaceCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of media-pipeline publish no list of tools, so we do not compare tools.
Settings each asks for
Only AWS Bedrock Data Automation asks for
AWS_BUCKET_NAMEAWS_PROFILEAWS_REGION
Only media-pipeline asks for
GEMINI_API_KEY (secret)GEMINI_DEFAULT_MODELIMAGE_OUTPUT_DIRIMAGE_PROVIDEROPENAI_API_KEY (secret)OPENAI_DEFAULT_MODEL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: AWS Bedrock Data Automation · What it can do: media-pipeline · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.