TrainBud runs on your own machine — the client starts it, so there is no endpoint to ping. 58 installs a week from npm. Last commit 18 Sep 2026.
Talk to your own fitness data. Findings computed in code against your own 28-day baselines.
What the code does
We read the source, 2 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
<select name="units">
<option value="metric"${profile.units === "metric" ? " selected" : ""}>Metric (km, kg)</option>
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add trainbud -e 'GARMIN_EMAIL=<GARMIN_EMAIL>' -e 'GARMIN_PASSWORD=<GARMIN_PASSWORD>' -- npx -y trainbud{
"mcpServers": {
"trainbud": {
"command": "npx",
"args": [
"-y",
"trainbud"
],
"env": {
"GARMIN_EMAIL": "<GARMIN_EMAIL>",
"GARMIN_PASSWORD": "<GARMIN_PASSWORD>"
}
}
}
}[mcp_servers.trainbud]
command = "npx"
args = ["-y", "trainbud"]
env = { GARMIN_EMAIL = "<GARMIN_EMAIL>", GARMIN_PASSWORD = "<GARMIN_PASSWORD>" }{
"mcpServers": {
"trainbud": {
"command": "npx",
"args": [
"-y",
"trainbud"
],
"env": {
"GARMIN_EMAIL": "<GARMIN_EMAIL>",
"GARMIN_PASSWORD": "<GARMIN_PASSWORD>"
}
}
}
}{
"servers": {
"trainbud": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"trainbud"
],
"env": {
"GARMIN_EMAIL": "<GARMIN_EMAIL>",
"GARMIN_PASSWORD": "<GARMIN_PASSWORD>"
}
}
}
}Put your own values in place of
<GARMIN_EMAIL> (The email address for your Connect account. Stored only in your local .env; `npx trainbud setup` writes it for you), <GARMIN_PASSWORD> (Your Connect password. Stored only in your local .env. Accounts with MFA enabled are not supported, because the unofficial library this drives cannot complete that flow).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
ANTHROPIC_API_KEY (Optional, and only for the watch app's Ask card and daily insight. The MCP tools themselves need no model key: every finding is computed in code, and the model only phrases it).
Alternatives to TrainBud
same job, measured the same wayScores your code across 12 areas, with findings, fix prompts, and re-assessment in your AI agent
Index your codebase. AI searches instead of re-reading files. 94% token savings.
A marketplace for codebases: find, buy, clone, and update them, or list your own for sale.
Code review on your own machine, for you and your coding agent. Nothing leaves your computer.
Finds the LLM model IDs pinned in your code that vendors have already switched off, or have dated to
Dates every quantum-vulnerable algorithm in your code against the NIST IR 8547 clock: deprecated aft
Publish apps from Claude Code, Codex or Cursor to your team, behind sign-in, with a database.
No-data MCP handoff for local Claude Code to Codex harness moves. $49 lifetime.
TrainBud — questions
Answers built from our own checks of this server.