Enterprise DNA
M MCP Servers Developer low

r-huijts/strava-mcp

by Various

A Model Context Protocol (MCP) server that connects to Strava API, providing tools to access Strava data through LLMs

R

MCP

r-huijts/strava-mcp

Added 1 June 2026

Overview

This MCP server exposes Strava API data to LLMs through the Model Context Protocol. It provides tools for querying athlete activities, segments, and other Strava resources directly from a chat interface.

Best for

Best for
Developers building AI assistants or tools that need to query and analyze Strava activity data through natural language.

Use cases

  • Retrieve recent activities and performance metrics via natural language queries
  • Analyze segment efforts and compare personal records across time
  • Build an LLM-powered coaching assistant that accesses Strava data

Notes

This MCP server exposes Strava API data to LLMs through the Model Context Protocol. It provides tools for querying athlete activities, segments, and other Strava resources directly from a chat interface.

427 stars on GitHub. Last updated 2026-04-07. Licensed MIT.

Use cases

  • Retrieve recent activities and performance metrics via natural language queries
  • Analyze segment efforts and compare personal records across time
  • Build an LLM-powered coaching assistant that accesses Strava data

Pros

  • Open source with active community (427 stars) and clear TypeScript codebase
  • Leverages the MCP standard, making integration straightforward for any MCP-compatible LLM client
  • Reduces boilerplate by handling Strava API authentication and request formatting

Cons

  • Relies on Strava API rate limits, which may throttle frequent requests
  • OAuth setup required for each user, adding friction for multi-user deployments
  • Limited to read-only data exposed by Strava API (no write support for creating activities)

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Open source with active community (427 stars) and clear TypeScript codebase
  • Leverages the MCP standard, making integration straightforward for any MCP-compatible LLM client
  • Reduces boilerplate by handling Strava API authentication and request formatting

Cons

  • Relies on Strava API rate limits, which may throttle frequent requests
  • OAuth setup required for each user, adding friction for multi-user deployments
  • Limited to read-only data exposed by Strava API (no write support for creating activities)