Strava

An MCP server to interact with Strava

python

4

GitHub Stars

python

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "yorrickjansen-strava-mcp": {
      "command": "mcp",
      "args": [
        "dev",
        "strava_mcp/main.py"
      ],
      "env": {
        "STRAVA_CLIENT_ID": "YOUR_CLIENT_ID",
        "STRAVA_CLIENT_SECRET": "YOUR_CLIENT_SECRET"
      }
    }
  }
}

You can run a Strava MCP Server that connects to the Strava API and exposes a set of MCP endpoints for getting user activities, activities, segments, and segment leaderboards. This server handles OAuth authentication and token management, so you can focus on querying Strava data from your MCP clients.

How to use

To use this Strava MCP Server, start the local MCP instance and connect with an MCP client. The server supports standard MCP requests to retrieve user activities, fetch detailed activity data, access activity segments, and obtain segment leaderboards. Authenticate once, and the server will securely refresh tokens for subsequent requests. When you launch the server, you perform authentication in the browser-based flow, after which the server stores the refresh token for future use.

Run your MCP client and point it at the local MCP server you started. Use the available endpoints to query data such as recent activities, details of a specific activity, segments within an activity, and a leaderboard for a given segment. The server handles authorization with Strava and keeps tokens refreshed automatically for ongoing requests.

How to install

Prerequisites you need before installing this server are: a runtime for the MCP environment, the MCP CLI, and an environment to store Strava credentials.

Install the MCP runtime and CLI using the package manager you use for your environment. Then install the Strava MCP Server package using the appropriate command for your setup.

Start the MCP server in development mode with the following command so you can test and iterate while developing.

Configuration and credentials

Set up Strava credentials so the server can perform authenticated requests. First, create a Strava API Application to obtain your Client ID and Client Secret. Use localhost as the Authorization Callback Domain.

Store your credentials in a dedicated environment file or source them before starting the server. Example environment variables to define are STRAVA_CLIENT_ID and STRAVA_CLIENT_SECRET.

When you start the server, a browser-based authentication flow will run automatically. You will authorize access in the browser, and the server will save a refresh token for future requests.

Security notes

Keep your Strava credentials secret. Store them in secure environment files or secret managers. Do not hard-code credentials in your source code or configuration files that are checked into version control.

Available tools

Get User Activities

Retrieves activities for the authenticated Strava user with optional filtering by time range and pagination.

Get Activity

Fetches detailed information about a single Strava activity, with an option to include all segment efforts.

Get Activity Segments

Retrieves segments associated with a specific activity.

Get Segment Leaderboard

Fetches the leaderboard for a specified segment with optional filters.