Strava Mcp

io.github.davidmosiah由 GitHub 账号 davidmosiah 发布v0.4.6更新于 Oct 24, 2026

Privacy-first MCP server for Strava activities, streams, routes and training.

已验证STDIO仅桌面位置与生活数据与分析

概览

AI 生成的概览

本地优先的 MCP 服务器,让助手以只读方式访问你的 Strava 活动、数据流、路线和训练摘要。

可以做什么
  • 检查配置、授权范围、隐私模式和缓存状态,获取授权链接或撤销访问
  • 读取运动员资料、心率与功率区间及汇总统计
  • 列出并查看活动、区间、逐秒数据流与序列,除非明确要求否则隐藏 GPS
  • 浏览路线、俱乐部和装备
  • 生成每日与每周训练摘要,包含负荷、强度和下周计划
  • 使用内置提示完成每日简报、每周耐力复盘和单个活动的数据流分析
适用场景
适合让助手基于你自己的 Strava 训练历史做分析,例如每周负荷、强度平衡、活动细节和路线背景,而无需手动复制 Strava 中的数字。它只读,面向个人耐力与表现回顾,不提供医疗或教练建议。
运行要求
需要 Node.js 20 或更高版本并以本地进程方式安装。需要一个 Strava API 应用,重定向地址为 STRAVA_CLIENT_ID 与 STRAVA_CLIENT_SECRET(或使用 setup 命令将其保存在本地配置文件)。需通过浏览器完成 OAuth 授权,令牌保存在本地。缓存、隐私模式和令牌路径为可选变量。
安装前请注意
需要你的 Strava OAuth 客户端密钥,并授予对活动(含私密活动)和个人资料的读取权限。GPS 坐标和路线几何默认隐藏,但可通过 include_gps 或 raw 模式暴露,如无需要请保持默认隐私模式。令牌保存在磁盘上,需妥善保护;复制到其他机器需手动操作。非官方项目,与 Strava 无关联,且不构成医疗建议。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Strava Mcp,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Strava MCP

Give your AI agent your Strava activities, streams, segments and routes — locally.
Local-first MCP server — tokens never leave your machine.

[npm version] [npm downloads] [License MIT] [Site]

[GitHub stars] [Built for MCP] [Hermes one-command setup] [Strava]

⚡ One-command install with Delx Wellness for Hermes: npx -y delx-wellness-hermes setup — preconfigures this connector and the other 8 in a dedicated Hermes profile.

Or wire it standalone into Claude Desktop / Cursor / ChatGPT Desktop — see the install section below.


HTTP (v2 stateless)

Default is stdio. Optional Streamable HTTP — no session id, JSON responses, loopback only:

bash
npx -y strava-mcp-unofficial --http# GET  http://127.0.0.1:3000/health# POST http://127.0.0.1:3000/mcp   (sessionless)

Env: STRAVA_MCP_HOST, STRAVA_MCP_PORT, STRAVA_MCP_TRANSPORT=http.

Local-first MCP server that connects AI agents to your Strava activities, routes, streams and training context.

Unofficial project. Not affiliated with, endorsed by or supported by Strava, Inc. Strava is a trademark of its respective owner. Use this only with your own Strava account and in line with Strava's API agreement.

Built by David Mosiah for people who use Claude, Cursor, Hermes, OpenClaw or other MCP-compatible agents to think about training, endurance and performance — without copy-pasting numbers from Strava.

Part of Delx Wellness, a registry of local-first wellness MCP connectors.

If this connector helps your agent workflow, please star the repo. Stars make the project easier for other AI builders to discover and help Delx keep shipping local-first wellness infrastructure.

Why this exists

Strava holds the long memory of your training — every ride, run, swim, segment, route and stream. But it lives behind an OAuth API with strict rate limits (200 req/15min, 2k/day per app) and GPS data that's privacy-sensitive by default.

This package does the OAuth dance locally, throttles under Strava's per-app limits, redacts GPS lat/lng unless you explicitly opt in, and exposes Strava through the Model Context Protocol. Any MCP-compatible agent gets your training context with one config snippet. Tokens never leave your machine.

Quickstart

From zero to your first agent call in about a minute. You only need a Strava app (create one here) with redirect URI http://127.0.0.1:3000/callback.

1. Paste your app's client id + secret (interactive, stored at ~/.strava-mcp/config.json with 0600):

