Everything starts the same way, whichever client you use.

Before you begin

  • Node.js 22 or newer. Check with node --version; get it from nodejs.org if needed.
  • A Garmin Connect account with a watch or scale syncing to it.
  • Chrome, Edge, Brave or Chromium for the sign-in window. Without a browser the sign-in falls back to the terminal, see Signing in.

Sign in once

npx -y garmin-mcp-cli login

A browser window opens Garmin’s own sign-in page. Sign in as you normally do, including a verification code or a CAPTCHA if Garmin asks. The window closes by itself. Only the tokens Garmin issues are stored, in ~/.garmin-mcp; your password never passes through the tool.

To check at any time:

npx -y garmin-mcp-cli status

Add the server to your client

Pick the guide for your client:

Optional: pre-load your data

Nothing is downloaded until a question needs it, and the first question about a period waits a few seconds for the download. If you prefer to have the last months ready, download them once:

npx -y garmin-mcp-cli sync --scope all --from 2026-07-01 --to 2026-09-30

Downloads are gentle with Garmin: 7-day chunks, short random pauses, at most 600 requests a day. A 90-day history takes about an hour and happens only once; stored days are never downloaded again.