AWS Bedrock Data Automation vs cascade-img
AWS Bedrock Data Automation is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). cascade-img is an MCP server published by laffeyp. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 |  cascade-img |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ca5c8e3d1bf0 Forks (GitHub): 1 835 Pulls (Docker Hub): 14 680 Stars (Docker Hub): 0 Stars (GitHub): 9 839 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.1 Downloads/month (PyPI): 85 Downloads/week (PyPI): 22 Forks (GitHub): 0 Stars (GitHub): 2 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 | cascade-img |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 839 (better) | 2 (worse) |
| Pulls (Docker Hub) (differs) | 14 680 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 835 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-bedrock-data-automation-mcp-server) | On your machine (cascade-img) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | 4, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | github.com/laffeyp/cascade-img |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
Analyze documents, images, videos, and audio.
cascade-img
LLM-operable Midjourney pipeline: 21 MCP tools to compose, generate, curate with vision, and log.
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-servercascade-img As a local MCP server: PyPI package
claude mcp add --env "DISCORD_USER_TOKEN=<YOUR_DISCORD_USER_TOKEN>" --env "MJ_CHANNEL_ID=<YOUR_MJ_CHANNEL_ID>" --env "MJ_IMAGINE_VERSION=<YOUR_MJ_IMAGINE_VERSION>" --transport stdio cascade-img -- uvx --from cascade-img cascade-mcp cascade-imgRequires: DISCORD_USER_TOKEN (secret), MJ_CHANNEL_ID, MJ_IMAGINE_VERSION
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of cascade-img 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 cascade-img asks for
CASCADE_BRIDGE_URLDISCORD_USER_TOKEN (secret)MJ_CHANNEL_IDMJ_IMAGINE_VERSION
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: cascade-img · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.