How to connect Coros to Claude

Once the hub is connected, Claude can see whatever the Coros app hands to Apple Health or Health Connect: your workouts, distance, pace, heart rate, and sleep. That is enough for it to line up a run against your heart rate or check how sleep held up after a hard week.

What Claude cannot see is the layer Coros keeps for itself. Training Load, EvoLab fitness and freshness scores, and similar Coros-proprietary readings are computed inside the Coros app and often do not export to the phone's health hub. If a metric never reaches Apple Health or Health Connect, Wellness Project has no way to read it, and neither does Claude.

Yes. Coros launched an official MCP server in 2026, and its setup guide has Claude users add mcp.coros.com/mcp as a custom connector. That path carries Coros data and nothing else.

Wellness Project is the path for the whole picture. The Coros app writes workouts, heart rate and sleep into Apple Health or Health Connect, Wellness Project reads that hub and structures it into a training log next to your nutrition, injuries, labs and sleep from every other source, and one Wellness Project MCP connection serves all of it to Claude. Once the Coros app is writing to the hub and Wellness Project is reading it, that connection carries every new run automatically, with nothing to rebuild each week.

راجع Coros connect guide أو اربط Coros بـ ChatGPT.

Three links carry your training data from watch to chat: Coros into the hub, Wellness Project onto the hub, and Claude onto Wellness Project. Set each one up once.

الأسئلة التي تستحق أن تُطرح هي تلك التي لا تستطيع شاشة Coros واحدة الإجابة عنها، لأنها تمتد عبر أسابيع بدلًا من نشاط واحد.

Try "How has my easy-pace heart rate trended over this training block?" or "Did my long-run pace hold up as my weekly mileage went up?" or "Which week this training cycle had the biggest gap between planned and actual mileage?" Claude answers from your structured Coros history, not a screenshot of today's run.