Articles in this section

Build on COROS MCP

What is this?

Build applications that connect to COROS user data through the Model Context Protocol (MCP) with OAuth 2.0 authentication. No application or approval required. Implement OAuth 2.0 in your app, and your users can connect their COROS account and grant access to their own data.

How it works

  1. You implement the OAuth 2.0 authorization flow in your application pointing to the COROS MCP endpoint.
  2. Your user clicks "Connect COROS" and logs into their COROS account.
  3. The user authorizes your app to access their training data.
  4. Your app reads training data and writes workout plans through the MCP.

What you can build

  • AI coaching apps that analyze training and prescribe workouts
  • Training dashboards and analytics platforms
  • Health and wellness integrations
  • Personalized training plan generators
  • Recovery and readiness tools

Technical Requirements

  • Your application must support the OAuth 2.0 authorization flow
  • MCP server endpoint: https://mcp.coros.com/mcp
  • All data access is scoped to the authorizing user only (single-user)
  • Full MCP documentation: COROS MCP GitHub

For implementation details on the OAuth 2.0 authorization flow, refer to the official specification: https://oauth.net/2/

COROS uses the standard OAuth 2.0 protocol. Any OAuth 2.0 client library in your language of choice will work.

Getting Started

  1. Step 1: Implement the OAuth 2.0 authorization flow in your application pointing to the COROS MCP endpoint.
  2. Step 2: Add a "Connect COROS" button in your app. When a user clicks it, they log in and authorize your app to access their data.
  3. Step 3: Start building. Your app can immediately read training data and write workout plans for that user.

Available data fields

Same fields as Tier 1 (see Connect COROS to Your AI). All read operations plus training plan and workout write capabilities.

Limitations

  • Single-user access only (each user authorizes their own data)
  • No webhook push notifications (your app polls the MCP)
  • No GPX route import/export
  • No two-way activity sync (COROS to your platform requires Partner API)

Need more?

If your platform requires webhook push notifications, two-way sync, or GPX route support, you can apply for full Partner API access.

Was this article helpful?
0 out of 0 found this helpful