Strava-mcp Server

Strava-mcp is an MCP integration. Remote MCP server for your Strava activities, segments, and routes.

Packages and local setup

The published oci package is ghcr.io/ljcl/strava-mcp:3.0.0. Its declared MCP transport is streamable-http.

The package declares STRAVA_CLIENT_ID (required): Strava API client ID; STRAVA_CLIENT_SECRET (required): Strava API client secret; PUBLIC_URL (required): Public HTTPS URL used for the Strava OAuth callback; STRAVA_ACCESS_TOKEN: Optional initial access token from setup-auth; STRAVA_REFRESH_TOKEN: Optional initial refresh token from setup-auth; MCP_AUTH_TOKEN: Shared secret gating /mcp and the OAuth web routes (recommended when internet-facing); PORT: Server port (default 3000); TOKEN_DATA_DIR: Override token storage directory (default ./data); ROUTE_EXPORT_PATH: Absolute directory for exported route files.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 3.0.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.