Skip to main content
Glama

Strava MCP Server

CI/CD Pipeline codecov

A Model Context Protocol (MCP) server for interacting with the Strava API.

User Guide

Installation

You can easily install Strava MCP with uvx:

uvx strava-mcp

Setting Up Strava Credentials

  1. Create a Strava API Application:

  2. Configure Your Credentials: Create a credentials file (e.g., ~/.ssh/strava.sh):

    export STRAVA_CLIENT_ID=your_client_id
    export STRAVA_CLIENT_SECRET=your_client_secret
  3. Configure Claude Desktop: Add the following to your Claude configuration (/Users/<username>/Library/Application Support/Claude/claude_desktop_config.json):

    "strava": {
        "command": "bash",
        "args": [
            "-c",
            "source ~/.ssh/strava.sh && uvx strava-mcp"
        ]
    }

Authentication

The first time you use the Strava MCP tools:

  1. An authentication flow will automatically start

  2. Your browser will open to the Strava authorization page

  3. After authorizing, you'll be redirected back to a local page

  4. Your refresh token will be saved automatically for future use

Available Tools

Get User Activities

Retrieves activities for the authenticated user.

Parameters:

  • before (optional): Epoch timestamp for filtering

  • after (optional): Epoch timestamp for filtering

  • page (optional): Page number (default: 1)

  • per_page (optional): Number of items per page (default: 30)

Get Activity

Gets detailed information about a specific activity.

Parameters:

  • activity_id: The ID of the activity

  • include_all_efforts (optional): Include segment efforts (default: false)

Get Activity Segments

Retrieves segments from a specific activity.

Parameters:

  • activity_id: The ID of the activity

Get Segment Leaderboard

Gets the leaderboard for a specific segment.

Parameters:

  • segment_id: The ID of the segment

  • Various optional filters (gender, age group, etc.)

Related MCP server: Strava MCP Server

Developer Guide

Project Setup

  1. Clone the repository:

    git clone <repository-url>
    cd strava
  2. Install dependencies:

    uv install
  3. Set up environment variables:

    export STRAVA_CLIENT_ID=your_client_id
    export STRAVA_CLIENT_SECRET=your_client_secret

    Alternatively, create a .env file with these variables.

Running in Development Mode

Run the server with MCP CLI:

mcp dev strava_mcp/main.py

Manual Authentication

You can get a refresh token manually by running:

python get_token.py

Project Structure

  • strava_mcp/: Main package directory

    • __init__.py: Package initialization

    • config.py: Configuration settings using pydantic-settings

    • models.py: Pydantic models for Strava API entities

    • api.py: Low-level API client for Strava

    • auth.py: Strava OAuth authentication implementation

    • oauth_server.py: Standalone OAuth server implementation

    • service.py: Service layer for business logic

    • server.py: MCP server implementation

  • tests/: Unit tests

  • strava_mcp/main.py: Main entry point to run the server

  • get_token.py: Utility script to get a refresh token manually

Running Tests

pytest

Publishing to PyPI

Building the package

# Build both sdist and wheel
uv build

Publishing to PyPI

# Publish to Test PyPI first
uv publish --index testpypi

# Publish to PyPI
uv publish

License

MIT License

Acknowledgements

Available Tools

3 tools
get_activityC

Get details of a specific activity.

Args: ctx: The MCP request context activity_id: The ID of the activity include_all_efforts: Whether to include all segment efforts

Returns: The activity details

Inputs: activity_id (required), include_all_efforts.

get_activity_segmentsC

Get the segments of a specific activity.

Args: ctx: The MCP request context activity_id: The ID of the activity

Returns: List of segment efforts for the activity

Inputs: activity_id (required).

get_user_activitiesB

Get the authenticated user's activities.

Args: ctx: The MCP request context before: An epoch timestamp for filtering activities before a certain time after: An epoch timestamp for filtering activities after a certain time page: Page number per_page: Number of items per page

Returns: List of activities

Inputs: before, after, page, per_page.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: get_activity retrieves details of a specific activity, get_activity_segments focuses on segments within an activity, and get_user_activities lists the user's activities. The descriptions clearly differentiate these functions, making tool selection unambiguous for an agent.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (get_activity, get_activity_segments, get_user_activities). The naming is predictable and readable, using 'get' as the verb throughout, which aligns well with the read-only nature of these tools.

    Tool Count2/5

    With only 3 tools, this server feels under-scoped for a Strava integration, which typically involves activities, segments, athletes, and more. While the tools cover some read operations, the count is too low to support comprehensive agent workflows, such as creating or updating activities, which are common in fitness tracking domains.

    Completeness2/5

    The tool surface is severely incomplete for a Strava server, as it only includes read operations (get) with no support for create, update, or delete actions. There are significant gaps, such as missing tools for managing segments, athletes, or uploading activities, which will likely cause agent failures when attempting full interactions with the Strava API.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides language models with access to Strava API data, allowing them to query and analyze athlete activities from Strava.
      4
      25
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables language models to interact with Strava data, including activities, athlete statistics, routes, achievements, and social features.
      6
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An MCP server that enables interaction with the Strava API v3 to manage fitness activities, athlete profiles, segments, and routes. It supports retrieving detailed performance metrics, exploring geographic data, and managing club information through natural language.
      33
      132 npm
      ISC