Schema | Strava MCP Server

Strava MCP Server

Describes the environment variables required to run the server.

Name	Required	Description
`STRAVA_CLIENT_ID`	Yes	Strava API Client ID from your Strava API Application settings
`STRAVA_CLIENT_SECRET`	Yes	Strava API Client Secret from your Strava API Application settings
`STRAVA_REFRESH_TOKEN`	Yes	Strava API Refresh Token obtained through the OAuth authorization flow

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
get_athleteB	Get the profile of the authenticated Strava athlete
get_athlete_statsB	Get lifetime and recent statistics for the authenticated athlete (total runs, rides, swims, distances, etc.)
get_activitiesC	Get a list of recent Strava activities
get_activities_betweenC	Get Strava activities within a specific date range
get_activityC	Get detailed information for a specific Strava activity by ID
get_activity_streamsC	Get detailed time-series data (streams) for an activity: GPS coordinates, heartrate, power, cadence, altitude, etc.
get_starred_segmentsB	Get the authenticated athlete's starred segments
get_segmentB	Get detailed information about a specific Strava segment

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/KerkhofMe/StravaMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server