---
title: Strava MCP Connector for AI Agents
description: Use the Strava MCP connector with an AI agent for activities, streams, routes and athlete context through a local-first, privacy-aware server.
canonical: https://wellness.delx.ai/guides/strava-mcp-for-ai-agents
content_signal: ai-train=no, search=yes, ai-input=yes
---

# Strava MCP Connector for AI Agents

The Strava MCP connector is a local-first bridge between Strava API v3 and an MCP-compatible AI agent. It provides read-only activities, summaries, routes and recorded sensor streams while keeping OAuth tokens outside model responses.

## Short answer

Create a personal Strava API app, run <code>npx -y strava-mcp-unofficial setup</code>, authorize <code>read activity:read_all profile:read_all</code>, and verify with <code>npx -y strava-mcp-unofficial doctor</code>. OAuth tokens stay local. Start from daily or weekly summaries; GPS lat/lng requires explicit opt-in and route geometry stays redacted from safe response modes.

## How do I connect Strava MCP to Claude?

Create a personal Strava API app, run the local setup and <code>npx -y strava-mcp-unofficial doctor</code>, add the documented <code>mcpServers</code> block to Claude Desktop and start with <code>strava_connection_status</code>, <code>strava_data_inventory</code> and <code>strava_privacy_audit</code>. Keep GPS disabled unless the user explicitly opts in.

## Setup method

1. Create a Strava API application and register <code>http://127.0.0.1:3000/callback</code>.
2. Run <code>npx -y strava-mcp-unofficial setup</code> and keep the client secret private.
3. Complete browser OAuth with <code>read activity:read_all profile:read_all</code>.
4. Run <code>npx -y strava-mcp-unofficial doctor</code>, then call <code>strava_connection_status</code>, <code>strava_data_inventory</code> and <code>strava_privacy_audit</code>.
5. Start with <code>strava_daily_summary</code> or <code>strava_weekly_summary</code>. Fetch a detailed stream only for a specific activity.

## MCP client configuration

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

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

Activity streams depend on the recorded sensors, activity type, visibility and granted OAuth scopes. Missing heart rate, power, cadence or GPS must not be inferred.

## Safe first-call sequence

1. <code>strava_connection_status</code>
2. <code>strava_data_inventory</code>
3. <code>strava_privacy_audit</code>
4. <code>strava_daily_summary</code>
5. <code>strava_activity_series</code>

## Privacy and rate limits

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

Strava documents default overall limits of 200 requests every 15 minutes and 2,000 per day for newly created apps, with separate read limits and account tiers. Read the live rate-limit headers, batch work, cache responses and avoid polling loops.

## Official sources

- OAuth: https://developers.strava.com/docs/authentication/
- Rate limits: https://developers.strava.com/docs/rate-limits/
- API v3 reference: https://developers.strava.com/docs/reference/
- Webhook events: https://developers.strava.com/docs/webhooks/

## Canonical Delx sources

- Connector specification: https://wellness.delx.ai/connectors/strava
- Connector comparison: https://wellness.delx.ai/guides/choose-wellness-mcp-connector
- Security model: https://wellness.delx.ai/security
- npm: https://www.npmjs.com/package/strava-mcp-unofficial
- GitHub: https://github.com/davidmosiah/strava-mcp

Delx Wellness and strava-mcp-unofficial are not affiliated with Strava. This is technical wellness integration context, not medical advice.