How-to

How to Connect Garmin to Claude or ChatGPT (2026)

Joules June 27, 2026 · 7 min read

Your Garmin already records the truth about your training — every ride, run, heart-rate drift and night of sleep. The obvious next move is to let the AI you already pay for read that data and reason over it in plain language. As of 2026 there are a few real ways to do it. Here's the honest guide: the routes that work, the one limit they all share, and how to close the gap between analyzing your Garmin history and actually coaching what comes next.

The one gate, up front

Adding a custom connector works on every Claude plan, including the free tier (free Claude allows one custom connector); on ChatGPT it needs a paid plan (Plus/Pro). (Some routes below also work with a free assistant account; we flag those.) MCP — the Model Context Protocol — is just the standard that lets an assistant talk to an outside data source live, so you ask questions in a normal chat instead of exporting files and pasting them in. With that out of the way, here are the routes, easiest first.

Route 1 — A hosted Garmin connector (the simplest path)

The lowest-friction option in 2026 is a hosted Garmin MCP connector: a cloud-run server that links your Garmin Connect account and gives you a personal connector URL to paste into your assistant. Several of these now exist (search "Garmin MCP connector" and you'll find current options and their setup pages). The shape is the same across them:

1. Sign in and authorize access to your Garmin Connect account on the connector's site.
2. Copy the personal MCP URL it gives you.
3. In Claude: Settings → Connectors → Add custom connector → paste the URL → save.
4. In ChatGPT: enable MCP servers under Settings → Beta features, then in a new chat open the Tools menu → Add custom MCP server → paste the URL, name it, save.

Then just ask: "What was my biggest training week this month?" or "How did my resting heart rate trend while my volume climbed?" One honest caution: a hosted connector holds credentials or a token for your Garmin account, so use one you trust, read what data it accesses, and prefer options that support revoking access. When in doubt, check the connector's own docs for exactly which data it reads and how to disconnect.

Route 2 — Go through Strava (often the cleanest)

If your Garmin already auto-syncs activities to Strava — a one-time toggle in Garmin Connect that most riders already have on — you can skip a Garmin-specific connector entirely and use Strava's official MCP connector instead. Strava shipped its own connector in 2026, so the data path is first-party and well-guarded:

1. In Garmin Connect, confirm the Strava auto-upload is on (Settings → Connected Apps → Strava).
2. In Claude or ChatGPT, add Strava's official connector from the connector directory / settings and authorize it.
3. Ask away — your Garmin rides are already in Strava, so the assistant reads them there.

The trade-off: Strava carries your activities (power, HR, pace, GPS) but not the full Garmin wellness layer — sleep, HRV, body battery, resting HR. If activities are what you care about, this is usually the cleanest route. We went deeper on it in Strava's MCP Connector for Claude: What It Does — and What It Can't (Yet).

Route 3 — A multi-source aggregator

If your data is spread across Garmin, Strava, WHOOP, Oura and Apple Health, an aggregator connector pulls many sources behind a single connection and exposes them all as tools the AI can query. One authorization, lots of sources, no manual exports — handy if you like cross-source questions ("did my HRV dip the week my volume spiked?"). It's the same read-side job as the others, just wider. We covered the current options in The Best Claude & ChatGPT Connectors for Cyclists.

Route 4 — Self-host (for the technical)

There are open-source community MCP servers for Garmin you can run yourself (you'll find them on GitHub). You host the server, give it your Garmin credentials locally, and point your assistant at it. Upside: nothing leaves your machine and you control exactly what's exposed. Downside: it's a developer setup (a terminal, a config file, keeping it running), and because these use unofficial access they can break when Garmin changes its login. Great if you're a tinkerer; overkill if you just want answers.

The catch every route shares: this is the read side

Once it's connected, the magic fades a little — and it's worth understanding why. Every route above gives the assistant your history. It becomes a genuinely good analyst: it can summarize a block, spot a trend, find your best 20-minute power. But ask it the question that actually matters —

That hedge — "treat this as a general suggestion" — is the read side showing its edge. The data tells the assistant what you did. It doesn't give it a season, a goal race, an intent for each week, or a way to grade what you actually do and adjust. That's coaching, and reading your Garmin history doesn't supply it. More data makes the analysis sharper; it doesn't turn analysis into a plan.

Closing the gap: add the coaching half

The missing half is an assistant that interviews you to build an athlete profile, sets a season backward from your goal race, prescribes each week with a purpose, and grades what you did so next week adapts. That's what Joules is built for: an MCP app that gives Claude or ChatGPT a cycling coach's brain. You add it the same way you added Garmin — paste the connector URL once.

A useful detail if your Garmin setup was fiddly: Joules is device-agnostic. It coaches from your goal and your real weeks, and it works even from just duration and perceived effort — so you get a real plan whether or not every data source is wired in. With a read connector also added, the two compose in one chat:

Read connector tells the assistant what you did; the coaching connector tells it what to do next, then checks whether you did it. That's the full loop — and it's the half a Garmin connection alone can't give you.

New to all this? Start with Can AI Be Your Cycling Coach? A Practical Guide for 2026, or see a real Joules training week — day by day, no install required.