Strava MCP

Name: Strava MCP
Author: ljcl

by ljclversion 3.0.0i★ –iRuns on your computer

Registry nameio.github.ljcl/strava-mcp

Install

Overview

Description from the maker (original English)

Remote MCP server for your Strava activities, segments, and routes

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: Streamable HTTP
Category: Other
You need to fill in: STRAVA_CLIENT_ID, STRAVA_CLIENT_SECRET, PUBLIC_URL, STRAVA_ACCESS_TOKEN, STRAVA_REFRESH_TOKEN, MCP_AUTH_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: STRAVA_CLIENT_ID, STRAVA_CLIENT_SECRET, PUBLIC_URL, STRAVA_ACCESS_TOKEN, STRAVA_REFRESH_TOKEN, MCP_AUTH_TOKEN, PORT, TOKEN_DATA_DIR, ROUTE_EXPORT_PATH

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

DockerDocker installed

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "strava": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "STRAVA_CLIENT_ID",
        "-e",
        "STRAVA_CLIENT_SECRET",
        "-e",
        "PUBLIC_URL",
        "-e",
        "STRAVA_ACCESS_TOKEN",
        "-e",
        "STRAVA_REFRESH_TOKEN",
        "-e",
        "MCP_AUTH_TOKEN",
        "-e",
        "PORT",
        "-e",
        "TOKEN_DATA_DIR",
        "-e",
        "ROUTE_EXPORT_PATH",
        "ghcr.io/ljcl/strava-mcp:3.0.0"
      ],
      "env": {
        "STRAVA_CLIENT_ID": "your-value",
        "STRAVA_CLIENT_SECRET": "your-value",
        "PUBLIC_URL": "your-value",
        "STRAVA_ACCESS_TOKEN": "your-value",
        "STRAVA_REFRESH_TOKEN": "your-value",
        "MCP_AUTH_TOKEN": "your-value",
        "PORT": "your-value",
        "TOKEN_DATA_DIR": "your-value",
        "ROUTE_EXPORT_PATH": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add strava --env STRAVA_CLIENT_ID=your-value --env STRAVA_CLIENT_SECRET=your-value --env PUBLIC_URL=your-value --env STRAVA_ACCESS_TOKEN=your-value --env STRAVA_REFRESH_TOKEN=your-value --env MCP_AUTH_TOKEN=your-value --env PORT=your-value --env TOKEN_DATA_DIR=your-value --env ROUTE_EXPORT_PATH=your-value -- docker run -i --rm -e STRAVA_CLIENT_ID -e STRAVA_CLIENT_SECRET -e PUBLIC_URL -e STRAVA_ACCESS_TOKEN -e STRAVA_REFRESH_TOKEN -e MCP_AUTH_TOKEN -e PORT -e TOKEN_DATA_DIR -e ROUTE_EXPORT_PATH ghcr.io/ljcl/strava-mcp:3.0.0

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "strava": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "STRAVA_CLIENT_ID",
        "-e",
        "STRAVA_CLIENT_SECRET",
        "-e",
        "PUBLIC_URL",
        "-e",
        "STRAVA_ACCESS_TOKEN",
        "-e",
        "STRAVA_REFRESH_TOKEN",
        "-e",
        "MCP_AUTH_TOKEN",
        "-e",
        "PORT",
        "-e",
        "TOKEN_DATA_DIR",
        "-e",
        "ROUTE_EXPORT_PATH",
        "ghcr.io/ljcl/strava-mcp:3.0.0"
      ],
      "env": {
        "STRAVA_CLIENT_ID": "your-value",
        "STRAVA_CLIENT_SECRET": "your-value",
        "PUBLIC_URL": "your-value",
        "STRAVA_ACCESS_TOKEN": "your-value",
        "STRAVA_REFRESH_TOKEN": "your-value",
        "MCP_AUTH_TOKEN": "your-value",
        "PORT": "your-value",
        "TOKEN_DATA_DIR": "your-value",
        "ROUTE_EXPORT_PATH": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "strava": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "STRAVA_CLIENT_ID",
        "-e",
        "STRAVA_CLIENT_SECRET",
        "-e",
        "PUBLIC_URL",
        "-e",
        "STRAVA_ACCESS_TOKEN",
        "-e",
        "STRAVA_REFRESH_TOKEN",
        "-e",
        "MCP_AUTH_TOKEN",
        "-e",
        "PORT",
        "-e",
        "TOKEN_DATA_DIR",
        "-e",
        "ROUTE_EXPORT_PATH",
        "ghcr.io/ljcl/strava-mcp:3.0.0"
      ],
      "env": {
        "STRAVA_CLIENT_ID": "your-value",
        "STRAVA_CLIENT_SECRET": "your-value",
        "PUBLIC_URL": "your-value",
        "STRAVA_ACCESS_TOKEN": "your-value",
        "STRAVA_REFRESH_TOKEN": "your-value",
        "MCP_AUTH_TOKEN": "your-value",
        "PORT": "your-value",
        "TOKEN_DATA_DIR": "your-value",
        "ROUTE_EXPORT_PATH": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

STRAVA_CLIENT_ID required env
Strava API client ID
STRAVA_CLIENT_SECRET secret required env
Strava API client secret
PUBLIC_URL required env
Public HTTPS URL used for the Strava OAuth callback
STRAVA_ACCESS_TOKEN secret env
Optional initial access token from setup-auth
STRAVA_REFRESH_TOKEN secret env
Optional initial refresh token from setup-auth
MCP_AUTH_TOKEN secret env
Shared secret gating /mcp and the OAuth web routes (recommended when internet-facing)
PORT env
Server port (default 3000)
TOKEN_DATA_DIR env
Override token storage directory (default ./data)
ROUTE_EXPORT_PATH env
Absolute directory for exported route files

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account ljcl, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 18352 servers in this category
Published to the registry more recently than 28% of the other 18352 servers in this category
Basic checks equal to or better than 100% of the other 18352 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Strava MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: STRAVA_CLIENT_ID, STRAVA_CLIENT_SECRET, PUBLIC_URL, STRAVA_ACCESS_TOKEN, STRAVA_REFRESH_TOKEN, MCP_AUTH_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (3.0.0) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Hunter Killer

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Hunter Killer

by Irishman-Management-LLC

Liquidation walls, snapshot age, evidence labels and a public record. Managed OAuth.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Strava MCP

A Model Context Protocol (MCP) server that supplements the official Strava MCP connector. It adds write access, segments, routes, photos, derived analysis, and interactive visualizations that the official connector does not provide.

Features

Write and update activities (title, description, sport type, gear, flags)
Create manual activities for sessions with no device recording (strength, yoga, treadmill)
Explore, view, star, and manage segments
Fetch per-activity photos, zone breakdowns, and running summaries
List and view details of saved routes
Export routes (GPX/TCX) and activity tracks (GPX built from streams)
Derived analysis Strava does not expose: interval detection, climb/descent breakdown, aerobic decoupling, training load, fitness/fatigue/form (CTL/ATL/TSB), and a solved taper to a target race-day form
AI-friendly JSON responses via MCP
Nine interactive visualizations rendered in MCP-compatible hosts — activity chart, cadence trends, route map, activity segments, training load, compare activities, activity zones, segment progress, and fitness trend
Guided prompts for weekly reviews, annotating a run, and segment hunting (docs/tools.md)
Automatic token refresh
Streamable HTTP transport for remote deployment

Browse the UI components in the live Storybook.

The full tool catalog, prompts, permission behaviour, and example requests live in docs/tools.md.

Quick Start (Docker)

1. Create a Strava API Application

Go to strava.com/settings/api
Create a new application:

Enter your application details (name, website, description)
Set "Authorization Callback Domain" to your public URL hostname (e.g., strava-mcp.example.com)
Note your Client ID and Client Secret

2. Configure Environment

cp .env.example .env

Edit .env with your values:

STRAVA_CLIENT_ID=your_client_id

STRAVA_CLIENT_SECRET=your_client_secret PUBLIC_URL=https://your-public-url.example.com

All variables are listed in docs/operations.md. Prefer the prebuilt image? Pull ghcr.io/ljcl/strava-mcp:latest (also on the MCP registry as io.github.ljcl/strava-mcp) and point your compose image: at it instead of building; you still supply the Strava credentials yourself. Published images carry SBOM/provenance attestations you can verify — see operations.md.

Note on the `./data` bind mount: tokens persist there, and the distroless image runs as non-root UID 65534, so the directory must be writable by that UID or token persistence fails on first run:

mkdir -p data

sudo chown -R 65534:65534 data

Alternatively use a named volume in docker-compose.yml (e.g. strava-data:/app/data), which Docker initializes with correct ownership. More detail in operations.md.

3. Start the Server

docker compose up -d

GET /health reports liveness without spending a Strava API request; with MCP_AUTH_TOKEN it also reports auth and rate-limit state. Response shapes and monitoring guidance: operations.md.

4. Authorize with Strava

Visit https://your-public-url/auth/start in your browser. After authorizing, tokens are saved automatically and refreshed from then on. Check status anytime at /auth/status.

If you set MCP_AUTH_TOKEN, append it to both URLs as ?token= .

5. Connect to Claude Desktop

Add to your Claude configuration (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

"mcpServers": { "strava": { "type": "url", "url": "https://your-public-url/mcp", "headers": { "Authorization": "Bearer your-mcp-auth-token" } } } }

The headers entry is only needed when MCP_AUTH_TOKEN is set (recommended for tunnel-exposed servers — see Securing the endpoint).

Restart Claude Desktop to load the new configuration.

Connecting to AI Tools

Most AI tools (Claude Desktop, Claude Code, etc.) need an HTTPS URL to reach your MCP server. Since the server runs on your local network, you'll need a tunnel to expose it.

Tailscale Funnel (Recommended)

Tailscale Funnel exposes a local port to the internet over HTTPS with no configuration:

tailscale funnel --bg 3000

→ https://your-machine.tail1234.ts.net

Set PUBLIC_URL in your .env to the resulting URL.

Cloudflare Tunnel

cloudflared tunnel --url http://localhost:3000

Securing the endpoint

A tunnel makes /mcp reachable by anyone who discovers the URL — including the update-activity write tool. Set MCP_AUTH_TOKEN to a long random secret (openssl rand -hex 32) and every /mcp request requires Authorization: Bearer ; each client snippet below shows where the header goes. The secret also gates /auth/start and /auth/status. Full details (including how OAuth callbacks stay safe): operations.md.

Set it in .env alongside your Strava credentials — docker-compose.yml forwards it automatically.

AI Tool (Claude Desktop, Claude Code, etc.)

│ HTTPS HTTPS Tunnel (Tailscale / Cloudflare) │ HTTP (localhost:3000) Strava MCP Server (Docker / Bun) │ HTTPS Strava API

Client configuration

The server works with any MCP client that supports the Streamable HTTP transport. In every snippet below, replace https://your-public-url with your tunnel URL (or http://localhost:3000 for local development), and include the Authorization header only if you set MCP_AUTH_TOKEN.

Claude Code

claude mcp add --transport http strava https://your-public-url/mcp \

--header "Authorization: Bearer your-mcp-auth-token"

Cursor

Add to .cursor/mcp.json in your project (or ~/.cursor/mcp.json for all projects):

"mcpServers": { "strava": { "url": "https://your-public-url/mcp", "headers": { "Authorization": "Bearer your-mcp-auth-token" } } } }

