Skip to content
HAPI Strava MCP Server logo

HAPI Strava MCP Server

Verified

Strava API exposed as MCP tools via HAPI for AI agents.

MCP ServerAI & KnowledgeRemote (streamable-http) 8
View on GitHub
Updated 2026-06-16

What is the HAPI Strava MCP Server MCP server?

Built on the HAPI MCP framework, this server automatically lifts an existing Strava API specification into MCP-compatible tools. No additional business logic or sidecar services are required; governance and security remain those of the original Strava API.

The resulting streamable-http MCP endpoint works with any compliant client including ChatGPT, Claude and custom agents, enabling deterministic access to Strava data inside AI workflows.

Install & connect

Add this to your MCP client config. Pick your client below and copy.

{
  "mcpServers": {
    "strava": {
      "url": "https://strava.run.mcp.com.ai/mcp"
    }
  }
}

Tools it exposes

5 tools your AI client can call once connected.

athletesStrava athlete profile and stats access
activitiesStrava activity listing, details and creation
segmentsStrava segment exploration and leaderboards
clubsStrava club membership and activity data
routesStrava route management and export

Example prompts

Once connected, try asking your AI client:

List my last 10 Strava activities with distance and time
Show athlete stats for user ID 12345
Find popular segments near my location
Export a route by its ID

Security & permissions

Requires a valid Strava OAuth token or API key passed via environment variables; runs as a remote streamable-http service and touches only data the authenticated Strava account can access.

What you can do with HAPI Strava MCP Server

Training analytics

Pull recent activities and segment efforts to generate personalized training insights.

Club management

Query club rosters and shared activities for community dashboards or reports.

Route planning

Retrieve and analyze saved routes to suggest new cycling or running paths.

How to use HAPI Strava MCP Server

  1. 1Install the HAPI CLI from the latest GitHub release.
  2. 2Provide your Strava OpenAPI spec to the hapi serve command.
  3. 3Supply Strava credentials through environment variables or OAuth.
  4. 4Start the server with the --headless flag to expose the MCP endpoint.
  5. 5Connect any MCP client to the published streamable-http URL.

HAPI Strava MCP Server: pros & cons

Pros

  • +Zero code changes to existing Strava API logic
  • +Automatic tool generation keeps docs and runtime in sync
  • +Inherits Strava auth, rate limits and audit features
  • +Works with any standard MCP client

Cons

  • Dependent on Strava API availability and quotas
  • Limited to operations defined in the source OpenAPI spec
  • Requires separate management of Strava credentials
Did you find this helpful?

Frequently asked questions

No. HAPI lifts the existing OpenAPI spec directly into MCP tools.

User reviews

Verified reviews from the community shape this listing's rating.

Loading reviews…

Sign in to review

Promote HAPI Strava MCP Server

Add this badge to your website, or share the tool.

DFeatured on DhanasviHAPI Strava MCP Server 0