Ext Ops Panel
Open dashboard
Comparison

AWS Bedrock Data Automation vs dominodatalab

AWS Bedrock Data Automation is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). dominodatalab is a plugin bundle for AI coding tools published by dominodatalab. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community). 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

Where each is published
MarketplaceAWS Bedrock Data Automationdominodatalab
Docker MCP Catalog Listed
Version: sha256:ca5c8e3d1bf0
Forks (GitHub): 1 835
Pulls (Docker Hub): 14 677
Stars (Docker Hub): 0
Stars (GitHub): 9 839
Not marked · First seen
Not listed
Claude Code: claude-plugins-official Not listed Listed
Version: 2026.603.3
Forks (GitHub): 3
Stars (GitHub): 7
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.0.0
Forks (GitHub): 3
Stars (GitHub): 7
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 dominodatalab
FactAWS Bedrock Data Automationdominodatalab
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)9 839 (better)7 (worse)
Pulls (Docker Hub) (differs)14 677No figure on Docker Hub
Forks (GitHub) (differs)1 835 (better)3 (worse)
Last release (differs)Not published2026-10-16
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: 02, secrets among them: 1
Parts of the bundle (differs)Not a bundle34
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/awslabs/mcpgithub.com/dominodatalab/domino-claude-plugin
Changes in the last 7 days00
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.

dominodatalab

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

Full Domino Data Lab platform support — workspaces, jobs, model deployment, experiment tracking, GenAI tracing, Spark/Ray/Dask, and app deployment for data science teams

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

dominodatalab As a Claude Code plugin

Claude Code
/plugin install dominodatalab@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 dominodatalab publish no list of tools, so we do not compare tools.

Settings each asks for

Only AWS Bedrock Data Automation asks for

  • AWS_BUCKET_NAME
  • AWS_PROFILE
  • AWS_REGION

Only dominodatalab asks for

  • DOMINO_API_KEY (secret)
  • DOMINO_HOST

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: dominodatalab · 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. 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