Skip to main content
Glama
sivaparthi

stravamcp

by sivaparthi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to stravamcp

No user-submitted related servers found.

    Related Servers

    • SportMCP

      rmezapi
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that provides AI agents with secure, read-only access to personal Strava fitness data, including activities, performance stats, and more through 21 MCP tools.
      MIT

    • strava-mcp

      SrenoG
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server to fetch Strava activities using OAuth authentication with automatic token refresh. Allows retrieving recent activities, activities by date range, activity details, and athlete stats.
      -

    • 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.
      4 npm
      1
      MIT

    • Strava MCP Server

      justmytwospence
      A
      license
      A
      quality
      D
      maintenance
      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.
      43 npm
      ISC

    • strava-mcp

      tayden-b
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI agents to Strava data, enabling profile retrieval, activity listing, detailed views, and weekly summaries via MCP tools.
      MIT
    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.9/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool targets a distinct resource (athlete, activity, club, gear, route, segment) and action (get/list), with utility tools (rate limit, auth status) clearly separated. Even similar tools like get_athlete_summary and get_athlete_stats differ in granularity and purpose, making misselection unlikely.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (get_*, list_*), but strava_auth_status breaks the pattern by using a noun phrase instead of a verb. Additionally, get_athlete_zones vs get_activity_zones could be mistaken without careful reading, though the resource is explicit in each name.

    Tool Count3/5

    With 20 tools, the server is on the heavy side, exceeding the 15-tool threshold for a well-scoped set. However, each tool maps to a specific Strava API endpoint, and the count is justified by the wide read-only surface of the Strava API, so it is borderline rather than excessive.

    Completeness4/5

    The server covers the primary Strava resources (athlete, activities, clubs, gear, routes, segments) with both list and detail views, plus utility tools. Obvious gaps like activity upload or a dedicated segment efforts tool are absent, but agents can obtain segment efforts via activity detail and upload is not a standard read-only operation.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources