Strava connects directly to Claude
Strava now has an official connection to Claude. Once it is connected, Claude can query your Strava account without a new export each time. The connection is read-only and available to Strava subscribers.
Strava describes this as a Claude-first launch and says other assistants may follow. On 18 August 2026, its help centre still lists no setup for ChatGPT.
How to connect Strava to Claude
1. Open Claude’s connector directory
On Claude’s web app, expand the sidebar and choose Customize, then Connectors. Select the add button and search the directory for Strava.
2. Choose Strava
Open the Strava listing and select Connect. Claude will send you to Strava to approve access.
3. Authorise your account
Sign in to the Strava account that holds the activities you want Claude to read. Review the permission request, then authorise it.
4. Test it with a narrow question
Start with something easy to check yourself, such as: “List my runs from the past seven days with distance, time and average pace.” A narrow first question makes it easier to spot a missing activity or an unexpected field.
Claude documents web connectors as available to all users, including people on the free plan. Normal Claude usage limits still apply. The paid requirement in this setup comes from Strava.
What Claude can read from Strava
Strava lists activity history, fitness trends, readiness, goal planning, cross-sport analysis and gear among the supported uses. It also says Claude can read detailed streams such as per-second pace and heart rate, GPS data and cycling power. The connection carries your Strava athlete profile too: heart-rate, pace and power zones, your FTP and whether Strava estimated it, your weight, and your bikes and shoes.
Every one of those values is something Strava computed from your activity data, not something you confirmed as current. What the connector can and can't tell Claude goes through the distinction in detail.
Claude can only read what reached Strava. If a watch or bike computer recorded the activity, Claude sees Strava’s version of it, not the original device account. A field that never reached Strava cannot appear through this connection.
That distinction matters for Garmin, Apple Watch and WHOOP users. Their routes into Strava and the fields they share are different, so check the relevant device guide before assuming a wellness metric will travel with an activity.
The connection is read-only
Claude cannot upload a new activity to Strava or edit an existing one through this connection. Strava says access is scoped to your account and can be revoked at any time.
To remove it from Strava on desktop, open Settings, choose My Apps and select Revoke Access for Claude. You can also disconnect Strava from Customize → Connectors in Claude.
What the activity does not tell you
A 10K time, pace trace and heart-rate stream describe what happened, and Strava's zones describe the ranges it derived from them. Neither tells Claude which race you are actually preparing for, what time you are chasing, or whether an injury is still limiting the week. Those facts change how the same activity should be read, and only you can state them.
Athmex holds what you enter and confirm yourself, each with the date it applied: goals and target times, upcoming races, injuries and constraints, notes, and results from races that never reached Strava. Where the two overlap, such as a threshold, a best effort or a pair of shoes, the difference is provenance. Strava reports what it derived from recorded activities; Athmex reports the figure you confirmed and when. Athmex never imports the Strava activity, and the same context is available to ChatGPT, which has no Strava route.
In the example above, Strava shows Claude the recent running. The race in 32 days and the sub-1:30 goal exist only in Athmex, and the 5K PB and threshold pace are the values the athlete confirmed rather than figures Strava derived. Claude still does the reasoning; Athmex supplies the athlete's chosen facts.
See how the two-source model works and what Athmex stores.
Questions worth asking first
Start with questions whose answers you can check in Strava.
- Were my easy runs genuinely easier over the past six weeks?
- How consistent were the pace and heart-rate traces across my recent threshold sessions?
- How has cycling or strength work changed alongside my running volume?
- Which shoes were attached to my fastest long runs this season?
When Athmex is also connected, make the comparison explicit: “Compare my last six weeks of Strava running with my current half-marathon goal and threshold pace in Athmex,” or “Review my volume around the active calf injury note in Athmex.”
What if you use ChatGPT?
There is an indirect route. Strava can write into Apple Health, and ChatGPT's Health feature reads Apple Health, so your Strava activities can reach ChatGPT that way. It needs an iPhone and a United States account, and it carries what Strava writes into Apple Health rather than the fuller picture the Claude connector answers from, so treat it as a different thing rather than the same connection reaching a second assistant.
Strava does not currently publish an equivalent ChatGPT setup. Avoid unofficial workarounds that ask for credentials or depend on brittle authentication. You can upload an export manually, but that is a static snapshot rather than the live connection described above.
If you need an official activity connection that works with both assistants, COROS documents setup for Claude and ChatGPT. Its data coverage and subscription requirements differ from Strava’s, so compare the two before choosing a route. Athmex also works with both assistants, but carries athlete context rather than activities.
For the full picture across every device and assistant, see which training-data routes currently work for ChatGPT and Claude.