TrainBud vs io.github.dropflyai/fitfly-engine
TrainBud is an MCP server published by Zsadigzade. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.dropflyai/fitfly-engine is an MCP server published by dropflyai. Marketplaces we read that list it: 1 (Official MCP Registry). 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.9.0 Downloads/month (npm): 497 Downloads/week (npm): 38 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.2.0 No figure published 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 | TrainBud | io.github.dropflyai/fitfly-engine |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (trainbud) | Remote server (workout-engine-production-5dd7.up.railway.app/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 2 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/zsadigzade/trainbud | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago |
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
TrainBud
Talk to your own fitness data. Findings computed in code against your own 28-day baselines.
io.github.dropflyai/fitfly-engine
Deterministic fitness coaching engine: adaptive programs, progression math, readiness autoregulation
How to run each
TrainBud As a local MCP server: npm package
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --env "GARMIN_EMAIL=<YOUR_GARMIN_EMAIL>" --env "GARMIN_PASSWORD=<YOUR_GARMIN_PASSWORD>" --transport stdio trainbud -- npx -y trainbud start
Requires: ANTHROPIC_API_KEY (secret), GARMIN_EMAIL, GARMIN_PASSWORD (secret)
io.github.dropflyai/fitfly-engine As a remote MCP server
claude mcp add --transport http fitfly-engine https://workout-engine-production-5dd7.up.railway.app/mcp --header "Authorization: Bearer <YOUR_TOKEN>"
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.dropflyai/fitfly-engine has a remote endpoint we check. How we check endpoints
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 io.github.dropflyai/fitfly-engine publish no settings it asks for, so we do not compare settings.
What it can do: TrainBud · What it can do: io.github.dropflyai/fitfly-engine · Compare two other plugins
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.