You can connect Strava to Claude in a few minutes using the Model Context Protocol (MCP), and once it’s connected, Claude can read your activities, stats, and training history directly instead of you exporting a CSV or screenshotting a graph. This guide covers what the Strava MCP server does, both ways to connect it, and why activity data deserves a slower look than most tools in this series — it isn’t a work file, it’s a record of where you personally were and when.

What the Strava MCP server actually does

Strava publishes a remote MCP server at mcp.strava.com that exposes your activities, stats, and training data as tools Claude can call directly. See the Strava server page in gate’s directory for the current tool list and connectivity status. In practice that means prompts like:

  • “How far did I run this month?”
  • “Summarize my last ride.”
  • “Am I on track for my yearly distance goal?”
  • “Compare this week’s training to last week’s.”

That’s a genuinely useful assistant for anyone who trains regularly — the alternative is opening the app, scrolling through a feed, and doing the comparison yourself. The catch is what the underlying data contains: an activity isn’t just a distance and a pace, it’s usually a GPS track, which means start and end points, and for most people the start and end point of a run is their front door.

Option 1: Connect Strava to Claude directly

Claude supports remote MCP servers natively. The short version of the setup:

  • Open Claude’s connector or MCP settings.
  • Add a remote server pointing at Strava’s MCP endpoint.
  • Sign in with your Strava account when prompted — this is standard OAuth, so Claude never sees your Strava password, and you can revoke access from Strava’s own account settings at any time.

Strava’s MCP server currently sits behind allow-listed OAuth in gate’s directory, the same restriction that Slack, Figma, and several other servers in this series hit — the vendor approves which clients can complete the OAuth flow before the consent screen even shows up, rather than accepting any client that asks. If the connection stalls or the consent screen never appears, that’s the likely reason, not a broken setup on your end. See the “unauthorized client” error for what that looks like in practice and how to tell the difference from an actual problem.

Option 2: Connect it once, through a gateway

If you’re already juggling more than one MCP server, or more than one AI client, wiring each pair directly gets old fast. The alternative is connecting Strava (and everything else) to one gateway URL, then pointing every AI client at that single URL instead of reconfiguring each one — see what an MCP gateway is for the full case.

With gate specifically, connecting Strava looks like this: add gate’s gateway URL to Claude once, then pick Strava from the MCP servers directory and sign in with OAuth the same way you would directly. From then on, Strava’s tools are available in every client connected to your gate URL — Claude, ChatGPT, or Cursor — without a second setup step, and every call it makes shows up in one readable log instead of scattered across each client’s own history.

Why activity data is a different kind of personal

Most tools in this series raise a work-context question — what can it read or change in a shared file, a CRM, a support inbox. Strava is personal in a way none of those are: the data is about you specifically, not a shared account, and some of it is genuinely sensitive even though it feels harmless.

  • GPS routes can reveal where you live and work. A default privacy zone in Strava’s own app hides the start and end of a route on the public feed for exactly this reason — the pattern of “runs that start and end at the same address every day” is a location, not just a workout. Once an AI client can pull raw activity data through a tool call, check whether it’s reading the same privacy-zoned view you see, or the underlying data before that redaction applies.
  • It’s a record of your schedule and habits. Training times, rest days, and travel (a sudden batch of runs in a different city) are all inferable from activity history. That’s a mundane fact about most people’s week, but it’s still the kind of pattern you wouldn’t hand to a stranger, and a tool call result can end up quoted back in a conversation, a summary, or a log you didn’t expect to share.
  • Check what the connection can write, not just read. Some fitness integrations can also update or delete activities. Before you approve a broad grant, look at whether Claude’s connection is limited to reading your data or can also modify it — the same read-vs-write question we raise for every tool in this series, just with your own body’s data instead of a company’s.

You can run a quick, no-signup check on any server’s tool list — including ones that require OAuth, once connected — with gate’s free MCP security scanner, which looks for prompt injection and hidden instructions in tool descriptions before you rely on a server day to day.

Troubleshooting the connection

A few things that commonly go wrong when connecting any remote MCP server, Strava included:

  • OAuth rejects your client outright. As noted above, Strava’s MCP server currently allow-lists which clients can complete the flow. If Claude’s own client isn’t on that list yet, the fix is waiting on Strava to widen access, not retrying the same setup.
  • Recent activities don’t show up yet. Activity data can lag a few minutes behind what you see in the app, especially right after a GPS watch finishes syncing — ask again in a bit before assuming the connection is broken.
  • Tools disappear or change shape after a Strava update. Remote servers can change their tool list without warning. If you’re connected through a gateway, that’s exactly what drift detection is meant to catch.

The bottom line

Connecting Strava to Claude with MCP takes a few minutes once the OAuth allow-list clears: point Claude directly at Strava’s server and sign in, or connect it once through a gateway if you want the same access available in every AI client you use. Either way, treat it as personal data, not just another integration — a GPS track is a location history with a workout attached, and that’s worth a minute’s thought before you say yes.