Strava MCP server

Strava × Cursor

Use the Strava MCP server
in Cursor

Your activities, stats, and training data from Strava. This guide connects Strava to Cursor (the AI code editor) through a governed gateway — one URL that also works in every other MCP client you use, with your rules and a full log attached.

Live-probed · Security-scanned · Note: Strava currently restricts third-party sign-ins — API-key path recommended

Setup: Strava in Cursor

Cursor adds MCP servers via MCP settings or install deep links. The gateway route takes about two minutes:

  1. Connect Strava to your free gate gateway from the verified directory.
  2. On your gate overview, click 'Add to Cursor' — Cursor opens and asks to install the gateway.
  3. Confirm and approve the sign-in.
  4. Strava's tools are now available to Cursor's agent, governed by your rules.

What to ask once it’s connected

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.

Why route it through a gateway

One URL, every client

The same Strava connection works in Claude, Claude Code, ChatGPT, VS Code too — no per-client re-wiring.

Rules before regret

Allow, ask, or block every tool Strava exposes — reads can flow freely while writes require your approval.

Every call logged

A plain-language activity log of everything Cursor did with Strava — searchable, exportable, auditable.

Scanned and probed

Strava passed a live handshake probe and a security scan before listing — and drift detection watches it after you connect.

Also available: Strava in Claude · Strava in Claude Code · Strava in ChatGPT · Strava in VS Code