millerchou-strava-bridgeCAUTION
Use Strava's official MCP from Codex and OpenCode without creating a developer app. Local macOS Keychain and privacy-first streams.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://github.com/millerchou/strava-mcp-bridge/actions/workflows/ci.yml) [](LICENSE)
Use Strava's official MCP from Codex, OpenCode, and other local stdio MCP clients without creating your own Strava developer app.
The bridge runs locally on Apple Silicon macOS. Its OAuth credential is kept in macOS Keychain, large activity streams stay in local files, and GPS/location data is blocked before it can enter the AI context.
What It Enables
Once connected, a local coding agent can use Strava data as part of a real project workflow instead of working from copied summaries or synthetic data.
You: Pull my new rides since the local watermark and rebuild my training dashboard. Codex: 3 new rides found through the official Strava MCP full activity streams saved locally, omitted from model context training summary and fitness chart rebuilt no GPS, location, or polyline fields returned to the conversation
Other example tasks:
- "Compare heart-rate load across my rides this week."
- "Fetch the non-location streams for this activity and update my analysis."
- "Use my latest cycling data to refresh the PMC/TRIMP dashboard in this repo."
The bridge supplies the safe Strava connection. Your agent can then combine the result with local scripts, notebooks, dashboards, or training-analysis code.
Why This Exists
Strava publishes an official MCP connector, but its documented first-time authorization flow currently targets Claude clients. Codex supports MCP, yet it cannot currently complete this Strava OAuth boot
f3778b0806ccOBSERVED · 2026-10-14Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add strava-mcp-bridge -- npx -y [email protected]
Exposed tools (3)
3 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
get_activity_streams | read | allowed with policy guard |
get_athlete_profile | read | not allowed |
health | read | safe |
Trust audit
CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | FAIL |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (2 observation(s))
- Network
- none-observed
- Shell
- declared (3 observation(s))
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (5)
- `keychain-access-denied`: macOS refused the Keychain access request (a denied
B -->|"read / rotate credential"| K["macOS Keychain"]
| `strava-mcp-bridge doctor` | Read-only platform/helper/credential check |
Tests use local mocks. They do not contact Strava or read Keychain.
Do not include access tokens, refresh tokens, Keychain dumps, or activity data in
Gates applied: no_behavioural_pass.
f3778b0806ccfull audit observations/trust-audit/mcp-server/millerchou__strava-mcp-bridge.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-14 | f3778b0806cc | CAUTION | B | 89 | first audit |
Questions
What is the millerchou-strava-bridge MCP server?
Use Strava's official MCP from Codex and OpenCode without creating a developer app. Local macOS Keychain and privacy-first streams.
What tools does millerchou-strava-bridge expose?
3 in total: 3 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is millerchou-strava-bridge safe to connect to an agent?
With care. The audit graded it B (89/100) and found 5 things worth knowing before you trust this server, listed below with the exact line each was found on.
What credentials does millerchou-strava-bridge need?
It reads STRAVA_MCP_ACCESS_TOKEN, STRAVA_MCP_ALLOW_KEYCHAIN_HELPER_OVERRIDE, STRAVA_MCP_ALLOW_TOKEN_ENDPOINT_OVERRIDE, STRAVA_MCP_AUTH, STRAVA_MCP_BRIDGE_KEYCHAIN_SERVICE, STRAVA_MCP_KEYCHAIN_BACKEND, STRAVA_MCP_KEYCHAIN_HELPER, STRAVA_MCP_KEYCHAIN_TIMEOUT_MS, STRAVA_MCP_OAUTH_TIMEOUT_MS and STRAVA_MCP_TOKEN_ENDPOINT from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does millerchou-strava-bridge run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as strava-mcp-bridge at 0.1.1.
How current is this page?
The grade is for one exact copy of the source (f3778b0806cc), read on 2026-10-14. The repository is watched and re-audited when it changes.