Skip to main content
Glama
Sign In

HAPI Strava MCP Server

by ai.com.mcp
OverviewDiscussionsAdmin

Server Details

Strava MCP tools for AI: athletes, activities, segments, clubs, routes. Powered by HAPI MCP server.

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
31.3% over 73 days
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL
Repository
mcp-com-ai/hapimcp
GitHub Stars
1
Server Listing
HAPI MCP
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 13 tools

Disambiguation5/5

Each tool targets a distinct resource and operation: segments, clubs, gear, athlete, routes, and stats. Even potentially similar tools like getEffortsBySegmentId and getSegmentEffortById are clearly differentiated by their descriptions (listing efforts vs. fetching a single effort).

Naming Consistency5/5

All tool names follow a consistent camelCase pattern with a verb (get, explore) followed by a specific noun phrase. Names like getClubById, getLoggedInAthlete, and getStats are uniform and predictable, making it easy to infer their purpose.

Tool Count5/5

With 13 tools, the server is well-scoped for a focused read-only API over Strava data. The count is within the ideal range and each tool covers a meaningful aspect of the domain without redundancy or bloat.

Completeness3/5

The tool surface covers several Strava domains (clubs, segments, gear, routes, athlete stats) but is missing any activity-related operations (e.g., list activities, get activity by ID) and all write operations. This creates notable gaps for a comprehensive Strava integration, though the read-only scope may be intentional.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 21 tool updates
    • RemovedcreateActivity
    • RemovedcreateUpload
    • RemovedgetActivityById
    • RemovedgetActivityStreams
    • RemovedgetCommentsByActivityId
    • RemovedgetKudoersByActivityId
    • RemovedgetLapsByActivityId
    • RemovedgetLoggedInAthleteActivities
    • RemovedgetLoggedInAthleteZones
    • RemovedgetRouteAsGPX
    • RemovedgetRouteAsTCX
    • RemovedgetRouteById
    • RemovedgetRouteStreams
    • RemovedgetSegmentById
    • RemovedgetSegmentEffortStreams
    • RemovedgetSegmentStreams
    • RemovedgetUploadById
    • RemovedgetZonesByActivityId
    • RemovedstarSegment
    • RemovedupdateActivityById
    • RemovedupdateLoggedInAthlete
  2. 34 tool updates
    • First observedcreateActivity
    • First observedcreateUpload
    • First observedexploreSegments
    • First observedgetActivityById
    • First observedgetActivityStreams
    • First observedgetClubActivitiesById
    • First observedgetClubAdminsById
    • First observedgetClubById
    • First observedgetClubMembersById
    • First observedgetCommentsByActivityId
    • First observedgetEffortsBySegmentId
    • First observedgetGearById
    • First observedgetKudoersByActivityId
    • First observedgetLapsByActivityId
    • First observedgetLoggedInAthlete
    • First observedgetLoggedInAthleteActivities
    • First observedgetLoggedInAthleteClubs
    • First observedgetLoggedInAthleteStarredSegments
    • First observedgetLoggedInAthleteZones
    • First observedgetRouteAsGPX
    • First observedgetRouteAsTCX
    • First observedgetRouteById
    • First observedgetRoutesByAthleteId
    • First observedgetRouteStreams
    • First observedgetSegmentById
    • First observedgetSegmentEffortById
    • First observedgetSegmentEffortStreams
    • First observedgetSegmentStreams
    • First observedgetStats
    • First observedgetUploadById
    • First observedgetZonesByActivityId
    • First observedstarSegment
    • First observedupdateActivityById
    • First observedupdateLoggedInAthlete

Related MCP Connectors

Related MCP Servers

  • Strava MCP Server

    justmytwospence
    A
    license
    A
    quality
    A
    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.
    33
    83 npm
    ISC

  • stravamcp

    sivaparthi
    F
    license
    A
    quality
    D
    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
    -
Try in Browser
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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources