Strava MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STRAVA_CLIENT_ID | Yes | Client ID from Strava API application | |
| STRAVA_CLIENT_SECRET | Yes | Client Secret from Strava API application | |
| STRAVA_REFRESH_TOKEN | Yes | Refresh token obtained via OAuth authorization |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_activitiesB | アスリートのアクティビティ一覧を取得します。ページネーションに対応しています。 |
| get_activityA | 特定のアクティビティの詳細情報を取得します。 |
| get_athleteA | 認証されたアスリートのプロフィール情報を取得します。 |
| get_athlete_statsB | アスリートの統計情報（総距離、総時間など）を取得します。 |
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 4 tools
The four tools are clearly distinct: one lists activities, one gets activity details, one gets athlete profile, and one gets athlete stats. No overlap or confusion between them.
All tool names follow a consistent get_noun pattern using snake_case. The naming is predictable and uniform across the entire set.
With 4 tools, the count is well-scoped for a read-only Strava integration. It covers the core data retrieval endpoints without unnecessary bloat.
The set covers primary needs: listing activities, retrieving activity details, and getting athlete profile and stats. However, it lacks advanced read endpoints like activity streams or club/route data, which are minor gaps for a comprehensive Strava API surface.