Connecting Stride to Claude (MCP)
Stride runs a Model Context Protocol (MCP) server, so an AI assistant such as Claude can read your training data and write to your calendar directly. Once it is connected you can ask about your rides, runs and swims in ordinary language, and the answer comes from the same analysis that powers Stride's AI insights rather than from a summary you have pasted into a chat.
This is separate from the AI inside Stride. The Training Planner and AI insights work on their own with no setup. The MCP server is for bringing your training into a conversation you are already having somewhere else.
Before you start#
- An active Stride trial or subscription. The connection completes without one, but every request that reads or writes data is refused until your subscription is active.
- A client that supports remote MCP servers. Claude, Claude Code, ChatGPT and most AI coding tools do. Adding a custom connector needs a paid plan on some of them.
- Your Stride login. You sign in to Stride as part of connecting, and approve the request there.
Garmin data#
Garmin's developer terms do not allow Stride to share Garmin data with other apps, including AI assistants. So sessions recorded through Garmin Connect do not appear in what the assistant can read, or appear only as the plan if you planned them in Stride, and it cannot open them in detail or download their files. Garmin's wellness, sleep and cycle readings are left out too.
Your training load, power curves and thresholds are Stride's own calculations, so they still include those sessions. The assistant tells you when something has been left out. Everything is still in the Stride app, and Stride's own AI uses all of it. Files you upload to Stride yourself are not affected.
Connect Claude#
The steps are the same in the Claude web app and the Claude desktop app.
- Open Settings, then Connectors.
- Choose Add custom connector.
- Name it Stride and enter the server URL
https://api.stride.is/mcp. - Choose Connect. A Stride window opens. Sign in if you need to, then approve the request.
- Claude returns to the connector list and shows Stride's tools. You are ready to ask it something.
No API key needed
You do not need a key or token for Claude or other AI assistants. The client registers itself and you sign in on Stride's own page, so your password is never given to the AI client. Stride's personal access tokens are for the REST API only and will not work as an MCP connection.
Connect Claude Code#
In a terminal, run claude mcp add --transport http stride https://api.stride.is/mcp. Then start Claude Code, run /mcp and choose to authenticate. Your browser opens for the same Stride sign-in, and the connection is remembered afterwards.
Other clients#
Anything that speaks remote MCP over HTTP works the same way. Point it at https://api.stride.is/mcp and complete the sign-in it opens. For your own scripts, use the Stride API instead.
What it can do#
Read your training#
- List your activities across any date window, completed and planned, so it can look forwards as well as back.
- Open the full analysis of a session: detected intervals and how well you hit them, W′ balance, aerobic decoupling, Weighted Power, pacing splits, laps and climbs, time in zones, route weather with the wind split into headwind, tailwind and crosswind, your RPE and comments, and the AI insight Stride already wrote about it.
- Fetch the workout that was prescribed for a session, or a short-lived link to the original recorded file.
- Read your metrics at a date or across a range: FTP, Critical Power and W′, weight, threshold and maximum heart rate, threshold pace, and wellness values such as HRV, recovery score and sleep score.
- Pull your power curve over a period, compared with an earlier window, including durability curves that show what you can still produce deep into a ride.
- Check your profile, including which integrations are connected and your subscription status.
Read the day around the training#
A day-by-day view returns one row per date with everything Stride holds against that date: races, holidays, illness, injury, rest days and notes, that day's wellness numbers, the night's sleep, your cycle position, and the sessions themselves. It is what makes questions about context answerable, not just questions about a file.
Search the workout library#
It can search the workout library in plain language, filter by tag, sport, creator and length, and open any workout with its intervals. That covers Stride's own workouts plus yours and your teams'.
Write to your calendar#
The connection is not read-only. It can schedule a planned session, update or delete one, save a new structured workout to your library, and record a metric such as a new FTP or weight. When it plans a structured session it saves the workout first and attaches it, so the steps reach your head unit like any other planned workout. A planned session without a workout is a placeholder with no steps.
Read the permission prompt
Most clients ask before running a tool for the first time, and it is worth reading what you approve. These writes are real: a deleted session is gone from your calendar, and a recorded FTP changes the zones and targets of your future workouts.
Coaches and teams#
If you are a coach or team admin, the assistant can list your teams and their athletes, then use any of the tools above for one of those athletes. A role on a team also covers the groups below it. Ask about an athlete by name and it looks the right person up rather than guessing. Coaches' and team admins' own training is only visible if they have chosen to train with the team.
Things to ask#
- "How did yesterday's threshold intervals compare with the same session a month ago?"
- "Look at my last six weeks and tell me honestly whether my endurance is improving or I am just riding more."
- "I felt awful on Tuesday's ride. What else was going on that week?"
- "Where does my power curve sit against three months ago, and how does it hold up after 2,000 kJ?"
- "Find me a 60 minute sweet spot session and put it on Thursday."
- "I tested at 285 watts this morning. Record it."
- "Go through my squad's week and tell me which three riders need a conversation."
Getting better answers#
- Give it a window. "Since the start of June" or "my last four weeks" is far more useful than "my training", and keeps the answer quick.
- Name what you care about. Asking about the intervals, the zones or the weather gets a sharper answer than asking for everything at once.
- Ask it to check before it writes. Ask it to show you the plan first and apply it once you agree.
- Wait for your history to import. If you have only just joined, let the first sync finish, otherwise the assistant is reasoning about a fraction of your training.
Permissions and privacy#
- The connection is tied to your Stride account. It can reach your own data and the athletes on teams where you are a coach or team admin. Any other athlete is refused, whatever the assistant is asked.
- You sign in on Stride's own page, so the AI client never sees your password.
- To end a connection, go to Settings > API in Stride on the web, find it under Connected apps and choose Disconnect. Removing the connector in your AI client also stops it. Either way, access ends within an hour.
- Each sign-in lasts about three months. After that your client asks you to connect again.
- Whatever the assistant reads is then handled under your AI provider's terms, not Stride's, so treat it as you would anything else you paste into a chat.
More on how your data is stored and used is in Data & Privacy.
Troubleshooting#
- The connector will not add. Check the URL is exactly
https://api.stride.is/mcp, with no trailing slash and no www. - It says it is not authorised. The sign-in has expired. Remove the connector and add it again, or reauthenticate from your client's connector settings.
- The tools are listed but every one fails. This is almost always the subscription check. A lapsed trial or subscription still connects and lists tools, so the first request can explain itself.
- It cannot see an athlete. You can only reach athletes on a team where you are a coach or team admin, or a group below one. Athletes you coach outside Stride are not reachable this way.
- An activity is missing. If it was recorded on a Garmin and synced through Garmin Connect, it is left out under Garmin's terms (see Garmin data above). Otherwise it has probably not synced to Stride yet, so check your integrations.
Still stuck?
Email support@stride.is with the client you are using and what it said, and roughly when you tried, so we can find the request.