# COROS MCP server
> Query COROS activity, sleep, HRV and training load data, and create or adjust training plans and workouts.
- Listing: https://mcp.tc/i/coros
- Connect: use the server's own URL `https://mcpus.coros.com/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Data & Analytics](https://mcp.tc/c/analytics)
- Vendor: COROS
- Homepage:
- Repository:
## About
Connects an AI assistant to your COROS account. You can review activities, laps and detailed metrics, check sleep, HRV, heart rate, stress and recovery, view fitness assessments, race predictions and training load, and read linked devices and profile information. Training plans and workouts can be created, changed and scheduled.
Runs as a hosted endpoint with US, EU and CN regions. Users sign in with their COROS account and authorize access. The service is free to use.
## What it can do
- Query activities, laps, custom segments and detailed metrics
- Retrieve FIT files for activities
- Review sleep, HRV, heart rate, stress and recovery
- View fitness assessments, race predictions and training load
- Create and modify training plans and workouts
- Schedule workouts on the training calendar
- Read profile information and linked devices
## Example prompts
- "Compare my last two long runs. How did pace and heart rate differ in the second half?"
- "Summarize my sleep and HRV trends over the past two weeks alongside my training volume."
- "Draft an 8-week half marathon plan from my recent training and save it to COROS."
- "Show my current training load and race predictions."
## Install
### Claude Code
1. Run this in a terminal, in your project folder:
```bash
claude mcp add --transport http coros https://mcpus.coros.com/mcp
```
2. Start Claude Code, type `/mcp`, pick **coros** and choose **Authenticate**. A browser window opens for the COROS sign-in.
Add `--scope user` to make it available in every project, not just this one.
### Claude Desktop
1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.
2. Name it **COROS** and paste this URL:
```url
https://mcpus.coros.com/mcp
```
3. Click **Add**, then **Connect**, and sign in when COROS asks.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
### claude.ai
1. Open the connector form on claude.ai. This button fills in the name and URL for you:
[Add to claude.ai]() (opens connector settings)
2. Check that the URL reads `https://mcpus.coros.com/mcp` and click **Add**.
3. Click **Connect** and sign in when COROS asks.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.
### ChatGPT
1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.
2. Enter a name for the server.
3. Under **Connection**, paste `https://mcpus.coros.com/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to COROS to sign in.
4. Check **I understand and want to continue**, then select **Create as a plugin**.
Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).
### Cursor
[Add to Cursor]() (opens Cursor)
Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):
`mcp.json`:
```json
{
"mcpServers": {
"coros": {
"url": "https://mcpus.coros.com/mcp"
}
}
}
```
Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.
### VS Code
[Install in VS Code]() (opens VS Code)
Or from a terminal:
```bash
code --add-mcp '{"name":"coros","type":"http","url":"https://mcpus.coros.com/mcp"}'
```
Or commit it to the repo in `.vscode/mcp.json`:
`.vscode/mcp.json`:
```json
{
"servers": {
"coros": {
"type": "http",
"url": "https://mcpus.coros.com/mcp"
}
}
}
```
VS Code asks you to sign in the first time the server starts.
### Devin Desktop
1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):
`mcp_config.json`:
```json
{
"mcpServers": {
"coros": {
"serverUrl": "https://mcpus.coros.com/mcp"
}
}
}
```
2. Refresh the MCP server list in Cascade and sign in when asked.
Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.
### Codex
```bash
codex mcp add coros --url https://mcpus.coros.com/mcp
codex mcp login coros
```
Or edit `~/.codex/config.toml` directly:
`config.toml`:
```toml
[mcp_servers.coros]
url = "https://mcpus.coros.com/mcp"
```
### Gemini CLI
```bash
gemini mcp add --transport http coros https://mcpus.coros.com/mcp
```
Then, inside Gemini CLI, run `/mcp auth coros` to sign in.
This adds it to the current project. Add `-s user` to use it everywhere.
### Any client
Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.
```json
{
"mcpServers": {
"coros": {
"type": "http",
"url": "https://mcpus.coros.com/mcp"
}
}
}
```
Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.
Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcpus.coros.com/mcp`.
## Details
- Server version: 1.0.1
- Last checked: 2026-11-15 (reachable, asks for credentials)
- Listed: 2026-11-01
- Updated: 2026-11-01
---
Source: https://mcp.tc/i/coros (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report