Suunto MCP

[Suunto MCP]

Suunto MCP

[CI] [npm] [License: MIT] [suunto-mcp MCP server]

Ask Claude anything about your training. Suunto MCP connects your Suunto watch data to Claude so you can just talk to your data instead of clicking through dashboards.

Built by a Suunto user who wanted to ask "how was my last long run?" and get a real answer with numbers — and to feed live training data into a personal AI coach.

🏃 For regular Suunto users: Suunto's API docs say access is for commercial partners only — that's not the full picture. Private users get access too. It just takes 3–4 weeks for approval after you apply. Submit, wait, enjoy. Don't let that disclaimer stop you. ✅

What you can do

Once it's set up, just ask:

• "How many kilometers did I run this month?"
• "Compare my last three long runs — has my heart-rate drift improved?"
• "How did my heart rate hold up set by set in last night's gym session?"
• "What's my average resting HR trend over the last two weeks?"
• "Summarize my training week in the style of a coaching report."
• "I've been feeling off — how do my recovery scores compare to last month?"
• "Find every workout where I averaged above 160 bpm."
• "Which of my runs this year had the most elevation?"

Claude figures out what data to pull. You just ask.

It's not just read-only either — Claude can push things to your watch too:

• "Plan tonight's gym session and send it to my watch."
• "Upload yesterday's Garmin export as a Suunto workout."
• "Export my last route as GPX so I can share it."

See What you can push to your watch below.

🤖 Don't want to do this yourself? Let Claude Code install it

If you already have Claude Code, you don't need to run a single terminal command. Just open it and say:

"Please install and set up suunto-mcp from https://github.com/googlarz/suunto-mcp"

Claude Code will clone the repo, run all the install commands, and add everything to your Claude Desktop config — on its own. That's exactly how this project's author set it up: no manual terminal work.

Three things stay yours no matter what, by design, not because of missing tooling:

1. Creating the apizone.suunto.com account — Claude can't create accounts on your behalf.
2. The apizone web form (naming your app, revealing your subscription key) — it's your account session; Claude tells you exactly where to click, but can't click there for you.
3. Clicking "Authorize" during login — that's OAuth working as intended. An app that could approve its own access wouldn't be secure.

Claude will tell you exactly what to do and when for each of these.

If you want to do it manually, keep reading.

What you need

Before starting, make sure you have:

• A Suunto watch synced to the Suunto app (any modern model — Race, Vertical, 9 Peak, 5 Peak, Ocean, etc.)
• Claude Desktop (or another MCP-compatible AI app)
• Node.js — free, download here, choose the "LTS" version
• Git — free, download here
• ~5 min to submit + 3–4 week wait for Suunto approval + ~15 min to install

Once it's done, you never redo it.

Setup

Prefer one guided walkthrough with a pacing choice up front (fast path vs. explained-step-by-step) and a proper explanation of how syncing works? See GETTING_STARTED.md. What follows here is the same steps in reference form.

The setup has three parts:

1. Register with Suunto's developer portal — tells Suunto your app is allowed to read your data
2. Install and configure — gets the software running on your computer
3. Connect to Claude — lets the AI find and use it

Try it without an account (demo mode)

Suunto takes 3–4 weeks to approve API access. You don't have to wait to see what this does: with SUUNTO_DEMO=1 the server runs on realistic synthetic data (about 8 weeks, ending today) and needs no Suunto account, no credentials and no network. Only Node.js is required. Add this to the mcpServers block of the Claude Desktop config (the file from Step 9), then restart Claude:

{  "mcpServers": {    "suunto-demo": {      "command": "npx",      "args": ["-y", "suunto-mcp"],      "env": { "SUUNTO_DEMO": "1" }    }  }}

What works: every read tool and the four prompts (suunto-morning, suunto-weekly, suunto-gym-today, suunto-gym-review) — workouts with guide-labelled gym laps (three sessions a week, one of them with a planted deviation for compare_workout_to_plan), one or two runs a week with TSS, nightly sleep with stages, score and HRV plus the odd nap, recovery every 30 minutes, daily steps and energy, two routes, three guides, and a small FIT file with heart rate for get_workout_fit and get_workout_rest_profile. Training load, baselines and snapshots are computed from that data by the normal code.

