Strava MCP Bridge MCP server

strava-mcp-bridge

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 bootstrap directly.

strava-mcp-bridge fills that gap:

requests to https://mcp.strava.com/mcp.

1. You authorize the official Strava MCP once through Claude Code.
2. You explicitly run strava-mcp-bridge bootstrap.
3. The bridge migrates the authorized credential into its own Keychain item.
4. It maintains the rotating refresh-token chain and forwards approved MCP

1. Normal Codex/OpenCode use no longer reads or invokes Claude Code.

This is not a Strava REST API wrapper and does not provide shared credentials or bypass user authorization.

Choose The Right Path

Managed connector behavior varies by provider. Review its data path and terms before connecting fitness data.

Good Fit / Not A Fit

Use this bridge when all of these are true:

servers.

• You use Codex, OpenCode, or another client that can run local stdio MCP

subscription.

• You have access to Strava's official MCP through an eligible Strava

• You do not want to create and maintain a Strava developer app.
• You prefer local credential custody and conservative data controls.
• You are on an Apple Silicon Mac.

Use another path when any of these are true:

Shortened. The full README is on GitHub.