Connect Claude to COROS: Read Training Data and Control Workout Changes

COROS offers an official MCP connection for Claude. Its current documentation describes reading training and health records and saving supported workouts or training plans to COROS. This is a vendor-operated connector, rather than a phone health-store workaround or an unverified community integration. Check the available tools after connecting: advice and an account change are different actions. COROS connection overview, checked September 30, 2026.

We make coach steve, an AI running coach you can text. We recommend it for goal-led support that fits an actual week. This article explains the documented Claude–COROS workflow; it does not claim a coach steve COROS integration or an authenticated test of these tools.

Start with the official connection

COROS's September guide directs Claude desktop users to Settings → Connectors → Discover → COROS → Connect, then COROS login and authorization. If using a custom connector instead, COROS publishes the server at mcp.coros.com/mcp. Use the vendor's link, not an endpoint copied from an unrelated tutorial. COROS's Claude setup guide, official endpoint and setup history.

Claude's own documentation makes custom remote connectors available across its plans, with one custom connector on Free. Team and Enterprise setup also involves organization controls. COROS recommends a paid AI subscription, but that recommendation is not proof that Claude universally requires Pro for custom MCP. Usage limits still matter. Claude connector eligibility.

Begin with a small read request: ask for one known activity, its date and source. Compare the result with the COROS app. A successful login is only the first step; the right account must contain synced records, and Claude must actually use the connector rather than answer from general knowledge.

What can the connector read?

COROS documents workout summaries, lap data, notes, daily sleep and health measures, training load and fitness assessments. Its update history includes FIT retrieval for GPS and detailed activity records, plus sleep HRV and stress time series. These are richer routes than assuming the same fields transfer through Apple Health. COROS MCP update history.

Preserve the difference between recorded data, COROS's assessments and Claude's explanation. A retrieved race prediction is a COROS estimate; a model discussing it has not independently validated race readiness. An empty recovery field should stay missing instead of becoming an invented score.

Choose the smallest reading scope that answers your question. A comparison of two interval sessions does not ordinarily require profile details or menstrual-cycle records. COROS's guide says Claude Pro connector settings can allow individual tools, require approval or block them. Review those controls before granting broader access. COROS's tool-permission guidance.

A library workout is not the workout on Thursday

The official COROS repository distinguishes reusable library templates, standalone dated workouts and workouts inside an execution plan. Editing a template leaves copies already scheduled unchanged. A standalone scheduled copy has its own editing tool; plan workouts use the plan update route. Plan updates replace submitted days' full workout contents. COROS's official tool definitions.

This is the most useful distinction to understand before enabling writes. If you ask to shorten Thursday's session and Claude edits the reusable template, Thursday may still contain the original session. If it creates another workout to imitate an edit, you may end up with two sessions on the date.

Before saving, the proposed action should identify the destination, date, existing record and resulting session. Review the full day's contents when a plan update is involved. Keep read tools available for checking the result, and set write tools to require approval if you want to review every save.

A worked example: shorten a session without changing the template

Suppose a fictional runner has a reusable 45-minute easy-run template and a copy scheduled for Thursday. They now have 30 minutes between work and a school pickup. Their goal is a steady four-run week, not a faster workout in less time.

The useful result is a proposal tied to the correct destination. After approval and a supported save, verify Thursday's actual contents in COROS and confirm the library template remains as intended. We have not run this example against an account; it illustrates how the documented destination rules affect an ordinary scheduling problem.

The conversation also needs the runner's reason. A shorter time window is not evidence that recovery has deteriorated. coach steve's standard is to ask what changed, explain the tradeoff and let the runner choose before a training adjustment.

What are the write and scheduling limits?

COROS documents new structured workouts for running, trail running and cycling, and plans covering 4–16 weeks. The official repository currently distinguishes plan starts within 14 days from standalone workout scheduling within 90 days. Moving or removing a standalone dated workout and deleting or quitting a plan still require the COROS app. Refresh the connected tool definitions before acting because limits can change. COROS's current training-management documentation.

A saved library item is not proof that a watch has received the intended session. Inspect the library or calendar destination first, then use COROS's normal app/device workflow and verify the session on the device before relying on it. A model saying “done” is insufficient evidence of the final watch state.

For deeper analysis, COROS's guide says GPS and cross-workout detail can require FIT retrieval. The official repository gives file retrieval and download-link retrieval a shared 50-file allowance per fixed 24-hour window; client support for binary files varies. Request the specific activities needed, rather than your entire history for a small comparison. COROS's raw-file guidance, current file limits.

When would Apple Health or an export be enough?

COROS's Apple Health guide lists cycling distance, heart rate, sleep analysis, steps, swimming distance and walking/running distance. It does not establish that full workout objects, EvoLab assessments or GPS detail transfer. Configure it through COROS → Profile → Settings → Third Party Apps → Data Sync → Apple Health. COROS's Apple Health field list.

Claude's iPhone Health feature is a US Pro or Max beta. Reading permitted Apple Health categories is a separate route from the official COROS MCP, with a different set of records and controls. Do not expect those six category names to reproduce a detailed interval comparison. Claude iPhone Health documentation.

For manual activity history, COROS Training Hub → Activity List → Export Data produces FIT or TCX files. Daily and sleep data requests follow a separate support process specifying a date range. That is more precise than treating an activity export as a complete wellness archive. COROS bulk export documentation.

For one activity, the app's workout details → Export Data offers formats including FIT and GPX; COROS recommends FIT when heart rate matters. Claude's standard upload list does not include FIT, TCX or GPX. If you prepare a readable CSV or JSON instead, label it as a converted snapshot and preserve the source file. MCP binary-file tools are a different mechanism from ordinary upload support. COROS individual export guide, Claude upload formats.

Is the developer API the same as this connection?

No. COROS separates self-service OAuth MCP from Partner API access. Its developer MCP guide lists single-user authorization, polling rather than webhooks, and no GPX route import/export. The Partner API requires an established platform, security requirements and standard terms, and adds capabilities including webhook push and route support. A personal Claude connection does not establish access to those partner features. Build on COROS MCP, Partner API requirements.

How do you stop access?

Remove the COROS connector in Claude and revoke the associated authorization through the account/service controls COROS provides; verify access has stopped. The official repository advises revocation when no longer using the connection. Previously saved workouts still need their own review, and copies already included in conversations fall under the AI platform's retention rules. Disconnection should not be mistaken for deleting those objects. COROS's authorization and privacy guidance, Claude connector removal.

Claude with official COROS access can offer useful training tools. A runner managing that setup still needs to distinguish a library edit from a scheduled session and check which workout they will actually follow. The value of building it yourself is control; the responsibility is keeping the parts consistent.

We recommend coach steve when you would rather use a service centered on running decisions through SMS. The intended coaching process starts with your goal and what changed, explains a proposal and leaves you involved in the choice. This is our reason for preferring the format, not a claim of superior COROS functionality. coach steve's COROS ingestion and workout delivery are not verified in this review. See our AI running coach comparison for the broader choice.