What does not: anything that writes (upload_workout, upload_route, push_*_guide, delete_guide, generate_daily_digest, log_session) writes nothing and only returns a short note on what it would do with real credentials. get_upload_status has no uploads to find.

You can't mistake demo data for real data: every tool result is JSON with a top-level "demo": true (a result that is a list, or text such as a GPX file, comes back as { "demo": true, "data": … }), the server's instructions and the prompts say the data is synthetic, and the startup line says DEMO MODE. Errors are unchanged. npm run doctor with SUUNTO_DEMO=1 just reports that demo mode is on. When your API access arrives, remove SUUNTO_DEMO and follow the setup below. Demo mode applies to the MCP server only, not to the terminal commands.

Part 1: Register with Suunto's developer portal (~5 min to submit, then wait 3–4 weeks)

Suunto has a free developer portal called apizone where you register apps that can access your data. You'll create an account, subscribe to the data plan, and register a small "app" — don't worry, there's nothing to build, it's just a name and a password you make up.

Step 1: Create your apizone account

Go to apizone.suunto.com and sign up or sign in.

Use the same email you use for the Suunto app. If you have a Sports Tracker account, that works too — it's the same login system.

Step 2: Subscribe to the Developer API

After signing in, follow the How to start guide — it walks you through subscribing to the Developer API. This is free and gives you access to your workout history.

Heads up: Suunto's website states that API access is only for commercial partners — ignore that. Private users do get access, it just takes 3–4 weeks for the subscription to be approved. Submit it and wait. It will come through.

You may see other products like "Sleep API", "Recovery API", "Daily Activity API". The Developer API is enough to get started (workouts). Subscribe to the other three as well if you want sleep, recovery, steps, the daily snapshot or the daily digest — they are listed next to the Developer API, and you can also add them later.

⏳ Stop here and wait. Once you've subscribed, Suunto needs to approve your request. This takes 3–4 weeks. You'll get an email when it's done. Come back to Steps 3–4 only after your subscription shows as Active in your apizone profile.

Step 3: Register your app (do this after approval)

You're going to tell Suunto: "I have a small program, here's its name and a secret password — please let it read my data."

1. Go to your apizone profile page

2. Scroll down to OAuth application settings

3. Fill in the form:

   Field	What to enter
   App name	suunto-mcp (or anything you like)
   Client secret	Make up a unique password — something only you'd know, e.g. alice-suunto-2026 with your own name. Write it down. Don't use this exact example.
   Redirect URI	http://localhost:8421/callback — copy this exactly

4. Click Save

After saving, the form shows a Client ID — a long code that Suunto generated for you. Copy it.

What are these three things? — Client ID: your app's username, generated by Suunto — Client Secret: your app's password, chosen by you — Redirect URI: where Suunto sends you back after you approve access — must match exactly, typos break it

The Client Secret is never shown again after you save. If you forget it, just set a new one in the same form.

Step 4: Get your subscription key (do this after approval)

The subscription key is a second passcode that goes on every data request. Here's how to find it:

1. Still on the apizone profile page
2. Scroll to the Subscriptions section
3. Your Developer API subscription is listed there. Next to it you'll see a Primary Key — click the button next to it to reveal it, then copy the key.

Save all three values before continuing — you'll need them in Part 2:

• Client ID (from the OAuth app form above)
• Client Secret (the password you made up)
• Subscription Key (from the Subscriptions section)

Part 2: Install and configure (~10 min, after Suunto approves you)

Used the "Let Claude Code install it" option above? Claude already ran every command below — skip to Part 3. These steps are for anyone doing it by hand.

Step 5: Download the code

Open Terminal on Mac (press ⌘Space and type "Terminal") or Command Prompt on Windows. Then run these commands one at a time:

