strava-mcp

MCP server for the Strava API v3. Exposes Strava data — activities, segments, routes, clubs, gear, and streams — as tools that any MCP client (Claude Desktop, Claude Code, etc.) can call.

Read-only by default. Pass --write to enable mutating tools (create/update activities, star segments).

OpenClaw-specific onboarding and sidecar setup: OPENCLAW.md.

Getting started

1. Create a Strava API application

Go to https://www.strava.com/settings/api and create an application. Note your Client ID and Client Secret.

2. Set up credentials

cp .env.example .env

Add your STRAVA_CLIENT_ID and STRAVA_CLIENT_SECRET to .env.

3. Build

pnpm install
pnpm build

4. Authenticate

pnpm auth

This opens your browser to authorize with Strava. After you approve, it automatically exchanges the code for tokens and saves STRAVA_ACCESS_TOKEN and STRAVA_REFRESH_TOKEN to your .env file. All scopes are requested (read_all, profile:read_all, activity:read_all, activity:write).

5. Test locally

pnpm inspect

Opens the MCP Inspector web UI where you can browse tools and call them interactively. Credentials are loaded from .env automatically.

You can also run the server directly:

pnpm start

6. Configure your MCP client

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "strava": {
      "command": "node",
      "args": ["/absolute/path/to/strava-mcp/build/index.js"],
      "env": {
        "STRAVA_ACCESS_TOKEN": "your-access-token"
      }
    }
  }
}

To enable write tools (create/update activities, star segments), add "--write" to args:

{
  "mcpServers": {
    "strava": {
      "command": "node",
      "args": ["/absolute/path/to/strava-mcp/build/index.js", "--write"],
      "env": {
        "STRAVA_ACCESS_TOKEN": "your-access-token"
      }
    }
  }
}

Claude Code

claude mcp add strava node /absolute/path/to/strava-mcp/build/index.js

Automatic token refresh

Strava access tokens expire. To enable automatic refresh, provide all four env vars:

{
  "env": {
    "STRAVA_ACCESS_TOKEN": "your-access-token",
    "STRAVA_REFRESH_TOKEN": "your-refresh-token",
    "STRAVA_CLIENT_ID": "your-client-id",
    "STRAVA_CLIENT_SECRET": "your-client-secret"
  }
}

When a request returns 401 and refresh credentials are available, the server will automatically request a new access token from Strava's OAuth endpoint and retry the request.

Related MCP server: strava-mcp

Environment variables

Tools

Read tools (always available)

Athlete

Activities

Segments

Routes

Clubs

Gear

Write tools (requires --write flag)

Documentation

• Use cases — example prompts and what you can do with the server

• Architecture — file structure, data flow, and component responsibilities

• Design decisions — rationale behind the read/write split, token refresh strategy, thin client approach, and other trade-offs