Schema | Strava MCP Server

Strava MCP Server

Describes the environment variables required to run the server.

Name	Required	Description
`STRAVA_CLIENT_ID`	No	Your Strava application Client ID (optional)
`STRAVA_ACCESS_TOKEN`	Yes	Your Strava access token (required)
`STRAVA_CLIENT_SECRET`	No	Your Strava application Client Secret (optional)
`STRAVA_REFRESH_TOKEN`	No	Your refresh token (optional, for token renewal)

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`	{}

Functions exposed to the LLM to take actions

Name	Description
get_athlete_profileB	Get the authenticated athlete's profile information including name, stats, and preferences
get_athlete_statsB	Get detailed statistics for the authenticated athlete including totals and recent activity counts
list_activitiesB	List the authenticated athlete's activities. Returns up to 30 activities by default.
get_activityC	Get detailed information about a specific activity by ID
get_segmentC	Get detailed information about a specific segment by ID
list_starred_segmentsB	List segments starred by the authenticated athlete
explore_segmentsC	Explore segments in a given area. Returns the top 10 segments matching the search criteria.
get_segment_effortsC	Get efforts on a specific 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/juanlarreapm/strava-mcp-server'

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