Skip to main content
Glama
EthanDM

strava-mcp

by EthanDM
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to strava-mcp

No user-submitted related servers found.

    Related Servers

    • Strava MCP server

      ls2g08
      A
      license
      B
      quality
      C
      maintenance
      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.
      3
      11 npm
      MIT

    • catence

      rifusaki
      A
      license
      B
      quality
      A
      maintenance
      MCP server for local fitness-data extraction and analysis from Garmin Connect, Intervals.icu, and Strava. Provides read-only analytical tools over DuckDB and targeted Strava enrichment.
      35
      271 npm
      AGPL 3.0

    • strava-mcp

      zurfyx
      A
      license
      Not graded
      quality
      D
      maintenance
      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.
      11 npm
      1
      MIT

    • stravamcp

      sivaparthi
      F
      license
      A
      quality
      C
      maintenance
      An MCP server that exposes Strava v3 API as read-only tools for AI agents. It covers athlete profiles, activities, stats, routes, segments, and rate limits, with OAuth2 authorization handled via a companion HTTP server.
      20
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools are clearly distinct, but a few could overlap in intent, such as athlete_profile vs athlete_stats and sync_activities vs export_activities. Overall, the descriptions and resource targets make confusion unlikely.

    Naming Consistency3/5

    All tools share the strava_ prefix, but the pattern is inconsistent: some use resource_detail/resource_status, while others use verb_entity like sync_activities and export_activities. This mixed convention reduces predictability.

    Tool Count4/5

    16 tools is slightly above the typical well-scoped range, but the count is reasonable for a Strava API surface covering athlete, activity, gear, zones, streams, sync, cache, and export functionality.

    Completeness4/5

    The toolset covers the main read-oriented Strava data needs: athlete info, stats, activities, streams, zones, laps, gear, and cache/export workflows. It lacks write/create/update operations, but for a read-heavy MCP server this is likely sufficient.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources