All connectors
Strava

strava-mcp-unofficial

Strava MCP server for AI agents

The Strava MCP server uses the official Strava API v3 so agents can work with activities, streams, routes and athlete stats through user-authorized OAuth.

ActivitiesStreamsRoutesAthlete StatsShared profile
Runners and cyclists training outdoors with route and endurance context
OAuth 2.0

Best for endurance agents and coaches that need a Strava MCP connector for route-aware activity details without exposing GPS by default.

MCP server answers

The Strava MCP server for AI agents is a local-first connector provided by strava-mcp-unofficial. It uses the official Strava API v3 and user-authorized OAuth to expose runs, rides, swims, activities, routes and recorded streams to Claude, Cursor and other MCP-compatible clients. OAuth tokens stay local, GPS lat/lng remains opt-in and route geometry is redacted from safe response modes; Strava does not provide live device telemetry and Delx does not host a copy of the data.

Compare this connector with the other wellness pathsSet up Strava OAuth, activity streams and location-safe agent calls
What is the Strava MCP server?

The Strava MCP server for AI agents is a local-first connector provided by strava-mcp-unofficial. It uses the official Strava API v3 and user-authorized OAuth to expose runs, rides, swims, activities, routes and recorded streams to Claude, Cursor and other MCP-compatible clients. OAuth tokens stay local, GPS lat/lng remains opt-in and route geometry is redacted from safe response modes; Strava does not provide live device telemetry and Delx does not host a copy of the data.

How do I install Strava MCP?

Run npx -y strava-mcp-unofficial setup, then npx -y strava-mcp-unofficial doctor. The Quick Start section below contains the client configuration and provider-specific setup.

What can an agent read from Strava?

The available records start with Activities, Activity details, zones and splits, Activity streams, Athlete profile, zones and aggregate stats. Check Data Availability for scope, device and export limitations before using any result.

Quick Start

terminal
npx -y strava-mcp-unofficial setup
npx -y strava-mcp-unofficial doctor
mcp-client.json
{
  "mcpServers": {
    "strava": {
      "command": "npx",
      "args": ["-y", "strava-mcp-unofficial"]
    }
  }
}
  1. 01

    Create a Strava API app.

  2. 02

    Use redirect URI http://127.0.0.1:3000/callback.

  3. 03

    Run auth and verify granted scopes with doctor.

Recommended scopes

read activity:read_all profile:read_all

Data Availability

Available

Activities

Runs, rides, swims, walks and workouts.

Available

Activity details, zones and splits

Heart rate, power, cadence, elevation and gear when present.

Available

Activity streams

Per-second samples for supported streams.

Opt-in

GPS lat/lng streams

Hidden by default; requires include_gps=true or raw mode.

Available

Athlete profile, zones and aggregate stats

Authenticated athlete context.

Not exposed

Live device telemetry

Not exposed by Strava's public API.

Agent Tools

Profile and onboarding

  • strava_profile_get
  • strava_profile_update
  • strava_onboarding

Start here

  • strava_connection_status
  • strava_daily_summary
  • strava_weekly_summary

Auth and diagnostics

  • strava_capabilities
  • strava_agent_manifest
  • strava_privacy_audit
  • strava_cache_status
  • strava_get_auth_url
  • strava_exchange_code
  • strava_revoke_access

Athlete and training

  • strava_get_athlete
  • strava_get_zones
  • strava_get_athlete_stats

Activities and streams

  • strava_list_activities
  • strava_get_activity
  • strava_get_activity_zones
  • strava_get_activity_streams

Routes and context

  • strava_list_routes
  • strava_get_route
  • strava_list_clubs
  • strava_get_gear

Prompts and Resources

Prompts

  • strava_daily_training_director
  • strava_weekly_endurance_review
  • strava_activity_stream_investigator

Resources

  • strava://capabilities
  • strava://agent-manifest
  • strava://athlete
  • strava://latest/activity
  • strava://summary/daily
  • strava://summary/weekly

Privacy Model

GPS streams are hidden unless explicitly requested.
OAuth tokens stay local.
Route geometry is redacted in summary and structured modes.
Agents can start from daily or weekly summary tools before fetching details.
Profile and goals persist locally to ~/.delx-wellness/profile.json (mode 0600); shared with all 14 Delx Wellness connectors and never uploaded.