Strava MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STRAVA_CLIENT_ID | Yes | The Client ID of your Strava API application | |
| STRAVA_ACCESS_TOKEN | Yes | Strava API access token with required scopes (e.g., read, activity:read_all) | |
| STRAVA_CLIENT_SECRET | Yes | The Client Secret of your Strava API application | |
| STRAVA_REFRESH_TOKEN | Yes | Strava API refresh token used to automatically refresh expired access tokens |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/justmytwospence/strava-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server