git clone https://github.com/googlarz/suunto-mcpcd suunto-mcpnpm installnpm run build

This downloads the code, installs what it needs, and builds it. Takes 1–2 minutes. If you see any errors, check the Troubleshooting section.

Step 6: Add your credentials

You'll create a file called .env in the suunto-mcp folder and put your three values in it. Even if Claude is doing the rest of this for you, type these three values in yourself rather than pasting them into the chat — keeps them out of your conversation history.

On Mac:

cp .env.example .envopen -e .env

This copies the template and opens it in TextEdit. Replace each placeholder with your actual values, then save and close.

On Windows:

copy .env.example .envnotepad .env

The file looks like this — replace the parts after the = signs:

SUUNTO_CLIENT_ID=your-client-id-hereSUUNTO_CLIENT_SECRET=your-client-secret-hereSUUNTO_SUBSCRIPTION_KEY=your-subscription-key-here

Save and close the file.

Only if you want to push guided workouts to your watch (see What you can push), add one more line: SUUNTO_APP_NAME=your-app-name-here — it must exactly match the app name you registered on apizone.suunto.com in Step 3, or the watch will reject the upload. Not needed for anything else.

Step 7: Pair your Suunto account

npm run auth

Here's exactly what happens:

① Terminal — you see a long URL printed and the message "Opening Suunto authorization in your browser…"

② Browser opens — Suunto's login page appears. It looks identical to the Suunto app login: email + password fields at the top, then "Sign in with Apple" and "Sign in with Facebook" below. Sign in with whichever you use.

③ Permissions screen — after logging in, a screen appears asking you to approve access for "suunto-mcp". It lists what the app will be able to read (your workouts). Click Authorize.

④ Browser confirmation — the page shows: "Suunto MCP connected. You can close this tab."

⑤ Terminal confirmation — prints: "Paired successfully. Tokens saved."

Done — you won't need to do this again. The connection stays active and renews itself automatically.

Browser didn't open automatically? Copy the long URL from the terminal and paste it into your browser manually.

Step 8: Check everything is working

npm run doctor

This runs a health check. You should see output like:

Suunto MCP — health check
  ✓  Node version             20.18.0 (require ≥ 20)  ✓  Credentials              client_id, client_secret, subscription_key set  ✓  Network → cloudapi-oauth.suunto.com   reachable (HTTP 200)  ✓  Pairing                  paired (user: your-username), token expires in 47 min  ✓  API probe (list_workouts)  received 1 workout

