Stride MCP
Stride connects your Strava account to AI so you can ask real questions about your training and get answers grounded in your actual runs, not generic advice.
Works with Claude.ai and ChatGPT. Free to connect. Use your own Strava API application.
Strava tracks splits, heart rate, shoe mileage, and how your volume shifts week to week. It does not tell you what any of it means for your next month of training.
Stride bridges that gap. It connects Strava to Claude or ChatGPT using an open standard called MCP (Model Context Protocol). Once connected, your AI can pull your data for any activity or timeframe and talk it through with you.
Not canned summaries. Not generic plans. Your trends and your questions.
Each question drives fresh calls into Strava so answers reflect recent runs and totals, not a stale export from last month.
Add Stride as a connector, then chat in the assistant you already pay for. No extra athlete app required for MCP setup.
You create your own Strava API application. That avoids shared developer quotas and keeps usage under your Strava app.
In Strava settings, create a free API application. You receive a Client ID and Client Secret. Set the authorization callback domain to match app.runstri.de as documented in setup.
Sign in with Google, paste your Strava credentials, and complete OAuth. You receive a personal MCP URL for Claude or ChatGPT.
In Claude, open your Project, add the MCP URL as a connector, and add the Stride skill to project instructions. Start chatting.
Real runners ask messy questions. Here is what it looks like when the model can read Strava.
Stride exposes specialised tools so Claude or ChatGPT can fetch profile, activities, trends, gear, segments, and social context on demand.
Name, locale, sport prefs, and basics so answers stay personal.
Totals and standout efforts for historical context.
Feed of runs and rides with pace, distance, and elevation.
Deep dive on one session including HR and gear when present.
Second-by-second or per-lap views for structured workouts.
Time in HR or power zones for a session.
Rolling weeks compared for load and intensity.
This week vs last week, month vs month, year vs year.
Best efforts surfaced from history.
Find sessions by keyword, type, or date range.
Shoes and bikes with accumulated distance.
Starred segments, efforts over time, saved routes.
Social context tied to an activity when available.
Paste the Stride skill into Project instructions so Claude fetches live data before guessing, chains tools when helpful, and answers like a coach: lead with the insight, cite real dates and activity names, finish with one sharp follow-up question.
Open or download the skill file and add it alongside your MCP connector in the same Project.
Claude.ai typically needs a paid plan (for example Claude Pro) to use MCP connectors in Projects. ChatGPT often needs Plus or higher for similar integrations. Check current Anthropic and OpenAI pricing. Claude is usually the smoother fit for Stride MCP today.
Stride stores your Strava API credentials and tokens (encrypted) so the connector can run. Live activity details flow through to your AI session when you ask questions; we do not build a separate workout archive like the full Stride coaching app.
Strava limits how many athletes can connect to a single API application. With your own Client ID and Secret, your quota is isolated from everyone else. Stride MCP is built for that model.
If your device syncs activities into Strava, that data is available to Stride MCP wherever Strava exposes it through the API.
The same tools cover rides, segments, gear, and training load. Coaching tone can span running and cycling.
Connecting through app.runstri.de is free on our side. You pay Claude or ChatGPT according to your subscription.
Yes. Your MCP URL can be added wherever the client supports it. Exact setup steps differ by product.
Budget about ten minutes: Strava account, free Strava API app, then Claude or ChatGPT with your MCP URL.
Connect your Strava →