Strava MCP Server
The Strava MCP Server enables interaction with the Strava API to retrieve and manage user activities and segments:
Retrieve User Activities: Fetch activities for the authenticated user with optional filters for time range and pagination
Get Activity Details: Obtain detailed information about a specific activity, including options to include segment efforts
Retrieve Activity Segments: Access segments associated with a specific activity
Get Segment Leaderboard: View leaderboards for specific segments with various filtering options (gender, age group)
Authentication Management: Automatically handle Strava OAuth authentication, including token refresh and storage
Provides tools for accessing data from the Strava API, including retrieving user activities, getting specific activity details, accessing activity segments, and viewing segment leaderboards.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Strava MCP Server show my last 5 running activities"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Strava MCP Server
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-mcpSetting Up Strava Credentials
Create a Strava API Application:
Create a new application to obtain your Client ID and Client Secret
For "Authorization Callback Domain", enter
localhost
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_secretConfigure 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:
An authentication flow will automatically start
Your browser will open to the Strava authorization page
After authorizing, you'll be redirected back to a local page
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 filteringafter(optional): Epoch timestamp for filteringpage(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 activityinclude_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 segmentVarious optional filters (gender, age group, etc.)
Related MCP server: Strava MCP Server
Developer Guide
Project Setup
Clone the repository:
git clone <repository-url> cd stravaInstall dependencies:
uv installSet up environment variables:
export STRAVA_CLIENT_ID=your_client_id export STRAVA_CLIENT_SECRET=your_client_secretAlternatively, create a
.envfile with these variables.
Running in Development Mode
Run the server with MCP CLI:
mcp dev strava_mcp/main.pyManual Authentication
You can get a refresh token manually by running:
python get_token.pyProject Structure
strava_mcp/: Main package directory__init__.py: Package initializationconfig.py: Configuration settings using pydantic-settingsmodels.py: Pydantic models for Strava API entitiesapi.py: Low-level API client for Stravaauth.py: Strava OAuth authentication implementationoauth_server.py: Standalone OAuth server implementationservice.py: Service layer for business logicserver.py: MCP server implementation
tests/: Unit testsstrava_mcp/main.py: Main entry point to run the serverget_token.py: Utility script to get a refresh token manually
Running Tests
pytestPublishing to PyPI
Building the package
# Build both sdist and wheel
uv buildPublishing to PyPI
# Publish to Test PyPI first
uv publish --index testpypi
# Publish to PyPI
uv publishLicense
Acknowledgements
Available Tools
3 toolsget_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
Scored across 3 tools
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.
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.
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.
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
Strava MCP tools for AI: athletes, activities, segments, clubs, routes. Powered by HAPI MCP server.
Model Context Protocol server for Studex tools, notifications, and profile integrations
Remote MCP server for training, nutrition, wellness, and performance data with OAuth 2.0.
Pace is a remote MCP server that exposes wearable and fitness data to Claude via the Model Context Protocol. It connects to Garmin, Oura, Whoop, Polar, Fitbit and 20+ devices and provides 15 tools for querying sleep, activity, recovery, and training data. Hosted on Google Cloud Run, OAuth 2.1 authentication, Streamable HTTP transport. Instructions: First you need to create an account at: https://pacetraining.co and connect your wearables. After that you can connect the remote Server via Custom Connector in Claude and OAuth 2.1 Flow startet.
Related MCP Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides language models with access to Strava API data, allowing them to query and analyze athlete activities from Strava.425MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables language models to interact with Strava data, including activities, athlete statistics, routes, achievements, and social features.6MIT
- AlicenseAqualityBmaintenanceAn 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.33132 npmISC
- AlicenseNot gradedqualityCmaintenanceMCP server for Strava integration, enabling LLMs to query activities, athlete stats, segments, routes, and perform training analysis.9MIT