Strava MCP Server
# Strava MCP Server
[](https://opensource.org/licenses/MIT)
[](https://www.python.org/downloads/release/python-3100/)
[](https://cursor.com/install-mcp?name=strava&config=eyJjb21tYW5kIjoidXZ4IHN0cmF2YS1tY3Atc2VydmVyIiwiZW52Ijp7IlNUUkFWQV9DTElFTlRfSUQiOiJZT1VSX0NMSUVOVF9JRCIsIlNUUkFWQV9DTElFTlRfU0VDUkVUIjoiWU9VUl9DTElFTlRfU0VDUkVUIiwiU1RSQVZBX1JFRlJFU0hfVE9LRU4iOiJZT1VSX1JFRlJFU0hfVE9LRU4ifX0%3D)
A [Model Context Protocol](https://modelcontextprotocol.io/introduction) (MCP) server that provides access to the Strava API. It allows language models to query athlete activities data from the Strava API.
## Available Tools
The server exposes the following tools:
### Activities Queries
- `get_activities(limit: int = 10)`: Get the authenticated athlete's recent activities
- `get_activities_by_date_range(start_date: str, end_date: str, limit: int = 30)`: Get activities within a specific date range
- `get_activity_by_id(activity_id: int)`: Get detailed information about a specific activity
- `get_recent_activities(days: int = 7, limit: int = 10)`: Get activities from the past X days
Dates should be provided in ISO format (`YYYY-MM-DD`).
## Activity Data Format
The server returns activity data with consistent field names and units:
| Field | Description | Unit |
|-------|-------------|------|
| `name` | Activity name | - |
| `sport_type` | Type of sport | - |
| `start_date` | Start date and time | ISO 8601 |
| `distance_metres` | Distance | meters |
| `elapsed_time_seconds` | Total elapsed time | seconds |
| `moving_time_seconds` | Moving time | seconds |
| `average_speed_mps` | Average speed | meters per second |
| `max_speed_mps` | Maximum speed | meters per second |
| `total_elevation_gain_metres` | Total elevation gain | meters |
| `elev_high_metres` | Highest elevation | meters |
| `elev_low_metres` | Lowest elevation | meters |
| `calories` | Calories burned | kcal |
| `start_latlng` | Start coordinates | [lat, lng] |
| `end_latlng` | End coordinates | [lat, lng] |
## Authentication
To use this server, you'll need to authenticate with the Strava API. Follow these steps:
1. Create a Strava API application:
- Go to [Strava API Settings](https://www.strava.com/settings/api)
- Create an application to get your Client ID and Client Secret
- Set the Authorization Callback Domain to `localhost`
2. Get your refresh token:
- Use the included `get_strava_token.py` script:
```bash
python get_strava_token.py
```
- Follow the prompts to authorize your application
- The script will save your tokens to a `.env` file
3. Set environment variables:
The server requires the following environment variables:
- `STRAVA_CLIENT_ID`: Your Strava API Client ID
- `STRAVA_CLIENT_SECRET`: Your Strava API Client Secret
- `STRAVA_REFRESH_TOKEN`: Your Strava API Refresh Token
## Usage
### Claude for Desktop
Update your `claude_desktop_config.json` (located in `~/Library/Application\ Support/Claude/claude_desktop_config.json` on macOS and `%APPDATA%/Claude/claude_desktop_config.json` on Windows) to include the following:
```json
{
"mcpServers": {
"strava": {
"command": "uvx",
"args": [
"strava-mcp-server"
],
"env": {
"STRAVA_CLIENT_ID": "YOUR_CLIENT_ID",
"STRAVA_CLIENT_SECRET": "YOUR_CLIENT_SECRET",
"STRAVA_REFRESH_TOKEN": "YOUR_REFRESH_TOKEN"
}
}
}
}
```
### Claude Web
For Claude Web, you can run the server locally and connect it using the MCP extension.
## Example Queries
Once connected, you can ask Claude questions like:
- "What are my recent activities?"
- "Show me my activities from last week"
- "What was my longest run in the past month?"
- "Get details about my latest cycling activity"
## Error Handling
The server provides human-readable error messages for common issues:
- Invalid date formats
- API authentication errors
- Network connectivity problems
## License
This project is licensed under the MIT License - see the LICENSE file for details.
TDQS
Scored across 4 tools
Multiple tools have overlapping purposes that could cause confusion. get_activities and get_recent_activities both retrieve recent activities with similar parameters, while get_activities_by_date_range provides date-based filtering that could also be used for recent activities. Only get_activity_by_id has a clearly distinct purpose.
All tool names follow a consistent verb_noun pattern with snake_case formatting. The naming is perfectly consistent across all four tools, making them predictable and easy to understand at a glance.
With only 4 tools, this feels thin for a Strava server that presumably handles athlete activities. While the count is reasonable for a minimal implementation, it lacks coverage for other Strava domains like segments, clubs, or athlete profiles that would be expected.
The tool surface is severely incomplete for a Strava integration. While it provides multiple ways to read activities, there are no tools for creating, updating, or deleting activities, nor any coverage of other Strava resources like segments, clubs, gear, or athlete statistics. This creates significant gaps that will limit agent capabilities.