Claude Strava connectorWhat Claude can do in your Strava account.
The Claude Strava connector exposes 8 tools: 8 read, 0 write. That split is deliberate: Strava itself says the connector can neither upload nor edit an activity. Below: what Claude can look at, what it can't touch, who gets access, and the limits Strava sets.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can read your Strava
Strava already holds your training. What it does not do is answer a precise question about it in your own words. With the connector, you ask Claude about your Strava performance in plain language, and it reads your account to help spot training patterns, suggest improvements, or simply cheer you on.
Look back. Activity history and fitness trends are on Strava's short list of what the connector covers today. Ask what changed over the last months and Claude reads your account to answer.
See how sports mix. If you swim, ride and run, cross-sport training is on that same list, next to readiness.
Plan the next block. Goal planning is covered too: describe the target and Claude works from what your account shows. Keep Strava's own warning in mind: an AI client processes information its own way, so its reading can differ from Strava's Performance Predictions or a Runna training plan.
What it does not do is just as clear. Strava calls the connector read-only: it cannot upload an activity or edit one. Nothing runs on its own either. No tool fires when you finish a workout; Claude only reads when you ask. If you want something to happen automatically after each ride, the Strava n8n integration and the Strava Make integration do that different job, on a trigger.
Five words before you connect
The vocabulary around this connector, in one minute.
- Connector
- The link you set up once between Claude and your Strava account, so Claude can look at your training while it answers you.
- Tool
- One named thing the connector lets Claude do. Claude chooses which ones to call by itself, in the middle of a reply.
- Authorization
- Strava's own sign-in screen, where you let Claude in. You grant it once, for yourself, and you can take it back the same way.
- Approval
- The go-ahead Claude waits for in the chat before doing something that would change an account. With Strava, no tool gets that far.
- MCP
- The shared standard behind connectors: it is what lets an assistant like Claude talk to an outside service such as Strava.
Connect Strava to Claude in three steps
- 01
Find Strava in Claude
Open Claude's settings, go to Customize then Connectors, and search for Strava. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector before members can each sign in.
- 02
Start the connection
Click Connect, then sign in with your Strava account in the window Strava opens. If the link breaks later, Disconnect and connect again. The access can also be withdrawn from the Strava account itself.
- 03
Read the authorization screen
Look at Strava's authorization screen before you accept. It belongs to Strava, not to Claude, and it sets what the access covers. Strava describes the connector itself as read-only.
The 8 tools, all on the reading side
Strava gives Claude 8 tools: 8 that read your account, 0 that change something in it.
Strava classes the whole connector as read-only, so every tool sits in one group. Strava does not describe the tools one by one, and the notes below say so rather than guess. Names stay exactly as Claude shows them.
- 8 read
What Claude reads (8)
8 toolsEight tools that look at your Strava data and leave it exactly as it is.
health
Part of the read-only set that Strava describes for the connector as a whole. Strava's help article gives no separate description of this tool, so we don't claim what it returns.
get_athlete_profile
One of the eight tools covered by Strava's read-only statement. No source spells out what it returns, so the page keeps to the one thing it knows: it only looks.
list_activities
Read-only by Strava's account of the connector. Activity history is on Strava's list of topics, but the article does not say which tool fetches it.
get_athlete_zones
Covered by the same read-only line from Strava and described nowhere else. It reads; what it reads is not documented anywhere we looked, in Strava's texts or Anthropic's.
get_activity_streams
Strava's article classes it as reading, like the rest, with no separate wording for what it brings back.
get_activity_performance
Read-only, per Strava's blanket statement, with no description of its own in any source we read.
get_club_info
Inside the read-only perimeter Strava sets for the connector. What it returns is not described in any source we read.
get_gear
Read-only like the other seven. Strava names gear among the subjects the connector handles today, though it does not say which tool answers those questions.
What Claude checks with you first
By default, Claude stops and asks before each action it takes on an account for someone. With Strava the question rarely comes up, because every tool only reads.
The general rule still stands. On Team and Enterprise workspaces, owners decide whether members may let some actions run without a prompt each time, and they can limit what a connector does across the organization, for example reading only. Nobody overrides that from a personal account. Claude also inherits the rights of the person who connected and nothing more: what your own Strava account cannot reach, Claude cannot reach either.
Which Claude plans include it
None of the 819 sheets in the official directory shows plan availability. The answer per connector is published nowhere, which is a real hole in the catalog.
Anthropic publishes a general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization before members can each connect. Strava adds its own condition on its side, a Strava subscription, covered in the limits below. For the current state on your account, the connector's sheet in the official directory is the place to look.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing happens when you save an activity or hit a new personal best.
Strava keeps a short list of what the connector covers today: activity history, fitness trends, readiness, goal planning, cross-sport training and gear. Anything outside that list is not promised. The connector is documented only by Strava: Anthropic's help center and developer documentation have no page for it. The partner badge in the directory is not a security audit, and Anthropic says on every sheet that it neither picks the tools a publisher exposes nor guarantees they behave as announced. For a connector that writes as well as reads, compare with the Claude gmail connector.
Need help connecting Strava to Claude?
A person reads every message.