bash
npx -y strava-mcp-unofficial setup

2. Authorize Strava. auth opens your browser; --no-open prints the URL so you can paste it yourself (handy on a headless box). Tokens are saved locally — the command never prints them:

console
$ npx -y strava-mcp-unofficial auth --no-openStrava MCP · Authorization
Open this URL manually:  https://www.strava.com/oauth/authorize?client_id=12345&redirect_uri=http%3A%2F%2F127.0.0.1%3A3000%2Fcallback&response_type=code&approval_prompt=auto&scope=read%2Cactivity%3Aread_all%2Cprofile%3Aread_all&state=aa38f29b
Steps  1. Approve access in the browser tab that opens.  2. Strava will redirect to the local callback.  3. Tokens are saved locally; this command never prints them.
Waiting for callback...

3. Verify you're ready — doctor confirms scopes and setup without calling Strava:

console
$ npx -y strava-mcp-unofficial doctorStrava MCP · DoctorStatus: READY ✓
Checks  ✓  Node.js >=20  ✓  Env vars  ✓  Local config  ✓  Automatic auth redirect  ✓  Token file  ✓  Token permissions  ✓  Refresh token  ✓  OAuth scopes  ·  Privacy mode  ·  Cache
Next steps  1. Ready. Add this MCP server to your agent and start with strava_daily_summary.

If OAuth scopes shows a ✗, re-run auth and approve activity:read_all profile:read_all read.

4. Make a first call — no live account required. Ask your agent to run strava_demo. It returns realistic, synthetic payloads (tagged is_demo: true) so you can wire prompts before connecting real data:

text
> Call strava_demo and summarize my week.
# Strava Demo
- **is_demo**: true- **recent_sessions**: 3- **load_classification**: moderate- **primary_signal**: Recent Strava load is manageable; use intent and consistency as the main lever.- **recommended_handoff**: exercise_catalog_recommend_session

Call it with response_format: "json" for the full shapes. The sample block mirrors strava_daily_summary, strava_training_context and strava_list_activities key-for-key — npm run test:demo-contract runs the real builders over fixtures/strava-activities.mjs and fails the build if the demo ever invents a field or omits one. Swap strava_demo for the real tool and the same shape arrives filled with your Strava data.

5. Wire it into your MCP client:

json
{  "mcpServers": {    "strava": {      "command": "npx",      "args": ["-y", "strava-mcp-unofficial"]    }  }}

For Claude Desktop, run setup --client claude and the snippet is written for you. For Hermes, see Hermes / remote setup below.

Try it with your agent

Three things to ask first:

text
Use strava_connection_status to check setup, then run strava_daily_summary.Tell me what my training context looks like in 5 lines.
text
Call strava_weekly_summary with response_format=json. Find my biggestload/intensity bottleneck and give me a next-week endurance plan.
text
Use the strava_activity_stream_investigator prompt for activity_id=<id>.Don't expose GPS unless I explicitly ask for it.

Data availability

This package uses the official Strava API v3. When this README says raw, it means the upstream Strava JSON for a supported endpoint — not continuous device telemetry.

DataAvailableNotes
Activities (runs, rides, swims, walks, workouts)✓All recorded activities
Activity details + zones + splits✓HR, power, cadence, elevation, gear
Activity streams (HR / cadence / watts / altitude)✓Per-second samples for the activity
GPS lat/lng streamsopt-inHidden by default; requires include_gps=true or raw mode
Athlete profile + zones + aggregate stats✓Authenticated athlete
Routes + clubs + gear✓Route geometry redacted in summary/structured modes
Live device telemetry / continuous HR—Not exposed by Strava's public API

Tools

Start with these:

  • strava_connection_status — verify local setup, scopes and readiness before calling Strava
  • strava_data_inventory — inventory supported data domains, scopes, privacy modes and recommended first calls without calling Strava APIs.
  • strava_daily_summary — latest activity, weekly load and intensity context for today
  • strava_weekly_summary — scorecard, comparison vs prior week, next-week training plan

Auth & diagnostics

  • strava_capabilities, strava_agent_manifest, strava_privacy_audit, strava_cache_status
  • strava_get_auth_url, strava_exchange_code, strava_revoke_access

Athlete & training

  • strava_get_athlete, strava_get_zones, strava_get_athlete_stats

