‹ blog · 2026-05-11 · 4 min read

How to connect Garmin to Claude or ChatGPT.

Three clicks, one link, then ask. Here's the setup, what your AI can actually see, and the prompts worth your time.

How to do it

Go to stats.training and subscribe.$10/month. Cancel any time from your account.
Log in with Garmin or Strava.One short form. Garmin uses your account credentials; Strava is a standard OAuth click-through.
Copy your personal MCP URL and paste it into Claude or ChatGPT's connector settings.That's it. From the next message onward, your AI can read live numbers from your training.

Garmin Connector card in Claude.ai settings showing the personal MCP URL and a Configure button. — Pasted into Claude's custom connectors. ChatGPT looks similar.

Now you can call Garmin or Strava tools directly from your favorite AI dashboard.

What your AI can actually see

The connector exposes 25 tools spanning the same categories you'd browse in Garmin Connect:

Activities. Splits, pace, heart rate, power, individual lap detail.
Sleep. Stages, score, restless moments, SpO₂, overnight respiration.
Recovery. HRV trend, body battery, resting heart rate, daily stress.
Training load. Status, readiness, morning readiness, hill score.
Performance. VO₂ max, fitness age, race predictions for 5K to marathon.
Weekly aggregates. Steps, intensity minutes, stress totals.

For Strava users, the equivalent activity feed, athlete stats, zones, and stream data (heart rate, pace, cadence per second).

It's read-only. Your AI can't push a workout to your watch or edit anything on your account.

Use cases

The novelty wears off fast if you only ask "show me my last run."

Where it gets interesting is when you ask things Garmin's UI doesn't make easy.

Claude chat showing the user's question 'Am I ready for a sub 20 5K? use my Garmin data' and Claude calling multiple Garmin tools in response. — One question, Claude pulls the relevant tools on its own.

"Compare my last four long runs. Pace, average HR, and how my HR drifted across each one." Garmin shows you one activity at a time. Claude can pull all four, line them up, and tell you whether your cardiac drift is shrinking. That's a real signal aerobic fitness is improving.

"What's the trend in my resting heart rate over the last 30 days? Anything unusual?" Useful before a hard week. A creeping RHR usually means you're under-recovered before you feel it.

"My HRV tanked last night. What did I do yesterday that might explain it?" Claude can cross-reference sleep, training load, stress, and the previous day's activity. Often the answer is boring (late workout, low sleep) but having it laid out is faster than clicking through five screens.

"Based on my last 8 weeks, what 10K time should I realistically target?" Garmin gives you a race predictor number. Claude can sanity-check it against your actual workout paces and tell you whether the prediction is optimistic.

"Build me a recovery-week plan based on this week's training load." This is where having a conversation beats having a dashboard. Claude can suggest specific sessions, you push back, it adjusts.

"Look at the last 4 weeks. Am I ramping volume too aggressively for where my readiness scores are sitting?" The 10% rule is a heuristic. Asking the question against your own load and readiness trend is the real version.

"I have a half marathon in 6 weeks. Given my current fitness and weekly pattern, write me a build-and-taper plan." You won't take it as gospel. But it's a better starting point than a generic plan from a magazine, and you can iterate on it.

"Do I sleep worse the night after interval sessions? Check the last two months." The kind of correlation question no built-in dashboard asks. Sometimes the answer is yes and the fix is moving sessions earlier.

What about privacy

Nothing about your training lives on stats.training's servers. When Claude wants a number, it sends a tool request, the bridge fetches it from Garmin, hands the number back. The conversation itself never touches the bridge, only what number to look up.

When you're done, you revoke access from Garmin Connect (or strava.com/settings/apps) and the link dies on the spot. You don't even have to come back to the site to cancel data access.

The point

A dashboard tells you things. A chat lets you ask things, including the half-formed questions you'd ask a coach in the car after a session. Garmin and Strava hold the data.

Claude and ChatGPT are good at thinking through it. The only thing missing was a wire between them.

If you try it, the queries that pay off most are the ones with context: comparisons across weeks, trend reads, planning decisions that depend on yesterday and the day before.

Claude's structured answer: headline number, VO2 max, training load, current status, and fitness trend, with a short read of where the athlete actually stands. — What the answer looks like. Numbers in, plan out.

Start there.

Ready to try it?

$10/month. Cancel any time. Works with Claude (Free, Pro, Max), ChatGPT, and any MCP-compatible AI.

Connect → See more use cases

‹ back to blog Originally posted on Medium