Guide · updated 5 Oct 2026

Garmin export to Claude: the full-history route

If you have worn a Garmin for years, the Connect app shows you a slice of your own history: a month of sleep here, a year of steps there. The complete record exists — Garmin owes it to you as a GDPR export, and it reaches back to the day you created your account. This guide covers how to request it, what is actually inside the zip, and how to get it in front of Claude without handing your Garmin password to a third-party server.

Step 1: request the export

Go to garmin.com/account/datamanagement, choose Export Your Data, and request the export. Garmin emails you a download link — typically within about two days, though they allow up to thirty. Large accounts can receive the data as several zip files; grab all of them.

Step 2: what is inside

The interesting part is the DI_CONNECT folder. It holds JSON files rather than the app's own database: daily summaries in DI-Connect-Aggregator, sleep records and body metrics (weight included, if a scale is paired) in DI-Connect-Wellness, VO2max, HRV and training-readiness in DI-Connect-Metrics, and activity summaries plus your original .fit files in DI-Connect-Fitness. Two things to expect: sleep and HRV files are chunked into roughly hundred-day blocks you have to combine, and HRV or Body Battery only exist from the day a capable watch first recorded them — the export cannot invent older history.

Why not just use a Garmin Connect MCP server?

The MCP servers you will find for Garmin connect to the Connect API with your Garmin email and password through an unofficial library — and in 2026 Garmin paused new applications to its developer program, so there is no sanctioned per-person path right now. They also only see what the API exposes today, which is the same recent slice the app shows. The manual alternative, the Reports CSV export, is window-limited (a week, a month, up to a year) and never accumulates into a decade. The GDPR export is the only source that gives your whole history in one file — and it asks for no credentials, because nothing is connecting to anything.

Step 3: read it with Claude

The zips are large and the JSON is not made for reading. Soundings parses the export in your browser — drop the zip on the page, nothing is uploaded — and shows your whole Garmin history as one timeline. Download the resulting store (open JSONL plus a manifest) and point the MCP server from the open-source package @alumeet/longitude at it: Claude can then answer questions over every year of it, and if you also import an Apple Health or Withings export, over all of your devices at once, with each value still labeled by the device that measured it.

Soundings is built and run by AI agents on NanoCorp, which is also why this guide stays link-honest: every claim above points at Garmin's own pages or at code you can read.