The exact lines vary a little, and more appear for the Sleep, Recovery and Daily Activity products. If any line shows ✗, the message tells you exactly what to fix — resolve it before moving on. A ! is only a warning (for example, an optional product you haven't subscribed to).

Part 3: Connect to Claude Desktop (~5 min)

Used the "Let Claude Code install it" option? This part is done too — Claude edited your config directly. Restart Claude Desktop and jump to Step 11.

Now you'll tell Claude Desktop where to find Suunto MCP.

Step 9: Open the Claude config file

Open this file in a text editor (create it if it doesn't exist yet):

• Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Quick way on Mac — run this in Terminal:

mkdir -p ~/Library/Application\ Support/Claude && open -e ~/Library/Application\ Support/Claude/claude_desktop_config.json

Quick way on Windows — run this in Command Prompt:

notepad "%APPDATA%\Claude\claude_desktop_config.json"

(If it asks "file not found — create it?", click Yes.)

Step 10: Add Suunto MCP

First, find the actual path to the suunto-mcp folder. In Terminal, while inside the folder, run:

pwd

It'll print something like /Users/yourname/suunto-mcp. Copy that.

Now paste the following into the config file. Replace /Users/yourname/suunto-mcp with the path you got from pwd, and replace the credential placeholders with your actual values.

If the file already has other servers configured, don't replace the whole file — just add the "suunto" section alongside them. The structure must be valid JSON, so keep all the curly braces balanced. When in doubt, compare your file to the example below.

If the file is empty, paste the whole block as-is.

{  "mcpServers": {    "suunto": {      "command": "node",      "args": ["/Users/yourname/suunto-mcp/dist/index.js"],      "env": {        "SUUNTO_CLIENT_ID": "your-client-id",        "SUUNTO_CLIENT_SECRET": "your-client-secret",        "SUUNTO_SUBSCRIPTION_KEY": "your-subscription-key"      }    }  }}

To also push guided workouts to your watch, add one more line inside "env": put a comma at the end of the SUUNTO_SUBSCRIPTION_KEY line, then add "SUUNTO_APP_NAME": "your-app-name" (exactly the app name registered on apizone) on a new line after it. If you only ask Claude about your data, you don't need it.

Anything the server needs must be in this "env" block — a .env file is only read by the terminal commands (npm run auth, npm run doctor, the CLI) when you run them from this folder.

Save the file.

Step 11: Test it

Three things, in order — this is the only part of setup nothing can do for you:

1. Quit Claude Desktop completely. Not just closing the window — ⌘Q on Mac, or right-click the icon in the taskbar → Quit on Windows. Config changes only load on a fresh start.
2. Reopen Claude Desktop.
3. Ask it:

   "What was my most recent workout?"

If Claude answers with your actual sport, date, and distance — you're done. If it doesn't, don't guess — go to Troubleshooting.

Example conversation

You:    Compare my last three long runs. Has my heart-rate drift improved?
Claude: Looking up your workouts…        Found 3 runs over 90 minutes in the last 6 weeks:          • Apr 12 — 22.4 km, 2h09, avg HR 148, last-30min drift +6 bpm          • Apr 19 — 24.0 km, 2h21, avg HR 144, last-30min drift +4 bpm          • Apr 26 — 25.1 km, 2h28, avg HR 142, last-30min drift +2 bpm        Drift is trending down despite slightly longer runs — your aerobic        base is improving. Pace at the same HR is also ~3 s/km faster.

What data is available

To add sleep, recovery, or daily activity: go back to apizone.suunto.com, find each product, and subscribe. Then run npm run doctor to confirm they're active.

What you can push to your watch

Suunto MCP isn't read-only. Claude can also send things back to your account:

Guided workouts show up as a SuuntoPlus Guide: exercise name and weight/reps on screen, lap button advances to the next one, a stopwatch (not a countdown) between exercises with a preview of what's next, a vibrate when a new exercise starts, and a "session complete" screen at the end. There's no live push to the watch itself — it appears after your phone's next normal Suunto app sync, same as any other watch data.

This pairs naturally with a coaching workflow: describe your goals, equipment, and current lifts to Claude, and it can write a real progressive program and push each session directly — see Pairs well with health-skill below for recovery-aware programming.

Prompts

MCP clients that support prompts (for example Claude Desktop) list these as one-click workflows. Each fills in the exact dates and tells Claude which tools to call.

Daily health digest

Ask Claude "generate my daily digest for yesterday" and it writes a color-coded markdown summary — steps, sleep, recovery balance, HRV, and a training-load model (Fitness/Fatigue/Form) — appended to SUUNTO_HISTORY.md in the folder the server runs from (set SUUNTO_DIGEST_HISTORY_PATH to choose another file).

Fitness (CTL), Fatigue (ATL), and Form (TSB) aren't Suunto API fields — there's no endpoint for them. They're computed here from each workout's real tss.trainingStressScore using standard 42-day/7-day exponential decay, the same math training-load tools like TrainingPeaks use. The running values persist in ~/.suunto-mcp/averages.json (override with SUUNTO_DIGEST_AVERAGES_PATH) since there's nowhere else to keep them.

How close is it to the watch? Checked on one day against the Suunto app: Fatigue matched (11), Form matched (2), Fitness came out about 1 lower (13.1 vs 14). Treat Fitness as ±1 of your watch; seed it from the app if you need it exact.

A few things worth knowing before you rely on it:

• CTL/ATL start at 0 on first use and take 4–6 weeks to converge to a realistic number — there's no API to read your watch's own displayed Fitness/Fatigue. To skip the cold-start, tell Claude the numbers off your watch on your very first digest ("my watch shows Fitness 42, Fatigue 38, seed the digest with those") — or pass --seed-ctl 42 --seed-atl 38 on the CLI. Only works on the first-ever digest; ignored after that.
• TSB colors match your watch's own legend (🔵 Optimal >+10, 🟢 Balanced 0 to +10, 🟡 Compromised −10 to 0, 🔴 Strained <−10) — not an invented scale.
• Ramp rate (this week's CTL vs. 7 days ago) has its own scale: 🔴 above +8/week means you're loading too fast — real injury risk, not just "good progress." 🟢 +3 to +8 is building well, 🟡 −2 to +2 is holding steady, 🟠 below −2 means fitness is slipping.
• Recovery Balance is reported as morning (the lowest point overnight) vs. peak (the highest point that day) — they use different color scales, since peak is naturally higher than the overnight low.
• HRV below your normal range for 2+ days in a row, or morning recovery below 65% for 2+ days in a row, adds a note to check your blood pressure — sustained low HRV/recovery is a real physiological signal worth a second data point on.
• Rolling baselines track each metric separately, with a separate bucket for "party nights" (>20,000 steps) so an outlier day doesn't skew your normal-day average.
• Run dates in chronological order. The digest refuses a date on or before the last one it processed, so a missed day can't be filled in after a later one has run — the running totals move forward one day at a time.
• Requires Sleep and Recovery API subscriptions on apizone for those sections to populate — without them, the digest still generates, those sections just say "no data" instead of erroring.

CLI: suunto-mcp daily-digest 2026-04-20 [--seed-ctl 42 --seed-atl 38]. MCP tool: generate_daily_digest.

Troubleshooting

Always run npm run doctor first — it pinpoints most problems automatically.

FAQ

Is this safe? Will Suunto lock my account? Suunto built this API specifically for people to connect their own tools — it's explicitly allowed. You're using it exactly as intended.

Is my data leaving my computer? Your data travels directly between your computer and Suunto's servers. Suunto MCP is just the bridge. When Claude asks about your workouts, it goes: Claude → Suunto MCP (on your machine) → Suunto's servers → back. No third-party services see your data.

Which Suunto watches work? Any watch that syncs to the Suunto app: Race, Vertical, 9 Peak Pro, 9 Peak, 5 Peak, Wing, Ocean, and older models. If it appears in your Suunto app, it works here.

Do I need to do anything when I record a new workout? No. Just ask Claude — it always pulls live data from Suunto.

What if I want to disconnect and stop using this? See Disconnecting below. You can fully revoke access in under a minute.

Can I use this with AI apps other than Claude? Yes — anything that supports MCP: Claude Code, Cursor, Windsurf, and others.

My Suunto app username is different from my email — which do I use? Use your email address to sign in to apizone. Your username will appear once you're authenticated.

Privacy

• All data flows directly between your computer and Suunto's servers. No third-party servers, no analytics.
• Your login credentials are stored locally at ~/.suunto-mcp/tokens.json — not uploaded anywhere.
• Suunto shows your connected app as "suunto-mcp" in apizone → profile → Authorized applications. You can revoke it there at any time.
• The AI only sees data it explicitly requests for your question — not your entire history at once.

Upgrading

• npx: npx -y suunto-mcp fetches the newest version on a fresh start; if you pinned a version in args, change it. Restart Claude afterwards.
• Cloned folder: git pull, npm install, npm run build, then restart Claude.

See CHANGELOG.md for what changed.

Environment variables

Set these in the env block of your Claude config (or in .env for terminal commands).

Local files

Besides the tokens, suunto-mcp keeps these on your computer (all under ~/.suunto-mcp/ unless you move them with the variables above; folders 0700, files 0600):

• cache/<workoutKey>.json — what get_exercise_history derived from a finished guided session (exercises, loads, sets, rest recovery; a few KB, never the raw FIT file). Sessions under 24 hours old are not cached. Safe to delete at any time: it is rebuilt on the next call (rm -rf ~/.suunto-mcp/cache). SUUNTO_CACHE=off stops it being read or written.
• journal.json — what you told log_session. This is your own record, nothing rebuilds it: delete it (rm -f ~/.suunto-mcp/journal.json) only if you want it gone.

Disconnecting

To fully remove access:

1. Log in to apizone.suunto.com → profile → Authorized applications → remove suunto-mcp. Suunto immediately stops honoring the connection.
2. Delete local credentials:
   bash

   rm -f ~/.suunto-mcp/tokens.json

   If you used SUUNTO_TOKEN_STORAGE=keychain, delete the "suunto-mcp" entry in your system keychain instead. The daily digest also keeps ~/.suunto-mcp/averages.json and SUUNTO_HISTORY.md, get_exercise_history keeps ~/.suunto-mcp/cache/ and log_session keeps ~/.suunto-mcp/journal.json — delete them too if you want the health data gone (rm -rf ~/.suunto-mcp/cache ~/.suunto-mcp/journal.json).
3. Remove the "suunto" block from your Claude config and restart Claude.

Pairs well with health-skill

If you use googlarz/health-skill — a Claude skill for symptom triage and health Q&A — you can connect both to Claude: health-skill handles the health side while Claude reads your training, sleep, and recovery data from Suunto MCP in the same conversation. Together they can answer questions like "given my recovery scores this week, should I keep tomorrow's interval session?" with real numbers.

The same combination works for planning, not just Q&A: Claude can check your actual HRV and sleep before writing a session, scale it back on a bad recovery day instead of a generic one, and push the result straight to your watch with push_strength_guide (gym) or push_interval_guide (cardio). Ask for it directly — "check my recovery and plan today's gym session" — no extra setup beyond having both connected.

To also store your daily step counts in health-skill's own records, run suunto-mcp sync-to-health-skill --health-root <your health folder> (add --person-id for a household member). It copies steps only, and only for days that are finished — today's total is picked up tomorrow.

For the full version — real progressive-overload programming that persists week to week instead of a one-off ask — install googlarz/gym-skill: /gym setup once, then /gym plan//gym today//gym log//gym review going forward.

Advanced

export SUUNTO_CLIENT_ID=your-client-id SUUNTO_CLIENT_SECRET=your-client-secret SUUNTO_SUBSCRIPTION_KEY=your-subscription-keynpx -p suunto-mcp suunto-mcp-authnpx -p suunto-mcp suunto-mcp-doctor

{  "mcpServers": {    "suunto": {      "command": "npx",      "args": ["-y", "suunto-mcp"],      "env": {        "SUUNTO_CLIENT_ID": "your-client-id",        "SUUNTO_CLIENT_SECRET": "your-client-secret",        "SUUNTO_SUBSCRIPTION_KEY": "your-subscription-key"      }    }  }}

claude mcp add suunto -e SUUNTO_CLIENT_ID=your-client-id -e SUUNTO_CLIENT_SECRET=your-client-secret -e SUUNTO_SUBSCRIPTION_KEY=your-subscription-key -- node /full/path/to/suunto-mcp/dist/index.js

node dist/index.js list-workouts --limit 10node dist/index.js get-workout <workoutKey>node dist/index.js get-workout-laps <workoutKey>node dist/index.js get-daily-snapshot 2026-04-20node dist/index.js get-daily-snapshot 2026-04-14 --to 2026-04-20node dist/index.js get-sleep 2026-04-20node dist/index.js list-recovery --from 2026-04-01 --to 2026-04-30

npm run webhook

SUUNTO_TOKEN_STORAGE=keychain npm install @napi-rs/keyringSUUNTO_TOKEN_STORAGE=keychain npm run auth

Credits

• Suunto APIzone — for opening their API to everyone
• Model Context Protocol — the standard this speaks
• fit-file-parser — FIT binary decoding

License

MIT — use it, fork it, improve it.