Activities & streams

  • strava_list_activities, strava_get_activity, strava_get_activity_zones
  • strava_activity_series, strava_get_activity_streams — GPS lat/lng requires include_gps=true or raw mode

Routes & context

  • strava_list_routes, strava_get_route, strava_list_clubs, strava_get_gear

Prompts

  • strava_daily_training_director — practical daily training brief
  • strava_weekly_endurance_review — week comparison + next-week endurance plan
  • strava_activity_stream_investigator — investigate one activity using streams (GPS-aware)

Each accepts timezone (IANA, default UTC).

Resources

  • strava://capabilities, strava://agent-manifest
  • strava://athlete
  • strava://latest/activity
  • strava://summary/daily, strava://summary/weekly

Privacy & security

  • OAuth tokens are stored in ~/.strava-mcp/tokens.json with 0600 permissions and are never returned by tools.
  • Write/upload scopes are not requested by default — read-only by design.
  • GPS lat/lng and route geometry are recursively removed in summary and structured modes, and only included with explicit include_gps=true for stream calls or raw mode.
  • Structured mode otherwise preserves complete upstream physiological records and future Strava fields.
  • Activity after / before filters retain instant semantics when converted from timezone-aware ISO date-times to Strava epoch seconds; invalid ranges fail before HTTP.
  • Route geometry is also redacted unless raw mode is explicitly requested.
  • The MCP client never sees access or refresh tokens.
  • This is not medical advice. The server exposes user-authorized data for personal AI workflows, not diagnosis or training prescription.

Configuration

setup writes most of these into ~/.strava-mcp/config.json (0600). Manual env override is supported:

bash
STRAVA_CLIENT_ID=…STRAVA_CLIENT_SECRET=…STRAVA_REDIRECT_URI=http://127.0.0.1:3000/callback
# OptionalSTRAVA_SCOPES="read activity:read_all profile:read_all"STRAVA_PRIVACY_MODE=structured        # summary | structured | rawSTRAVA_CACHE=sqlite                   # no effect: authenticated responses are never cached

Hermes / remote setup

bash
npx -y strava-mcp-unofficial setup --client hermes --no-authnpx -y strava-mcp-unofficial auth                       # run locally if browser auth is needednpx -y strava-mcp-unofficial doctor --client hermeshermes mcp test strava

Hermes commonly exposes Strava tools with a prefix:

  • mcp_strava_strava_agent_manifest
  • mcp_strava_strava_connection_status
  • mcp_strava_strava_daily_summary
  • mcp_strava_strava_weekly_summary
  • mcp_strava_strava_get_activity_streams

After Hermes config changes, use /reload-mcp or hermes mcp test strava. Don't restart the gateway for normal data access.

If browser OAuth has to happen on a different machine than Hermes, run auth locally and copy ~/.strava-mcp/tokens.json to the server with chmod 600. The token must include activity:read_all profile:read_all read for activity history and streams.

Requirements

  • Node.js 20+
  • A Strava app with redirect URI http://127.0.0.1:3000/callback

Why these scopes:

  • read — public profile, routes and public Strava resources
  • activity:read_all — your activities, including private activities visible to your app
  • profile:read_all — fuller authenticated athlete profile fields

No write scope is requested by default.

Development

bash
git clone https://github.com/davidmosiah/strava-mcp.gitcd strava-mcpnpm installnpm testnpm run build

Test with MCP Inspector:

bash
npx @modelcontextprotocol/inspector node dist/index.js

Links

See also

The full Delx Wellness connector library:

One-command setup for Hermes — preconfigures every connector above plus wellness skills + onboarding: delx-wellness-hermes.

📧 Contact & Support

License

MIT — see LICENSE.

Disclaimer

This software is provided as-is. It is not a medical device, does not provide medical advice, and should not be used for diagnosis, treatment or training prescription. Always consult qualified professionals for medical or training concerns.

Skill or MCP

Same package, two doors. MCP registers tools on stdio/HTTP. The skill can drive the same tools through the CLI when the client has no MCP:

bash
npx -y strava-mcp-unofficial call strava_connection_status --json '{}'

Copy skill/SKILL.md into your agent skills dir.

Release migration

Before upgrading to 0.7.0, review the compatibility and migration notes.

来源:README.md,提交 bc328b3

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.4.6最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分