VS Code

Add to .vscode/mcp.json in your workspace (or run MCP: Add Server from the command palette):

"servers": { "strava": { "type": "http", "url": "https://your-public-url/mcp", "headers": { "Authorization": "Bearer your-mcp-auth-token" } } } }

Other clients (generic Streamable HTTP)

Any client that speaks Streamable HTTP can connect to the /mcp endpoint directly. One URL serves both protocol eras: 2026-07-28 clients send stateless requests carrying the io.modelcontextprotocol/* envelope keys (server/discover advertises capabilities); 2025-era clients use the ordinary initialize handshake. POST JSON-RPC messages with an Accept: application/json, text/event-stream header. Protocol details: docs/architecture.md.

Using alongside the official Strava MCP

Strava's official MCP connector handles activity discovery and basic reads. This server supplements it with everything the official connector does not offer: writing to activities, segments, routes and GPX/TCX export, photos, derived analysis, and interactive visualizations.

Install both

Official: claude mcp add --transport http strava-mcp https://mcp.strava.com/mcp (or via claude.ai Connectors / Claude Desktop).
This server: see the install steps above.

Who does what

Capability	Official	This server
List / read activities, streams, profile, zones, gear, clubs, training plan	yes	no (use official)
Update activities, star segments	no	yes
Segment detail / search / efforts	no	yes
Routes plus GPX/TCX export	no	yes
Activity GPX export (synthesized from streams)	no	yes
Activity photos	no	yes
Athlete stats, per-activity zones, best efforts, running summary, training load, compare	no	yes
Interval, hill, and aerobic analysis; fitness/fatigue/form (CTL/ATL/TSB)	no	yes
Interactive apps: activity chart, cadence trends, route map, activity segments, training load, compare activities, activity zones, segment progress, fitness trend	no	yes

Caveats

The official connector requires a Strava subscription and currently runs only in Anthropic clients.
With the duplicate reads removed, this server now effectively assumes the official connector is installed for activity discovery. The aggregate analysis tools (get-best-efforts, get-training-load) fetch their own activity lists, but per-activity tools (get-running-summary, compare-activities, get-activity-zones, etc.) need an activity id from the official list_activities.
The two use separate rate-limit quotas, so running both spreads API load.

Recommended workflow

Use the official connector to discover and read activities, then use this server to write, explore segments, manage and export routes, and visualize. The model can pass activity ids from official list_activities directly into this server's tools.

Example requests

Ask your AI assistant questions like these (use the official Strava MCP to discover activity IDs, then pass them to these tools):

"Update the title of activity 12345678 to 'Morning Threshold'"
"Show me the HR zone breakdown for activity 12345678"
"Break down the intervals in activity 12345678 — did I fade across the reps?"
"Did I positive-split Sunday's long run, or was that just the hills?"
"My race is on 13 September — what should the next three weeks look like so I arrive at TSB +10?"
"Am I getting faster on segment 8109834? Show my effort history"
"Map my race route with fuel stops at 10k, 21k, and 32k, and flag the climb at 28k"

Local Development

Prerequisites: Bun and a Strava account.

bun install

Guided OAuth flow using localhost as redirect URI

cd apps/server && bun run setup-auth && cd ../..

Start dev server (server + MCP App watchers)

bun run dev

Then point any client at http://localhost:3000/mcp. Repo layout, task runner, tests, coverage gates, and Storybook workflow: docs/development.md. Agent conventions live in AGENTS.md.

Documentation

Doc	Contents
docs/tools.md	Full tool catalog, prompts, permission behaviour, example requests
docs/operations.md	Environment variables, auth/token handling, health endpoint, rate limits, endpoint security
docs/architecture.md	Server architecture: transport, HTTP layer, cache, error taxonomy, analysis math
docs/mcp-apps.md	MCP App packages: shared shell, mobile, theming, per-app details
docs/development.md	Monorepo mechanics: Turborepo, coverage gates, Storybook gates, Docker build
docs/releasing.md	Release automation: Conventional Commit PR titles, release-please, publishing
docs/project.md	Issue tracking and project board

PRs are squash-merged and the PR title becomes the commit on `main`, so write it as a [Conventional Commit](https://www.con

Only the beginning is shown; read the rest in the repo

Strava MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Hunter Killer

README from the maker

Strava MCP

Features

Quick Start (Docker)

1. Create a Strava API Application

2. Configure Environment

3. Start the Server

4. Authorize with Strava

5. Connect to Claude Desktop

Connecting to AI Tools

Tailscale Funnel (Recommended)

→ https://your-machine.tail1234.ts.net

Cloudflare Tunnel

Securing the endpoint

Client configuration

Claude Code

Cursor

VS Code

Other clients (generic Streamable HTTP)

Using alongside the official Strava MCP

Install both

Who does what

Caveats

Recommended workflow

Example requests

Local Development

Guided OAuth flow using localhost as redirect URI

Start dev server (server + MCP App watchers)

Documentation