You can connect your COROS account to AI tools like Claude and ChatGPT, to ask direct questions about your training' build your own workouts, training plans, and dashboards; and gain deeper insights about your performance data. This guide covers how it works, what you're able to do, and how to set it up.
Why connect?
You can connect your COROS account to compatible AI tools and ask questions about your training, health, recovery, and more - and even build workouts and training plans that sync to your COROS library.
With your COROS account connected, services like Claude and ChatGPT can access your actual numbers and respond accordingly. Ask something like:
- "I have a race in six weeks. Am I ready?"
- "Build me a training plan for my 10k race coming up in three months."
- "How has my resting heart rate changed since I started altitude training?"
Requirements
Here's what you need to start:
- A COROS account. If you use the COROS app, you already have one.
- Recommended: Paid subscription to ChatGPT Plus or Claude Pro, or any AI platform that supports plug-ins or connectors. (While free accounts support the connectors or plug-ins, they are usually restricted to one custom connector, and using the tool may quickly consume your usage limits.)
How to Set Up
ChatGPT
1. Open ChatGPT and click your account profile in the bottom corner to open Settings
2. Select "Plugins" from the sidebar
3. Search for "COROS" and click the plus icon to connect
5. Authorize and log into your COROS account
Claude (Desktop app)
1. Open Claude and select the gear icon for Settings
2. Go to Connectors → select the Discover tab
3. Search for "COROS" and click Connect
4. Authorize and log into your COROS account
Gemini
While Gemini currently does not support custom MCP connectors through its standard chat interface, you can still connect via the Gemini CLI. Follow Google's setup guide here and use the COROS MCP link: https://mcp.coros.com/mcp.
Once you have authorized the connection, confirm it's working properly by asking the AI a question about your COROS data. For example: "Show me my workouts from the past two weeks." If it returns your actual data, the connection is live.
What Data it Can See
As of September 2026 update, the COROS MCP can query the following data:
-
Activity data
- Activity records
- Lap and segment data for workouts
- Workout feedback and training notes
- .FIT files, including GPS tracks (capped at 50 file requests per day)
-
Workouts and Training Plans (available September 21, 2026)
- Create road running, trail running, and cycling workouts that sync to your COROS workout library
- Create road running, trail running, and cycling training plans that sync to your COROS training plan library
- Make changes to workouts or training plans via AI, and sync those changes to COROS
-
Health and daily data
- Menstrual cycle data
- Daily steps, calories, workout duration, and weekly Training Load
- Sleep data
- Daily heart rate, HRV, stress, Wellness Checks, and resting heart rate
-
Fitness data
- Current training plan and training calendar
- VO2 Max, Running Fitness, race prediction times, and recovery status
- Threshold pace, and pace zones
- User profile and connected device information
Some example prompts include:
- "Build me a dashboard that compares my multi-sport training from 2025 to 2026."
- "I'm tired from a long travel day. What's an easier workout I can do today?"
- "Build me a training plan for my half marathon coming up in five weeks."
- "How has my HRV responded around hard training blocks this month?"
Create Training Plans and Workouts (available September 21, 2026)
Ask your AI to build a workout or training plan based on your fitness and goals, and it can sync directly to your COROS library. Training plans must be between 4 and 16 weeks long.
- Supported activity types: You can build plans and workouts for road running, trail running, and cycling. Support for more activity types are coming soon.
- Where they sync: If you don't choose a start date, your new training plan or workout will sync to your COROS Training Plan Library / COROS Workout Library (found in the Profile page).
- Edit and delete: After creating a plan or workout, you can ask your AI tool to make changes, and these will sync to COROS. However, you are not able to delete a plan or workout with AI; this must be done manually in the COROS app.
- Choose a start date: You can ask your AI tool to add the workout or plan to your COROS Training Calendar. The start date can be anytime from today to 14 days from now.
- Search: Use your AI tool to look up details for any training plan or workout in your COROS library.
Tips for Deeper Analyses
For deeper workout analysis, you will need to request .FIT files through the MCP. The following analyses are not available in a basic query, but require pulling the .FIT files first so the MCP has the raw data to analyze:
- GPS information: The AI cannot describe a route, compare elevation profiles between two runs on the same loop, or analyze terrain from a basic query alone.
- Interval and lap analysis: While the AI can reference your lap summary for a workout, it won't be able to analyze split-by-split details if you are trying to compare across workouts or identify trends.
- Cycling power: Power data is not part of the standard query set, even when a power meter is paired and recording. This means a power curve and FTP estimation is not possible.
.FIT file requests in these connections are capped at 50 files per calendar day, but you can manually export specific .FIT files (or your entire activity history) from t.coros.com and upload the files to your AI as a workaround. See our guide here on how to export your historical activity data.
Troubleshooting
Confirm your COROS account works normally at t.coros.com first. If you are unable to log in there, the MCP connection will not work either. Try using the password reset option at t.coros.com to reset your COROS credentials. If that doesn't work, double check that you are logging in with the correct email address by going to your COROS app > Profile page > Settings > Account Management > Email.
This usually means your AI platform requires a paid plan for this feature. Free tiers often don't support MCP connections. We recommend using Claude Pro or ChatGPT plus.
ChatGPT Plus, Claude Pro, and Cursor all support MCP connections. While Gemini's standard chat interface does not currently support custom MCP connectors, the Gemini CLI does. Use the COROS MCP link from Step 1 above as the server URL if setting up with Gemini CLI.
This generally points to a temporary service issue on the API side rather than your setup. Try again after a few minutes. If it persists, confirm your connector permissions are still active in your AI platform's settings.
Yes. Once connected, the MCP queries data across every device registered to your account, not just the one most recently synced.
No. The MCP only queries your own activity data. It cannot read data belonging to another athlete or to an athlete you coach. The same permission structure that governs coach and athlete visibility in Training Hub applies here. You can manage your athlete and coach settings by going to t.coros.com, selecting your profile picture near the bottom left corner, and scrolling down to Privacy Settings.
Yes, most platforms allow you to customize which tools are accessible. Customization varies by platform. For example, in Claude Pro, go to Settings → Connectors → COROS MCP from the desktop app, and here you can specify which individual tools have full access, are approval-required, or blocked.
The MCP does not introduce new privacy risk beyond what already exists when using your COROS account and AI platform independently. The MCP is not a backdoor, nor does it bypass either platform's existing authentication or privacy controls. Data retention after a query is governed by the AI platform's own policies. See our COROS Privacy Policy and your AI platform's security documentation for specifics.
Privacy and Security
Using the COROS MCP does not create any new security or privacy risks beyond those that already exist when using your COROS account and your chosen AI platform separately. It is a structured connection layer that allows the two systems to communicate in a controlled, permission-based way. The same standards of account security, data protection, and platform privacy continue to apply.
Your COROS data remains governed by COROS privacy and security protections, and your AI interactions remain governed by the policies, permissions, and settings of the AI platform you choose to use. In other words, connecting through MCP does not change the underlying rules around how your data is protected - it simply allows approved data and actions to move between systems in a more useful and efficient way.
Access is only granted through explicit user authorization. You decide whether to connect your account, and the connection only operates within the permissions you approve. Depending on the capabilities enabled, that may include both read access to analyze training data and write access for supported actions within the connected experience. Those permissions are not open-ended; they are limited to the scope of the integration and the controls provided by COROS and the AI platform.
Importantly, this integration is not a backdoor into your account, and it does not bypass existing authentication, privacy controls, or security safeguards. It uses the same identity, authorization, and protection principles that already apply across secure connected services.
In practical terms, users should think of this as a secure extension of the tools they already use: your data protections remain in place, your permissions still matter, and you remain in control of what is connected and what actions are allowed.