HAPI Strava MCP Server

Official13 toolsLive

by la-rebelion · HTML

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

ai.com.mcp/strava MCP Server

This MCP server exposes Strava-related capabilities as Model Context Protocol (MCP) tools for AI. It focuses on athletes, activities, segments, clubs, and routes, and is powered by a HAPI MCP server. The server is described as lifting an OpenAPI catalog into MCP tools for headless API access.

🛠️ Key Features

Strava MCP tools for AI: athletes, activities, segments, clubs, routes
Powered by HAPI MCP server
HAPI MCP lifts OpenAPI catalog into MCP tools automatically (per the provided excerpt)

🚀 Use Cases

AI integrations that need Strava data for athletes and activities
AI workflows involving Strava segments, clubs, and routes

⚡ Developer Benefits

Reuse of existing API logic via OpenAPI in, MCP tools out (per excerpt)
Separation between design (OAS/Arazzo) and runtime (agents/LLMs) (per excerpt)

⚠️ Limitations

Provided details do not specify authentication, tool schemas, or which 13 tools correspond to the features listed.

Captured live from the server via tools/list.

getStats

Get Athlete Stats - Returns the activity stats of an athlete. Only includes data from activities set to Everyone visibilty.

Parameters1

integer

required

Raw schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "integer",
      "format": "int64"
    }
  },
  "required": [
    "id"
  ]
}

getLoggedInAthlete

Get Authenticated Athlete - Returns the currently authenticated athlete. Tokens with profile:read_all scope will receive a detailed athlete representation; all others will receive a summary representation.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {}
}

getLoggedInAthleteStarredSegments

List Starred Segments - List of the authenticated athlete's starred segments. Private segments are filtered out unless requested by a token with read_all scope.

Parameters2

page	integer	optional
per_page	integer	optional

Raw schema

{
  "type": "object",
  "properties": {
    "page": {
      "type": "integer"
    },
    "per_page": {
      "type": "integer"
    }
  }
}

getEffortsBySegmentId

List Segment Efforts - Returns a set of the authenticated athlete's segment efforts for a given segment. Requires subscription.

Parameters4

segment_id	integer	required
start_date_local	string	optional
end_date_local	string	optional
per_page	integer	optional

Raw schema

{
  "type": "object",
  "properties": {
    "segment_id": {
      "type": "integer"
    },
    "start_date_local": {
      "type": "string",
      "format": "date-time"
    },
    "end_date_local": {
      "type": "string",
      "format": "date-time"
    },
    "per_page": {
      "type": "integer"
    }
  },
  "required": [
    "segment_id"
  ]
}

exploreSegments

Explore segments - Returns the top 10 segments matching a specified query.

Parameters4

bounds	array	required
activity_type	string	optional
min_cat	integer	optional
max_cat	integer	optional

Raw schema

{
  "type": "object",
  "properties": {
    "bounds": {
      "type": "array",
      "items": {
        "type": "number",
        "format": "float"
      },
      "minItems": 4,
      "maxItems": 4
    },
    "activity_type": {
      "type": "string",
      "enum": [
        "running",
        "riding"
      ]
    },
    "min_cat": {
      "type": "integer",
      "minimum": 0,
      "maximum": 5
    },
    "max_cat": {
      "type": "integer",
      "minimum": 0,
      "maximum": 5
    }
  },
  "required": [
    "bounds"
  ]
}

getSegmentEffortById

Get Segment Effort - Returns a segment effort from an activity that is owned by the authenticated athlete. Requires subscription.

Parameters1

integer

required

Raw schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "integer",
      "format": "int64"
    }
  },
  "required": [
    "id"
  ]
}

getClubById

Get Club - Returns a given club using its identifier.

Parameters1

integer

required

Raw schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "integer",
      "format": "int64"
    }
  },
  "required": [
    "id"
  ]
}

getClubMembersById

List Club Members - Returns a list of the athletes who are members of a given club.

Parameters3

