"Using Strava Data for Analysis or Integration" matching MCP servers:

Enables AI assistants to read your Strava training data and answer plain-language questions about activities, splits, and totals across sports like running, skiing, and hiking.

Minimalist Strava integration for Claude with 7 focused tools for querying athlete stats, activities, zones, and segment analysis.

A read-only local MCP server for querying your own Strava data from Codex, providing tools for activities, athlete profile, stats, gear, and more.

Privacy-first MCP server for Strava activities, streams, routes and training data.

MCP server that exposes Strava API v3 data (activities, segments, routes, clubs, gear, streams) as tools for any MCP client. Read-only by default, with an optional --write flag to enable mutating operations.

Exposes your Strava data to Claude, enabling training load analysis, activity comparison, and lap splits via conversation.

An MCP server that integrates Strava OAuth for remote connections, enabling users to authenticate with their Strava account and access Strava data through the MCP protocol.

An MCP server that supplements the official Strava connector with write access, segments, routes, photos, derived analysis, and interactive visualizations.

Connects Claude to your Strava fitness data, enabling natural language queries about your training history such as activities, stats, and routes.

Exposes Strava training data to Claude for coaching, planning, and analysis via a read-only MCP server with OAuth and Docker support.

Connects Strava training data to Claude, enabling personalized coaching through analysis of training load, workout planning, gear maintenance, and power metrics.

Connects Claude to your Strava account so you can query your activities, stats, routes, and segments using natural language.

An MCP server that enables interaction with the Strava API v3 to manage fitness activities, athlete profiles, segments, and routes. It supports retrieving detailed performance metrics, exploring geographic data, and managing club information through natural language.

A TypeScript server that acts as a bridge to the Strava API, enabling LLMs to access users' activities, routes, segments, and athlete data through natural language interaction.

A local, read-only Model Context Protocol server for an athlete's Strava profile and activities, enabling retrieval of profile data, activity lists (with paging and date filters), and detailed activity information via standard input/output for MCP hosts.

Enables users to interact with their Strava data through natural language to analyze workouts, track fitness progress, and explore routes. It supports retrieving detailed activity stats, heart rate data, and segment insights directly within AI assistants.

Provides live wait times and office details for all 60 Oregon DMV field offices by scraping the ODOT website, with no authentication required.

Enables agents to read and analyze personal Strava cardio data, including activity summaries, detailed activities, laps, heart-rate and power zones, streams, and aggregate statistics, through the official Strava API with read-only permissions.

Connects Claude to Strava data for natural language queries about rides, stats, and activities.

An HTTP broker that exposes Strava data and operations (activities, routes, segments, etc.) as MCP tools, allowing users to interact with their own Strava account via natural language using per-user OAuth2 authentication.