AWS Bedrock Data Automation vs experiment-tracker
experiment-tracker is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
AWS Bedrock Data Automation is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). experiment-tracker is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-30. A plugin in this pair is no longer listed on any marketplace we read, 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 835 Pulls (Docker Hub): 14 828 Stars (Docker Hub): 0 Stars (GitHub): 9 848 Not marked · First seen |
Not listed |
| Community marketplace barnburner121/claude-plugin-marketplace | Not listed | Removed on 2026-10-18 Version: 1.0.0 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 | experiment-trackerno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 9 848 | 3 |
| Pulls (Docker Hub) (differs) | 14 828 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 835 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-bedrock-data-automation-mcp-server) | On your machine (@barnburner121/plugin-hub-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 |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/awslabs/mcp | github.com/barnburner121/claude-plugin-marketplace |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-14 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of experiment-tracker
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Skills for tracing, evaluating, and improving AI agents with MLflow. Supports the full agent improvement loop: instrument → trace → evaluate → iterate → validate.
-
ML model training pipelines, hyperparameter tuning, model deployment automation, experiment tracking, and MLOps workflows
-
ML model training pipelines, hyperparameter tuning, model deployment automation, experiment tracking, and MLOps workflows
-
ml-research
Machine learning experiments, training, evaluation and reproducible papers.
-
ML engineering plugin: Give your AI coding agent ML engineering superpowers.
-
Agent skills for CMF — instrument ML pipelines, track artifacts, sync metadata, and query lineage
What each says it does
AWS Bedrock Data Automation
Analyze documents, images, videos, and audio.
experiment-tracker
Generate ML experiment tracking with MLflow
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-serverexperiment-tracker
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 experiment-tracker publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of experiment-tracker publish no settings it asks for, so we do not compare settings.
What it can do: AWS Bedrock Data Automation · What it can do: experiment-tracker · 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.