---
title: Strava MCP connector
description: Runs, rides, swims, segments and per-second activity streams.
canonical: https://wellness.delx.ai/connectors/strava
content_signal: ai-train=no, search=yes, ai-input=yes
---

# Strava MCP Connector

A Strava MCP connector that turns recorded activities and activity streams into agent-ready training context.

## Install

```bash
npx -y strava-mcp-unofficial setup
npx -y strava-mcp-unofficial doctor
```

## Agent client config

```json
{
  "mcpServers": {
    "strava": {
      "command": "npx",
      "args": ["-y", "strava-mcp-unofficial"]
    }
  }
}
```

## Signals

- Activities
- Streams
- Routes
- Athlete Stats

## Data availability

- Activities: available. Runs, rides, swims, walks and workouts.
- Activity details, zones and splits: available. Heart rate, power, cadence, elevation and gear when present.
- Activity streams: available. Per-second samples for supported streams.
- GPS lat/lng streams: opt_in. Hidden by default; requires include_gps=true or raw mode.
- Athlete profile, zones and aggregate stats: available. Authenticated athlete context.
- Live device telemetry: not_available. Not exposed by Strava's public API.

## MCP tools

### 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

- `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

- 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.

## Best for

- Endurance weekly review
- Activity stream investigation
- Route and gear context
- Training load planning

## Known limits

- No live telemetry.
- GPS requires explicit opt-in.
- API visibility depends on Strava scopes and privacy settings.

## Links

- GitHub: https://github.com/davidmosiah/strava-mcp
- npm: https://www.npmjs.com/package/strava-mcp-unofficial
- Legacy docs: https://stravamcp.vercel.app/
- Provider docs: https://developers.strava.com/docs/reference/