Strava for agents
Other. MCP servers, the command line and skills for connecting an agent to Strava.
- Official server
- 1 server
- Sourced servers by others
- 7
- Command line
- none curated
- Vendor skills
- none
Official server
The MCP Registry does not list Strava's own server, but its owner names its address on a page of its own, at a domain we curate for Strava: on those two proofs it is the system's official server here. Beyond that we only ask it each night, with no credential, what it answers.
https://mcp.strava.com/mcpnamed on the owner's page, read . Asked with no credential on , it refused a client with no credential.
How it is reached
As Strava's vendor states it, read from its own page on the day given.
- Through its API. Each user signs in to their own account. An app may have 10 users before the vendor reviews it. The vendor's page, read .
Its terms, for an agent
Clauses of Strava's terms that bear on an agent's use, each the page's own words, which a person chose and a nightly check looks for on the page. They are the vendor's words, not legal advice and not all of the terms: read the page. See how terms are checked.
Use with AI · §5.3 · in effect from The page says: “in connection with the development, training, evaluation, or operation of any AI Application”
The page, read ; the words were on it .
Aggregators and relays · §5.16 · in effect from The page says: “operate any MCP Server, agent-mediated interface, or analogous mechanism that exposes the Strava API Materials”
The page, read ; the words were on it .
Servers by other publishers
7 servers for Strava that name a public repository or a package, or whose tools we could read. Anyone can publish one, and we have not read their code: check the publisher and the source before giving one a credential.
In this order: live servers before deprecated ones, first-party first, a known vulnerability last, then more downloads, then a more recent push, then by name. There is no score, and the number of tools is not part of the order: fewer is not better. Tools are what a server listed to a client with no credential, or what its package listed when run with no network, downloads are from npm and pypistats, the last push from GitHub and vulnerabilities from OSV; a server's own page has the day each was read, and "not read" means we have no figure, not that there is none. See how this directory is made.
| Server | Publisher | Reach | Tools | Downloads a week | Last push | Vulnerabilities |
|---|---|---|---|---|---|---|
| io.github.davidmosiah/strava-mcp | Sourced | npm | not read | 170 | not read | none known |
| io.github.r-huijts/strava-mcp | Sourced | npm | not read | 71 | not read | none known |
Strava Training MCPio.github.ArjanLig/strava-mcp | Sourced | PyPI | not read | 56 | not read | none known |
Strava MCP Bridgeio.github.millerchou/strava-mcp-bridge | Sourced | npm | not read | 35 | not read | none known |
HAPI Strava MCP Serverai.com.mcp/strava | Sourced | remote | asks to sign in | not read | not read | not checked |
Strava MCP Server and API by Cotletdev.cotlet/strava | Sourced | remote | asks to sign in | not read | not read | not checked |
| io.github.ljcl/strava-mcp | Sourced | Container image | not read | not read | not read | not checked |
Listed only
1 more server in the registry for Strava with no repository and no package named. Nothing else is known about them, so they have no page here.
training.stats/garmin
Changes for Strava
None in the last 30 days. The log began on , and nothing older was recorded.
A change is a difference between two readings of public records, not a review. Strava in the log · How the log is made · Strava's Atom feed
A server is listed for Strava when we have named it as the system's official server, when its registry title or the last part of its registry name names Strava as whole words, or when it is published at Strava's own domain. See how this directory is made.
Built from agent catalog version 2026-11-18.1 of , from the MCP Registry as read on . A listing here is not an endorsement: anyone can publish a server, and we have not read its code. Names, descriptions and addresses are the publisher's own. See how this directory is made, and tell us about a wrong entry through the contact page.