id	integer	required
page	integer	optional
per_page	integer	optional

Raw schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "integer",
      "format": "int64"
    },
    "page": {
      "type": "integer"
    },
    "per_page": {
      "type": "integer"
    }
  },
  "required": [
    "id"
  ]
}

getClubAdminsById

List Club Administrators - Returns a list of the administrators of a given club.

Parameters3

id	integer	required
page	integer	optional
per_page	integer	optional

Raw schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "integer",
      "format": "int64"
    },
    "page": {
      "type": "integer"
    },
    "per_page": {
      "type": "integer"
    }
  },
  "required": [
    "id"
  ]
}

getClubActivitiesById

List Club Activities - Retrieve recent activities from members of a specific club. The authenticated athlete must belong to the requested club in order to hit this endpoint. Pagination is supported. Athlete profile visibility is respected for all activities.

Parameters3

id	integer	required
page	integer	optional
per_page	integer	optional

Raw schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "integer",
      "format": "int64"
    },
    "page": {
      "type": "integer"
    },
    "per_page": {
      "type": "integer"
    }
  },
  "required": [
    "id"
  ]
}

getLoggedInAthleteClubs

List Athlete Clubs - Returns a list of the clubs whose membership includes the authenticated athlete.

Parameters2

page	integer	optional
per_page	integer	optional

Raw schema

{
  "type": "object",
  "properties": {
    "page": {
      "type": "integer"
    },
    "per_page": {
      "type": "integer"
    }
  }
}

getGearById

Get Equipment - Returns an equipment using its identifier.

Parameters1

string

required

Raw schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string"
    }
  },
  "required": [
    "id"
  ]
}

getRoutesByAthleteId

List Athlete Routes - Returns a list of the routes created by the authenticated athlete. Private routes are filtered out unless requested by a token with read_all scope.

Parameters2

page	integer	optional
per_page	integer	optional

Raw schema

{
  "type": "object",
  "properties": {
    "page": {
      "type": "integer"
    },
    "per_page": {
      "type": "integer"
    }
  }
}

README.md6 KBView on GitHub

HAPI MCP – Headless API for Model Context Protocol

Stop rewriting systems for AI. Instantly turn your APIs into MCP servers.

HAPI MCP lifts your OpenAPI catalog into MCP tools automatically, keeping design (OAS/Arazzo) and runtime (agents/LLMs) cleanly separated. Your existing APIs become AI-ready tools—no new business logic, no sidecar servers, no rework.

Key Features

No rewrites: Reuse 100% of your API logic. OpenAPI in, MCP tools out. No parallel codebase or shadow services.
Faster time-to-value: Turn specs into agent-ready tools in minutes. Update the spec, ship new tools instantly.
Reduced risk: Permissions, auth, rate limits, auditability are inherited from your APIs—governance without bolt-ons.
Scales with you: runMCP delivers serverless-like elasticity with long-running when needed. Cold-start fast, stay warm for throughput.
Deterministic orchestration: OrcA plans and executes multi-tool tasks predictably—no brittle prompt chaining.
Vendor-neutral: Works with any MCP client: ChatGPT, Claude, QBot, chatMCP. OAS + MCP + Arazzo stay portable.

How It Works

Pick your API spec
- OpenAPI, Swagger, REST—HAPI CLI works with any API specification format.
- Supports OpenAPI 3.0+, REST APIs, OAuth 2.0 Dynamic Client Registration.
Run a single command
- One simple CLI command transforms your API into a usable MCP Server.
- No complex setup, zero configuration, works anywhere, cross-platform.
Use instantly
- Your API is now ready as a tool, AI agent, or testing interface.
- MCP server ready, AI agent compatible, testing interface, developer experience friendly.

Visual Pipeline

code

API Spec (swagger.json) → HAPI CLI → Usable Tool (AI-ready) ← MCP Clients

code

