Can Claude Analyze Polar Flow Data and Nightly Recharge?

Claude can analyze a Polar Flow CSV you upload, or read selected Polar records through Apple Health or Android Health Connect. These phone connections are indirect. Claude's mobile Health feature is currently a US Pro or Max beta, and Android requires version 14 or later. We did not verify an official Polar fitness MCP connector or test an authenticated account. Claude iPhone guide, Claude Android guide, checked September 30, 2026.

Nightly Recharge needs its own route check. Polar documents API access to that assessment, but its phone-sharing lists do not establish that the Nightly Recharge status itself transfers. A model reading sleep duration has not thereby retrieved Polar's recovery result. Polar AccessLink Dynamic API, Polar Apple Health fields, Polar Health Connect fields.

We make coach steve, an AI running coach you can text. We recommend it when you want a conversation focused on a running goal and the week you can manage. This guide does not claim a coach steve Polar integration or score-driven automatic changes.

Pick the route before asking for a trend

A single-session pacing question is a good reason to start with CSV. A recent sleep-timing question may fit the phone route. A repeated analysis of named Polar assessments requires either the original values you supply or a verified authorized service exposing the relevant API fields.

Before comparing months, establish whether both periods are present. “No rows returned” and “no training occurred” mean different things. That distinction matters more than the fluency of the resulting summary.

How do you export a Polar workout for Claude?

In Polar Flow on the web, open Diary → training session → Export → CSV. Polar also offers FIT, TCX and GPX, with GPS routes in GPX or FIT and other training measures available in CSV, TCX or FIT. Multisport exports use GPX, FIT or TCX. Polar's individual-session export guide.

CSV is among Claude's supported upload types. FIT, TCX and GPX are not in its standard file list. If you transform one of those formats into a readable table, label the conversion and preserve the original. For a basic session comparison, the documented CSV route avoids needing to establish a separate binary-file tool. Claude file support.

Inspect the actual columns before uploading. Keep the session date, sport, duration, units and sampling interval with any heart-rate or cadence values. A sequence of samples is not automatically a table of laps; a summary average cannot show what happened in the last five minutes.

Polar also warns that other services may recalculate or filter exported data. If Claude's calculation differs from Flow, identify the calculation and denominator rather than assume one display is wrong. A simple arithmetic check is often more useful than asking a model for an overall judgment about the session. Polar's export interpretation note.

Does downloading the account archive include everything in Flow?

Polar provides an account download at account.polar.com → Download your data → Download. It emails when the archive is ready, with two weeks to retrieve it. Its guide says the export excludes algorithm-derived data and specifically warns that activity and sleep information are not included in that export. Do not promise a complete sleep or Nightly Recharge history from the account archive. Polar's account-download boundaries.

That is distinct from exporting a session through Flow and from reading particular API endpoints. The word “archive” describes a download mechanism, not a guarantee that every value visible in the app appears in it.

What can Claude read through an iPhone?

Polar Flow sends selected data one way to Apple Health. Its list includes workout heart rate, workout details, energy, steps, weight and sleep timing/duration. Continuous heart rate is explicitly excluded. Enable sharing in Flow → More → General settings → Apple Health, then select categories. Polar's Apple Health guide.

Claude can then request access to permitted Health categories on the phone. Do not use the presence of workout heart rate to claim all-day heart-rate access, or use sleep timing to claim a Polar recovery assessment. For a missing recent record, Polar's Sync now control under the Apple Health toggle replays the last two weeks. That is a troubleshooting window, not a full-history import promise. Polar's sync troubleshooting, Claude's iPhone Health feature.

What is different on Android?

Polar Flow's Health Connect export list includes exercise timing and available laps/routes, workout heart rate and speed, sleep timing/stages, daily steps and other listed categories. Resting heart rate and VO2 max come from physical settings in that list; they should not be described as automatically measured nightly values. Connect through Flow → General settings → Health Connect → select data → Allow. Polar's Health Connect documentation.

Ask Claude a dated question and review its reading permissions. Its Android connection cannot write or modify health records. Neither phone route documented here demonstrates that Claude can send training targets back to Polar. Claude's Android read-only connection.

What would a custom Polar API or MCP service need?

Polar's AccessLink API uses OAuth and requires user consent. Its v3 exercise list exposes sessions uploaded within the last 30 days and after the user was registered with that client. A newly connected service cannot assume that endpoint supplies the runner's whole prior training history. Polar AccessLink v3 documentation.

The Dynamic API v4 documents separate reading scopes for training sessions, sleep and Nightly Recharge. Its Nightly Recharge date range has an inclusive start and exclusive end; without extra features it allows a 28-day range, while samples require one day at a time. Those are endpoint-specific rules, not universal limits for all Polar data. Polar's v4 scopes and Nightly Recharge endpoint.

Claude supports custom remote MCP connectors. A community Polar server still needs an identifiable operator, verified fitness-provider identity, OAuth implementation, applicable terms and clear tools. “Polar MCP” can refer to unrelated companies; a name match does not establish Polar Electro data access. We have not endorsed or verified a particular community service. Claude custom connector documentation.

Inspect which API generation and endpoints the service uses, whether it stores copies and how it handles missing or late-synced records. Do not assume the phone's limited permissions also govern a separate API authorization.

A worked example: two weeks are not a two-month trend

Consider a fictional runner connecting a service on September 20. The service returns two weeks of sessions, while the runner wants to compare August with September. A blank August table cannot support the conclusion that training volume increased from zero.

Use this coverage-first request:

The immediate answer should be that the supplied data cannot support the requested month-to-month comparison. You can either narrow the question to the available period or supply comparable earlier records. If you choose the latter, use the same units and record types for both periods and mark any incomplete days.

Nightly Recharge adds another source distinction. Polar describes it as combining sleep charge and autonomic nervous system charge against usual levels from the past 28 days. Copy an actual dated result if you want to discuss it; do not ask Claude to reconstruct the proprietary assessment from a few generic phone fields. Polar's explanation of Nightly Recharge.

How do you stop access or put a proposal on the watch?

For iPhone sharing, Polar directs users to Apple Health → Profile → Apps → Polar Flow → turn categories off. Remove Claude's reading permissions separately. For Android, Polar documents switching off Health Connect in Flow and managing sharing permissions. Polar iPhone controls, Polar Android controls.

For a v3 API service, require its disconnection process to de-register the user; Polar says that revokes the associated access token. Remove the Claude connector too, and address retained files or copies separately. This describes ending that service's access, not deleting your Polar account or training history. Polar AccessLink de-registration, Claude connector removal.

Polar's own documented training-target workflow creates targets in Flow and syncs them through FlowSync or the Flow app to supported devices. A Claude explanation of a proposed session does not perform those steps. Review and choose the session first, then use the supported Polar workflow and verify it on the device. Polar training-target instructions.

A Polar export gives Claude a snapshot. In a self-managed coaching workflow, you choose the time window, explain missing history and carry an agreed decision back to the plan you use. That is a reasonable approach for occasional analysis and for runners who enjoy maintaining their own system.

coach steve is our recommendation for a running-focused conversation that you can continue by SMS. It is designed around your goal, available history and the days you can run, with relevant context intended to carry forward. We have not benchmarked that continuity against Claude or verified a Polar feed here. Choose the service for its coaching focus, and check the exact integration before relying on it. See our AI running coach comparison for the broader choice.