Vague questions get vague answers, and sometimes invented ones. Every prompt here names the activities, the dates and the output, and caps how many activities it touches. Strava limits requests per minute and per day, and pulling streams is one tool call per activity. Swap anything in square brackets for your own details.
Every Strava subscription includes it, among them the standard plan, Strava + Runna, Family, Student, and the military, educator and medical discount plans, according to Strava’s support article. The connector returns metric units, so ask for miles if you want them.
Make something from your routes
The connector hands over GPS points, so Claude can draw with them. In Claude.ai or Cowork, ask for an artifact or an SVG file; in Claude Code, ask for an SVG or HTML file.
1. A poster of one route
Find my longest run from the last 12 months. Pull its GPS and altitude streams and draw the route as a minimal poster in an artifact: off-white background, one continuous dark line, no map underneath, a thin elevation profile along the bottom, and the name, date, distance and elevation gain in small type. Cut the first and last 400 meters off the line so the start and finish are not exact.
What you get: A printable poster drawn from your own GPS points, with no map tiles involved.
What it reads: Your activity list to find the run, then the GPS and altitude streams for that one activity.
Watch for: Trimming the ends helps, but a route that starts at your door still points at your street. Look before you share, and check who can see anything you share out of Claude.
2. A year of route shapes
List every run and ride I did in 2026 with the route line included. Draw each one as a small silhouette in a grid, in date order, runs in one color and rides in another, each shape scaled to fit its cell. Point out the three strangest shapes and tell me which activities they are.
What you get: A contact sheet of your year, which looks better than it has any right to.
What it reads: Only the activity list, asked to include a simplified route line per activity. No per-activity stream calls, so it goes easy on the rate limit.
Watch for: The lines are simplified, so tight loops smooth out. Same location caveat as the poster.
3. A course card for a race you want to run again
For my race [activity name or date], pull the distance, altitude, grade and speed streams. Make a one-page course card in an artifact: the elevation profile with every climb steeper than 3% marked, my pace overlaid, and a note on each climb saying how much time I lost or gained against my average pace for the race.
What you get: A pacing map to study before next year’s attempt.
What it reads: Distance, altitude, grade and speed streams for one activity (Claude converts speed to pace), plus its laps from the activity details.
Races and tapers
4. What came before your best and worst races
Find my races from the last three years by race tag, name, description or pace, and list them so I can confirm before you go on. For each one, summarize the 10 weeks before it: weekly distance, longest session, number of hard sessions, and what the last 14 days looked like. Then compare my best three results with my worst three and tell me what differed. If the differences are small or there are too few races to say, tell me that.
What you get: A table per race and a short read on the pattern, if there is one.
What it reads: Your activity list (names, descriptions, distances, relative effort) and activity details for the races.
Watch for: Six races is a tiny sample, and weather, course and illness aren’t in the data. Let it conclude that nothing stands out.
5. A taper built from your own history
Find my races longer than 10 km from the last three years and list them so I can confirm. For each, show how much I cut weekly distance and hard sessions in the three weeks before, and how the race went compared with my training at the time. Then suggest a taper for my race on [date] based on what worked for me rather than a generic template, and flag where my history is too thin to support it.
What you get: A taper suggestion with the evidence for it laid out underneath.
What it reads: Your activity list and activity details for each race.
Watch for: It’s a suggestion from a handful of past races, not a coach. Check it against how you feel.
Heart rate, heat and zones
6. Heart-rate drift across a season
Find up to 20 of my steady runs between 50 and 90 minutes this year. For each, compare heart rate against pace in the first half and the second half (aerobic decoupling) using the heart rate, speed and time streams. Leave out runs with obvious heart-rate spikes. Chart the drift over the season and name the runs that break the trend, with dates.
What you get: A durability chart for the year, and a short list of odd days worth remembering.
What it reads: Your activity list, then heart rate, time and speed streams (Claude converts speed to pace) for each run it picks.
Watch for: Heat, hills and wrist-sensor glitches all cause drift too. The spike filter helps a little.
7. What heat costs you
For up to 25 of my runs from the last 12 months that have a temperature stream, compare average temperature with heart rate at similar speeds. Tell me roughly how many beats per minute each 5 °C costs me, and how confident that estimate is given the number of runs.
What you get: A rough number for your own heat penalty, with a confidence note attached.
What it reads: Temperature and heart rate streams, and the speed stream (Claude converts it to pace).
Watch for: Only devices that record temperature produce this stream, and the device’s sensor can read differently from the air temperature.
8. Easy runs that aren’t easy
Look at my runs in the last 8 weeks that weren’t workouts or races. Get my heart-rate zones as of the start of that period. Work out the time in each zone for each run from the heart rate stream. Show what share of my easy running actually sat in zone 3 or higher, and which weeks were worst.
What you get: A plain check on intensity creep, week by week.
What it reads: Your heart-rate zones as of a past date, your activity list, and heart rate streams for each easy run.
Watch for: Eight weeks of runs can be a lot of stream calls. If it stalls, cut it to four weeks.
9. Warning signs in your load
Look at my last 16 weeks. Flag any week where total relative effort jumped more than 30% over the average of the four weeks before it, and any stretch of two weeks or more where my heart rate at my usual easy pace went up. List the dates and the numbers and nothing else.
What you get: A short list of dates to look at, with no story attached.
What it reads: Your activity list (relative effort per activity) and heart rate and speed streams (Claude converts speed to pace) for a sample of easy runs.
Watch for: This is pattern-spotting, not a diagnosis, and none of it is medical advice. Pain, illness or tiredness that won’t go away is a conversation for a doctor or physio.
Gear
10. Which shoes or bike are actually faster
Get my gear. For each pair of shoes with more than 100 km on them, compare pace at similar heart rate on runs of similar distance and climbing. Do the same for my bikes, using speed at similar power, but only on rides with power from a power meter. Tell me whether any difference survives once route and effort are matched. Then list my active shoes by total distance.
What you get: A matched comparison per shoe and bike, and a mileage list for replacing shoes.
What it reads: Your gear list (names, brand and model, total distance, retired or not), your activity list, and activity details.
Watch for: Comparing every run means fetching details for each one, so ask for the last 50 runs per pair if it stalls. And it’s correlation: you probably wear the fast shoes on fast days, which is exactly what a matched comparison struggles to undo.
Plans, reports and clubs
11. Your Strava training plan as a calendar file
Read my training plan. Show me every session as a list first. Then turn it into an .ics calendar file with one event per workout at 7:00 local time and the session details in the event description.
What you get: A file you import into your own calendar.
What it reads: The training plan tool, which, as of September 2026, describes itself as returning personalized running training plans. If your account has no plan, there’s nothing for it to read.
Watch for: The connector is read-only, so Claude can’t change the plan in Strava. The file puts it in your calendar instead.
12. A first draft of a race report
Write a first draft race report for my activity [name or date]. Use the laps, best efforts, segment efforts, and the heart rate and speed streams to find where I faded or surged, and quote my own activity description for how it felt. Keep it under 400 words, write it in the first person, and mark where every number came from.
What you get: A draft you edit into your own words.
What it reads: Your activity list for the description, activity details (laps, best efforts, segment efforts), and heart rate and speed streams (Claude converts speed to pace) for the one activity.
Watch for: Check every number against the activity page before you post it anywhere.
13. The story versus the data
Read my activity titles and descriptions from the last 12 weeks next to the numbers. Where does what I wrote disagree with what I did? You’re allowed to conclude that they agree.
What you get: A reading of your own captions against your training.
What it reads: Only the activity list, which carries titles, descriptions and the summary numbers.
Watch for: Needs real titles and descriptions. The last line matters: without it, the model tends to find a gap whether or not one exists.
14. Club events that fit your week
List the upcoming events in my clubs for the next two weeks. Given what I did in the last 7 days, and my training plan if I have one, pick the two that fit best and say why. Name the ones I should skip.
What you get: A shortlist of group runs or rides that don’t wreck the week.
What it reads: Your clubs and their upcoming events, your recent activity list, and the training plan tool if you have a plan.
Strength
15. Strength progress, and the run the day after
Pull the exercise sets from my strength workouts in the last 12 weeks. Chart weight times reps per exercise over time. Then check whether my runs the day after a leg session are slower at the same heart rate than my other runs.
What you get: A progress chart per exercise and an answer on the day-after cost.
What it reads: The strength workout tool, which returns sets with exercise, muscle groups, weight, reps and duration (Strava’s September 16, 2026 update on r/Strava says subscribers can ask Claude about exercises, sets, weight and reps). Plus your activity list and heart rate and speed streams (Claude converts speed to pace).
Watch for: Only sets logged in Strava show up. Sets without a recorded weight or reps (bodyweight, timed) drop out of the chart.
How people are using it
Runners, cyclists and triathletes have been writing up what they asked since the June launch. These are their results, as they reported them.
- Martin Biela, writing on the Substack Uphill Notes, had Claude read Biela’s OCC race from Strava, pull out the shape of its elevation profile, and find a 31.9 km loop in the Taunus hills near Wiesbaden with the same shape. The connector can’t write, so Biela uploaded the route to Strava by hand. (The course card prompt starts from the same streams.)
- The same post has Claude build a “running fingerprint” from a sample of runs (easy, tempo, two trail runs and a race): 28% slower uphill (6.8 km/h against 9.5 km/h on the flat), negative splits on trails but tempo runs started too fast, and a cadence that settles at 154 steps per minute, the same tempo an earlier song matcher had used to pull tracks from Biela’s own playlist. The shoe history came out as 13 pairs and 4,430 km, with one Nike Pegasus 40 at 1,547 km of it (the gear prompt ends on the same list).
- Matsubokkuri (まつぼっくり), on the blog ITエンジニアのトライアスロン日記, used Claude Code with the Strava connector to go back over a 2025 duathlon (20 km bike, 8 km mountain leg, 30 km bike, 20 km run). It put about 21 minutes within reach for next season: roughly 7 by avoiding punctures, 10 on the final run through cramp prevention and run endurance, and 5 on the descents. It first read the low heart rate on that run as energy held in reserve, and only got it right after reading the race report, which had the walking and the cramps in it. That’s why the race report prompt asks for your own description.
- Scott Dunlap’s post on trailrunner.substack.com uses the second-by-second heart rate from a swim threshold (CSS) test of 10 x 100 m to confirm the breakpoint between reps 5 and 6, where heart rate went from 125 to 143 bpm. The same post counts dog walks: 170.6 km over 81 outings, 4.8% of the distance for the year so far.
- u/raygunner88 on r/Strava posted a prompt that reads 12 weeks of titles and descriptions against the numbers and asks where the story and the data disagree. In the replies, u/Fun_Effective_836 pointed out it will always find a story because you asked for one, and suggested letting it conclude the two agree. The story versus data prompt carries that line.
- Elio Struyf, on eliostruyf.com, built a Claude skill that reads FTP, power zones, profile, the last 14 days of rides and recent power data through the Strava connector, classifies the rider type, and writes a week of Zwift workouts as .zwo files plus strength and core sessions. The skill is open source on GitHub.
- CyclingClaude, a German cycling blog, asked about form ahead of Vätternrundan. Claude pulled a 209 W FTP, the zones and the power curve from 5 seconds to an hour, worked out watts per kilo, and noticed the 2024 Vätternrundan was more efficient than 2025’s (2.13 against 2.05 W/kg), which it put down to higher body weight. The post says that used to take hours in Excel.
- Daniel Yubi, on yubi.blog, set up a Claude Project as a marathon coach, aimed at London in April 2027 with a December half marathon as a checkpoint. Each week starts with a review of the last 7 to 14 days, and Yubi writes sleep, food and how a run felt into the Strava notes so Claude can read them, with Claude’s Apple Health integration connected too. In the eleven months before, 40% of Yubi’s weeks had no running; the post now reports “an easy pace, which I did not previously have.”
What people say about it
The praise is mostly about analysis: CyclingClaude calls it one of the most useful AI integrations the blog has tried, and Dunlap writes that it “justifies the requirement of Strava Premium instantly.” Not everyone is sold on it as a coach: Biela calls it “a data layer, not a coach.” The complaints start with access. It’s for subscribers only (“a paywall to access my own singular data,” wrote u/Landcruiser82), it works with Claude and nothing else, which Canadian Cycling Magazine called walled openness, and it’s read-only, so Biela uploaded that loop by hand. On the data side, u/Mission-Candy1178 says vague prompts get made-up answers, u/BroadbandEng was told they’d climbed a hill several times because its segments overlap, u/RaptorsRule247 still pastes Garmin screenshots for running dynamics like ground contact time, and u/McZubs finds the swim data thinner than bike and run, and loads swim exports as CSV instead.
Getting better answers
- Be specific. Name the activity, the date range and what you want back (a table, a chart, a file).
- Cap the count. “Up to 20 runs” is a real instruction. Strava doesn’t publish its per-minute and per-day limits, and a prompt that pulls streams for 80 activities can hit them halfway through.
- Ask it to show its working. A table of the activities it used, with dates, makes a wrong answer easy to spot. Ask it to say when the sample is too small.
- Check the totals. Answers can be wrong and still sound sure of themselves. Weekly distance and time are easy to compare with Strava’s own training log.
- Know what isn’t there. As of September 2026, none of the connector’s tools return sleep, HRV or running dynamics such as ground contact time. Prompts that need them get guesses.
Every prompt and the data it reads
| Prompt | Data it reads | Approx. tool calls |
|---|---|---|
| Route poster | Activity list; GPS and altitude streams | 2 (list, then streams) |
| Year of route shapes | Activity list with route lines | 1 per 100 activities |
| Race course card | Distance, altitude, grade and speed streams; laps | 3 (list, streams, details) |
| Best vs worst races | Activity list, activity details | A few list calls, plus one per race |
| Taper from your history | Activity list, activity details | A few list calls, plus one per race |
| Heart-rate drift | Heart rate, speed and time streams | A few list calls, plus up to 20 |
| Heat cost | Temperature, heart rate and speed streams | A few list calls, plus up to 25 |
| Easy runs check | Heart-rate zones, heart rate streams | 1 for zones, 1 list call, plus one per easy run |
| Load warning signs | Relative effort, heart rate and speed streams | A few list calls, plus one per sampled run |
| Shoes and bikes | Gear list, activity list, activity details | 1 for gear, list calls, plus one per run compared; cap it |
| Plan to calendar file | Training plan | 1 |
| Race report draft | Description, laps, best and segment efforts, streams | 3 (list, details, streams) |
| Story vs data | Titles, descriptions, summary numbers | 1 per 100 activities |
| Club events | Clubs and events, activity list, training plan | 1 for clubs, 1 list call, 1 for the plan |
| Strength progress | Strength sets, heart rate and speed streams | 1 for all workouts, plus one per run |
Estimates from the connector’s tools as of September 2026, not a Strava figure. Streams and activity details are fetched one activity at a time, so those are the calls that add up against the rate limit. The activity list returns up to 100 activities per page, which makes the list-only prompts cheap.
Sources
- What is the Strava MCP Connector?, Strava Support (subscribers and plans, Claude surfaces, read-only, rate limits)
- Strava API and MCP FAQ, Strava Support
- Strava connector in Anthropic’s connector directory (activity list, streams, performance, zones, gear, clubs)
- Strava launches MCP connector, Strava Press, June 1, 2026
- What’s New on Strava, u/will-from-strava on r/Strava, September 16, 2026 (asking Claude about strength workout details)
- Tool descriptions exposed by the connector in September 2026 (stream types, units, page size, training plan and strength tools)
- I Connected Strava to Claude AI and Handed Over Eight Years of Running. Then We Played., Martin Biela, Uphill Notes, July 12, 2026
- Strava MCPを使って自分のレースとトレーニングを分析させてみてトレーニング計画を作ってみた (Japanese), Matsubokkuri, ITエンジニアのトライアスロン日記, June 14, 2026
- How To Use the Strava MCP, The New AI Connector to Your Strava Data Layer, Scott Dunlap, June 26, 2026
- How I built an adaptive AI cycling coach using Claude, the Strava Connector, and a skill to create workouts, Elio Struyf, June 11, 2026
- Der ultimative KI-Trainingsberater 2026: Strava MCP mit Claude.ai (German), CyclingClaude, June 6, 2026
- Strava MCP + Claude: Build an AI Running Coach, Daniel Yubi, August 11, 2026
- Strava goes full AI (if you want) with Claude integration, Terry McKall, Canadian Cycling Magazine, June 9, 2026
- r/Strava and r/triathlon threads, June to August 2026: u/raygunner88, u/Fun_Effective_836, u/Landcruiser82, u/Mission-Candy1178, u/BroadbandEng, u/RaptorsRule247, u/McZubs
Related reading
Setup, availability and revoking access are on the Strava MCP page, and the June launch is covered in Strava’s MCP connector. If you’d rather have a dashboard than a chat, the apps under analytics and AI read the same activities, and the route posters above have print-shop cousins under art.