experiment-tracker vs io.github.us-all/mlflow
experiment-tracker is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
experiment-tracker is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. io.github.us-all/mlflow is an MCP server published by us-all. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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 |  io.github.us-all/mlflow | |
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.12.7 Downloads/month (npm): 154 Downloads/week (npm): 58 Forks (GitHub): 0 Stars (GitHub): 1 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 | experiment-trackerno longer listed · | io.github.us-all/mlflow |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | 1 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | On your machine (@us-all/mlflow-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 8, secrets among them: 2 |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | github.com/us-all/mlflow-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
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
experiment-tracker
Generate ML experiment tracking with MLflow
io.github.us-all/mlflow
MLflow MCP — experiments, runs, registered models, versions, traces, assessments (MLflow 3)
How to run each
experiment-tracker
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.us-all/mlflow As a local MCP server: npm package
claude mcp add --env "MLFLOW_TRACKING_PASSWORD=<YOUR_MLFLOW_TRACKING_PASSWORD>" --env "MLFLOW_TRACKING_TOKEN=<YOUR_MLFLOW_TRACKING_TOKEN>" --env "MLFLOW_TRACKING_URI=<YOUR_MLFLOW_TRACKING_URI>" --transport stdio mlflow -- npx -y @us-all/mlflow-mcpRequires: MLFLOW_TRACKING_PASSWORD (secret), MLFLOW_TRACKING_TOKEN (secret), MLFLOW_TRACKING_URI
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
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: experiment-tracker · What it can do: io.github.us-all/mlflow · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.