Strava MCP Broker
Provides tools for interacting with the Strava API, including athlete data, activities, routes, segments, clubs, and gear management.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Strava MCP Brokershow my latest 5 activities"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Strava MCP Broker
An HTTP broker that exposes the r-huijts/strava-mcp server over MCP Streamable HTTP, with per-user Strava OAuth2. Each user brings their own Strava API credentials — no shared app secrets needed.
Quick Start (Hosted Version)
A public instance is running at strava-mcp.julian-bruegger.ch. No setup required.
Create a Strava API app at strava.com/settings/api
Set Authorization Callback Domain to
strava-mcp.julian-bruegger.ch
Enter your Strava Client ID and Client Secret, then click Connect with Strava
Authorize on Strava — you'll receive your personal MCP endpoint URL
Add the endpoint to Claude:
Claude.ai: Settings → Integrations → Add MCP server → paste the URL
Claude Desktop: Add to your
claude_desktop_config.json(see below)
Manage your sessions anytime at strava-mcp.julian-bruegger.ch/dashboard
Related MCP server: Strava MCP Server
Self-Hosted Version
Host your own instance with Docker and Cloudflare Tunnel.
Architecture
Claude.ai / Claude Desktop
│ HTTPS (MCP Streamable HTTP)
▼
Cloudflare Tunnel
│
▼
Docker: strava-mcp-broker (Express server, port 3000)
│ stdio JSON-RPC
▼
Docker: @r-huijts/strava-mcp-server (child process per session)
│ HTTPS
▼
Strava API v3Prerequisites
A server with Docker + Docker Compose (e.g. Proxmox, VPS, Raspberry Pi)
A domain managed by Cloudflare (free plan is fine)
A free Cloudflare Zero Trust account (one.dash.cloudflare.com)
Step 1 — Set Up Cloudflare Tunnel
Log in to one.dash.cloudflare.com
Go to Networks → Tunnels → Create a tunnel
Choose Cloudflared as the connector type
Name your tunnel (e.g.
strava-mcp)On the "Install connector" page, choose Docker — copy the tunnel token
In Public Hostname, add a route:
Subdomain:
strava-mcpDomain:
yourdomain.comService:
http://strava-mcp:3000(Docker service name on the internal network)
Save the tunnel
Step 2 — Configure and Deploy
git clone https://github.com/julianbruegger/strava-mcp-broker
cd strava-mcp-broker
cp env.example .envEdit .env:
PUBLIC_URL=https://strava-mcp.yourdomain.com
CLOUDFLARE_TUNNEL_TOKEN=eyJhIjoiM... # from Step 1
SESSION_SECRET=<run: openssl rand -hex 32>Deploy:
docker compose up -d --buildCheck logs:
docker compose logs -fYou should see:
strava-mcp-broker | Strava MCP broker running on http://0.0.0.0:3000
strava-mcp-broker | Public URL: https://strava-mcp.yourdomain.com
strava-mcp-tunnel | Registered tunnel connectionStep 3 — Connect Your Strava Account
Go to strava.com/settings/api and create an app
Set Authorization Callback Domain to your tunnel domain (e.g.
strava-mcp.yourdomain.com)
Open your broker URL in a browser
Enter your Client ID and Client Secret, then click Connect with Strava
Authorize on Strava — you'll receive your personal MCP endpoint URL
Connect to Claude
Option A — Claude.ai (recommended)
Go to Settings → Integrations → Add MCP server and paste your endpoint URL:
https://strava-mcp.yourdomain.com/mcp?session=YOUR_SESSION_TOKENOption B — Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"strava": {
"command": "npx",
"args": [
"mcp-remote",
"https://strava-mcp.yourdomain.com/mcp?session=YOUR_SESSION_TOKEN"
]
}
}
}Restart Claude Desktop. You'll see the Strava tools available.
Available Tools (25+)
Category | Tools |
Athlete |
|
Activities |
|
Routes |
|
Segments |
|
Clubs |
|
Gear |
|
Connection |
|
See SKILL.md for detailed tool descriptions and usage guidelines.
Dashboard
Each user gets a dashboard at /dashboard to manage their sessions:
View all connected sessions
See MCP endpoint URLs
Delete individual sessions
Delete all data at once
The dashboard is protected by a signed cookie set during Strava OAuth — no extra login needed.
Maintenance (Self-Hosted)
Update to latest strava-mcp-server version
docker compose build --no-cache
docker compose up -dBackup tokens
docker cp strava-mcp-broker:/data/tokens.db ./tokens-backup.dbSecurity Notes
Each user provides their own Strava API credentials — the broker stores no shared secrets
Session tokens are random 256-bit hex strings — treat them like passwords
Tokens are stored in SQLite at
/data/tokens.db(mounted volume) — back it upAccess tokens are refreshed automatically (Strava tokens expire every 6 hours)
The
/mcpendpoint is rate-limited (60 req/min per IP) and requires a valid session tokenDashboard auth uses HMAC-signed cookies (30-day expiry, HttpOnly, SameSite)
Cloudflare Tunnel handles TLS — no certificates needed on the server
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/julianbruegger/strava-mcp-broker'
If you have feedback or need assistance with the MCP directory API, please join our Discord server