claudex-strava-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STRAVA_CLIENT_ID | Yes | Your Strava API client ID | |
| STRAVA_CLIENT_SECRET | Yes | Your Strava API client secret | |
| STRAVA_REFRESH_TOKEN | Yes | Your Strava refresh token for OAuth |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_athlete_profileA | Get the authenticated athlete's profile including name, location, and preferences |
| get_athlete_statsA | Get athlete statistics including total distance, time, elevation for running, cycling, and swimming. Includes recent, year-to-date, and all-time totals. |
| list_activitiesA | List the authenticated athlete's recent activities with pagination. Returns summary data for each activity including name, type, distance, time, and elevation. |
| get_activityA | Get detailed information about a specific activity including splits, segment efforts, and all metrics. Use list_activities first to find activity IDs. |
| get_activity_lapsA | Get lap data for a specific activity. Each lap includes time, distance, pace, heart rate, and other metrics. |
| get_activity_zonesA | Get heart rate and power zone distribution for a specific activity. Shows time spent in each zone. |
| list_routesA | List the athlete's saved routes. Returns summary data including name, distance, elevation gain, and type. |
| get_routeA | Get detailed information about a specific route including distance, elevation profile, and waypoints. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct resource/action: athlete profile, stats, activities (list and detail), activity laps, activity zones, routes (list and detail). No two tools overlap in purpose, and descriptions clearly differentiate list-level summaries from detail-level data.
All tool names follow a consistent verb_noun pattern: 'get_' for single resources and 'list_' for collections. CamelCase is not used, and the pattern is uniformly applied across all eight tools.
Eight tools is well-scoped for a Strava data retrieval server. Each tool covers a distinct aspect of athlete, activity, or route data, and the count is neither too small for utility nor too large for coherence.
The domain appears to be read-only athlete data retrieval. Core areas are covered: profile, stats, activities, activity details (laps, zones), and routes. Minor gaps exist, such as activity streams or segment efforts, but these are not essential for the apparent primary purpose.