[ OpenAPI / Swagger ]       [ HAPI CLI ]        [ MCP Server ]
       (Your API)         →   (Transform)   →   (Usable Tool)
                                                 ↑          ↑
                                                 |          |
                                          [ ChatGPT ]  [ runMCP ]
                                          [ Claude  ]  [ OrcA   ]
                                          [ QBot    ]  [ chatMCP]
                                          [ Agents  ]

Who Wins With HAPI

Executives: Ship AI initiatives without ballooning cost. Keep teams focused on outcomes, not rewrites and integration sprawl.
Architects & PMs: Design with OpenAPI/Arazzo, run with MCP. Clear contracts, policy inheritance, and versioned workflows keep risk low.
Engineers & Ops: Deploy once. HAPI Server + runMCP scale tools; QBot/chatMCP give fast feedback; OrcA keeps executions deterministic.

Your Stack, Already Wired

HAPI Server: Turns OpenAPI into MCP tools automatically—contracts stay in sync with your source of truth.
runMCP: Autoscaling execution and testing for MCP tools; cold-start fast, stay warm when workflows run long.
QBot: CLI TUI for power users to interact with MCP tools directly from terminal or scripts.
chatMCP: Conversational client that speaks MCP natively for support, ops, and internal assistants.
OrcA: Deterministic planning and orchestration for multi-tool tasks; no brittle prompt spaghetti.
Agents: Build agentic systems from standard APIs—no custom glue. Connect MCP clients across platforms.

Demos

Playlist with demos
New HAPI MCP YT Channel with demos API-First and MCP

Documentation

FAQ

Do we need to rewrite our services?
No. HAPI MCP lifts your existing OpenAPI specs directly into MCP tools. Your auth, validation, and business rules remain unchanged.
Is this just another MCP server?
It’s the Headless API model: your API becomes the runtime. HAPI Server reflects it as MCP; runMCP scales it; OrcA orchestrates it. No duplicate logic.
Which clients can consume the tools?
Any MCP client: ChatGPT, Claude, QBot, chatMCP, bespoke orchestrators—vendor-neutral by design.
How do we keep control and compliance?
Your API remains the single source of truth. Policies, RBAC, rate limits, and audit logs flow through automatically; no shadow logic.
What about security and privacy?
Scoped credentials, per-tool permissions, and auditable calls are inherited from your API layer. HAPI adds guardrails and observability for regulated environments.
How fast can we get started?
You can transform your first API into an MCP tool in less than five minutes. The HAPI CLI makes it quick and painless.

Get Started

Install HAPI CLI from latest release: https://github.com/la-rebelion/hapimcp/releases
Transform your OpenAPI spec into an MCP server with a single command:
bash
```
hapi serve path/to/your/swagger.json --headless
```
Start using your MCP tools with any compatible client!
Explore the documentation for advanced usage and best practices.

Contributing

Contributions are welcome! Open a discussion or submit a pull request on GitHub: https://github.com/la-rebelion/hapimcp

License

HAPI MCP is licensed under the MIT License. See LICENSE for details.

Install

Tools (13)

getStatsgetLoggedInAthletegetLoggedInAthleteStarredSegmentsgetEffortsBySegmentIdexploreSegmentsgetSegmentEffortByIdgetClubByIdgetClubMembersById

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://strava.run.mcp.com.ai/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "strava": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://strava.run.mcp.com.ai/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

ai.com.mcp/strava MCP Server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

getStats

getLoggedInAthlete

getLoggedInAthleteStarredSegments

getEffortsBySegmentId

exploreSegments

getSegmentEffortById

getClubById

getClubMembersById

getClubAdminsById

getClubActivitiesById

getLoggedInAthleteClubs

getGearById

getRoutesByAthleteId

HAPI MCP – Headless API for Model Context Protocol

Key Features

How It Works

Visual Pipeline

Who Wins With HAPI

Your Stack, Already Wired

Demos

Documentation

FAQ

Get Started

Contributing

License

Install

Remote endpoint

Related servers