rouvy-mcp
An unofficial Rouvy MCP server for reading your own Rouvy activities and managing your own workout library.
List your Activities newest first with compact summary rows.
Get one Activity’s Rouvy summary and snapshot settings (power, HR, cadence, speed, zones, laps, etc.).
Analyze per-second data: fixed-size intervals/splits, stats for any chosen time window, best efforts, half-vs-half comparisons, and HR:power decoupling.
Fetch downsampled activity streams (power, heart rate, cadence, speed, altitude, distance) for charting or reasoning.
List and read your own Workouts, including steps in % FTP, cues, tags, visibility, route, and current FTP.
Create, update, or delete your own Workouts in Rouvy, only when asked; it does not write anything else.
Optionally export an Activity’s FIT file or per-second CSV to a configured export folder.
Run locally over stdio or self-host on Cloudflare for web MCP clients.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@rouvy-mcp How did my last ride go? Compare the first and second half of the climb."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
rouvy-mcp
Unofficial Rouvy MCP server.
It reads your own Rouvy Activities and serves them to any MCP client (Claude Desktop, Claude Code, Cursor…): list your Activities, read Rouvy's summary of one, and analyse its per-second data (splits, any stretch you pick, downsampled streams). It also reads your own Workouts and, when you ask, creates, changes or deletes them in your Rouvy library. It never writes anything else. It runs locally over stdio, or self-hosted on Cloudflare for web clients such as claude.ai. Please read the disclaimer before you use it.
Install
You need Node.js 22 or later.
1. Log in once, in a terminal:
npx -y rouvy-mcp loginIt asks for your Rouvy email and password (a Rouvy password: Google, Apple or Facebook sign-in alone won't do, but you can set a password on your Rouvy account). The password is never stored. Only a refresh token is kept, in $XDG_CONFIG_HOME/rouvy-mcp/credentials.json (by default ~/.config/rouvy-mcp/credentials.json; %APPDATA%\rouvy-mcp\credentials.json on Windows), readable by you alone.
2. Add the server to your MCP client. For most clients, that's this entry in the MCP config:
{
"mcpServers": {
"rouvy": {
"command": "npx",
"args": ["-y", "rouvy-mcp@latest"]
}
}
}@latest keeps npx from serving an old cached version, so you get the fixes when Rouvy changes something. With Claude Code: claude mcp add rouvy -- npx -y rouvy-mcp@latest.
If you log in after the client has started, there's no need to restart it: the server reads the credentials file on every call.
Optional: exporting files
Set ROUVY_MCP_EXPORT_DIR to an absolute folder path to turn on the export_activity_file tool, which saves an Activity's FIT file, or its per-second records as CSV, into that folder:
{
"mcpServers": {
"rouvy": {
"command": "npx",
"args": ["-y", "rouvy-mcp@latest"],
"env": { "ROUVY_MCP_EXPORT_DIR": "/Users/you/Rouvy exports" }
}
}
}Without it, the tool doesn't exist and rouvy-mcp writes nothing to disk besides the credentials file.
Related MCP server: garmin-raw-mcp
Tools
Tool | What it gives |
| Your Activities, newest first: id, link in the Rouvy web app, title, type, start, moving time, distance, elevation, TSS, IF. |
| One Activity's summary and its link in the Rouvy web app, with Rouvy's own numbers (NP, IF, TSS, power peaks, HR, zones, laps…) and its Activity snapshot (the Rider settings Rouvy stored with it). |
| Fixed-size splits (every 5 min by default) from the per-second Activity file. |
| Stats for one stretch (e.g. a climb from 20:00 to 35:00): best efforts, first half vs second half, HR:power decoupling. |
| Downsampled per-second data (power, heart rate, cadence, speed, altitude, distance), at most 500 points per field. |
| Only with |
| Your own Workouts (the plans in your Rouvy library), newest first: id, link in the Rouvy web app, name, duration, TSS, difficulty, tags, number of Steps. |
| One of your Workouts: its link in the Rouvy web app, its Steps in % FTP (with cadence ranges), Cues, tags, visibility, route, and your current FTP. |
| Creates a Workout in your library from steady, ramp, free-ride and repeated Steps, with Cues and tags. Private unless you ask. |
| Changes one of your Workouts: only the fields given; new Steps replace them all. A Workout synced from another app may be overwritten by that app's next sync. |
| Deletes one of your Workouts and checks it's gone from your library. Rouvy may keep it readable by its id. |
Try asking: "How did my last ride go? Compare the first and second half of the climb."
Commands
npx -y rouvy-mcp login # log in (or switch accounts)
npx -y rouvy-mcp status # who is logged in, and whether a Session can still be opened
npx -y rouvy-mcp logout # delete the credentials filelogout deletes the credentials file from your machine, but it can't revoke the refresh token on Rouvy's side. To make sure a copied credentials file stops working, change your Rouvy password.
How it behaves
It only calls the routes Rouvy's own web app calls, one request at a time, with an honest user agent (
rouvy-mcp/<version>). It never polls and makes no requests while idle.The only writes it can send are to your own Workouts, and only when a tool you called asks for one. Any other write is refused before it leaves your machine. A write is never retried: if Rouvy fails mid-write, the tool tells you to check
list_workoutsfirst.If Rouvy's bot protection or rate limits push back, it stops and tells you when to try again, rather than retrying. A server error or a network failure gets one retry, 2 s later, and an expired Session is renewed once.
No telemetry and no update check: the only requests it makes go to Rouvy.
Nothing is cached on disk.
If a tool says Rouvy changed its API, update (restart your MCP client: @latest picks up the new version) or open an issue.
Self-host on Cloudflare
The hosted server lets riders connect from a web client such as claude.ai, signing in with their Rouvy email and password on its own page instead of running anything locally. You can run your own, with the same code as the Public instance. This is best effort, with no support promise: if you only need it for yourself, the stdio server above costs nothing.
You are the operator. Riders hand your instance their Rouvy login, and it keeps their refresh tokens (encrypted) on your Cloudflare account. The duties that come with that (a privacy notice, answering access and erasure requests, shutting down if Rouvy objects) are yours, not the project's. Read spec-m2 §10 before you invite anyone.
You need a Cloudflare account on Workers Paid ($5/month: tool calls take 57–305 ms of CPU, over the Free plan's 10 ms) and Node.js 22 or later.
Fork the repo and clone your fork, then
npm ciandnpx wrangler login.Pick the instance's URL,
PUBLIC_URLunder[vars]inwrangler.toml: the bare origin, with no path or trailing slash. Its/mcpis the OAuth audience and sits in every rider's connector, so never change it once riders have connected: every Grant would stop working. Keep "rouvy" out of the hostname.On workers.dev (what the Public instance does): set
nameto your Worker's name, andPUBLIC_URLtohttps://<name>.<your-subdomain>.workers.dev. Then never rename the Worker or your account's workers.dev subdomain.On a custom domain on your Cloudflare account (
mcp.example.orgstands for yours): add these two lines at the top level, above[vars], and setPUBLIC_URLto"https://mcp.example.org":workers_dev = false routes = [{ pattern = "mcp.example.org", custom_domain = true }]
Name yourself as the operator,
OPERATOR_NAMEandOPERATOR_CONTACTunder[vars]: your name and the address riders write to about their data. The privacy notice at<PUBLIC_URL>/privacyand the sign-in page show them. Read the notice before inviting anyone, since it's written for the Public instance: you own its accuracy for yours.Create the KV namespace that holds clients, Grants and tokens, and paste the
idit prints intowrangler.toml's[[kv_namespaces]]:npx wrangler kv namespace create OAUTH_KVThere's nothing to create for the Durable Object: the code puts it in the EU jurisdiction (
RIDERS.jurisdiction("eu")), and the first deploy creates it.Keep both compatibility flags,
nodejs_compatandglobal_fetch_strictly_public. Without the second one, the OAuth provider refuses to fetch a client's metadata document, and claude.ai can't connect.Set the allow-list, the Rouvy emails allowed to sign in, separated by commas or whitespace. Anyone else is told the instance is invite-only.
npx wrangler secret put ALLOW_LISTDeploy with
npm run deploy, which stamps the version, then runswrangler deploy. Check<PUBLIC_URL>/.well-known/oauth-protected-resource/mcp: itsresourceis<PUBLIC_URL>/mcp.Connect: in claude.ai, add a custom connector with the URL
<PUBLIC_URL>/mcp, sign in with an allow-listed Rouvy account, and ask for your last Activities.
Running it: docs/operations.md has how long Grants and tokens live, and how to kill one rider, which is also how you handle an erasure request. To shut your instance down for good, take the same steps as the Public instance's Hard stop runbook, on your own account: close the sign-in page, tell your riders, delete the KV namespace, then the Worker. The repo's daily drift canary only checks the Public instance: watch your own /health (it runs the same account-free checks from your Worker's egress, and reports the block signals the runbook acts on).
Disclaimer
Unofficial project. rouvy-mcp is not affiliated with, endorsed by, or supported by ROUVY or VirtualTraining s.r.o. "ROUVY" is a trademark of its owner.
Rouvy has no public API. This tool talks to Rouvy's private web API with your own account, from your own machine, and only reads data. Rouvy's Terms of Use (§29.h) prohibit reverse engineering and "using any automated means for accessing and using ROUVY". Using this tool may breach those terms, and Rouvy may suspend or terminate your account without a refund (§15, §29.d). The API may change or stop working at any time.
Use at your own risk. The software is provided "as is", without warranty of any kind (see LICENSE). The authors aren't responsible for any consequences to your Rouvy account or data. Nothing here is legal advice.
If you'd rather stay within Rouvy's terms, use Rouvy's official integrations (e.g. Intervals.icu, Strava, Garmin Connect) or request a copy of your data from Rouvy under the GDPR (gdpr@rouvy.com).
License
Available Tools
11 toolscreate_workoutA
Create a Workout in the rider's Rouvy library, only when they ask for one. Steps are steady, ramp or free ride, in % FTP (use get_workout's rider_ftp_w to convert watts), each with an optional cadence range; repeat a block with a repeat Step. Private unless the rider asks for public. Returns the saved Workout as Rouvy has it. If it says the outcome is unknown, call list_workouts before trying again.
Inputs: name (required), steps (required), cues, tags, +3 more.
delete_workoutADestructive
Delete one of the rider's own Workouts from their Rouvy library, only when they ask, and check it's gone. Warning: a Workout synced from another app (TrainingPeaks, Intervals.icu…) may come back with that app's next sync. Returns the deleted Workout's id and name.
Inputs: workout_id (required).
export_activity_fileA
Save one Activity to the rider's export folder: its Activity file as downloaded from Rouvy (fit), or its per-second records as CSV (csv). Overwrites an earlier export of the same Activity and returns the file's absolute path.
Inputs: activity_id (required), format.
get_activityA
One Activity's summary, with Rouvy's own numbers (they match the Rouvy app): times, distance, elevation, kcal, NP, IF, TSS, power peaks, min/max/avg power, heart rate, cadence and speed, %FTP, time in power and HR zones, laps and route segment results. Also the Rider settings used (FTP, weight, max HR, zones) from the Activity snapshot, which data exist, and a note for each value left out.
Inputs: activity_id (required).
get_activity_intervalsA
Fixed-size splits of one Activity (every 5 min by default), from its per-second Activity file. For each split: start/end second, avg, NP and max power, avg power as %FTP, avg/max heart rate, avg cadence, avg speed, distance and climbing. %FTP uses the FTP from the Activity snapshot. A note says why any stat is left out.
Inputs: activity_id (required), every_sec.
get_activity_streamsB
Downsampled per-second data of one Activity, from its Activity file, to chart or reason about: one array per field, each value the mean of one bucket of resolution_sec_used seconds from start_sec (the last bucket may be shorter). Units: power W, heart_rate bpm, cadence rpm, speed m/s, altitude m, distance m from the start. At most 500 points per field: a finer request is served at the smallest resolution that fits. A field the Activity doesn't have is listed in missing_fields; a bucket with no data is null.
Inputs: activity_id (required), fields, end_sec, start_sec, +1 more.
get_window_statsA
Stats for one stretch of an Activity (e.g. a climb from 20:00 to 35:00), from its per-second Activity file: the same stats as one split of get_activity_intervals, plus the best efforts (peak powers for the durations that fit), the first half vs the second half, and HR:power decoupling between them. %FTP uses the FTP from the Activity snapshot. A note says why any stat is left out.
Inputs: end_sec (required), start_sec (required), activity_id (required).
get_workoutBRead-only
One of the rider's own Workouts: name, description, tags, visibility, duration, TSS, IF, difficulty, route, its Steps (steady, ramp or free ride, in % FTP, with an optional cadence range) and Cues (text at a time from the start). Also rider_ftp_w, the rider's current FTP in watts, to turn watts into % FTP.
Inputs: workout_id (required).
list_activitiesA
List the rider's Rouvy Activities, newest first, as compact rows (id, title, type, start, moving time, distance, elevation, TSS, IF). Use the ids with the other tools.
Inputs: limit, offset.
list_workoutsARead-only
List the rider's own Workouts in their Rouvy library (the plans, not the rides), newest first, as compact rows (id, name, duration, TSS, difficulty, tags, number of Steps). Use get_workout for the Steps.
Inputs: limit, offset.
update_workoutADestructiveIdempotent
Change one of the rider's own Workouts, only when they ask. Give only what changes: steps, when given, replace all Steps; every field left out (cues included) keeps its current value; the route is kept. A get_workout result can be edited and passed back as is. Warning: a Workout synced from another app (TrainingPeaks, Intervals.icu…) may be overwritten by that app's next sync. Returns the saved Workout.
Inputs: workout_id (required), cues, name, tags, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
Each tool has a clearly distinct role, and the descriptions explicitly differentiate them (summary vs. fixed splits vs. arbitrary window vs. raw stream). The closest pair is get_activity_intervals and get_window_stats, which return the same stat family and can overlap if a window matches a split, but the fixed-vs-arbitrary distinction is spelled out well enough to choose correctly.
Almost everything follows a consistent snake_case verb_noun pattern grouped by resource (activities, workouts), with get/create/update/delete_workout forming a clean CRUD set. The only wobble is get_window_stats, whose noun omits the 'activity' resource seen in every other activity tool.
Eleven tools is well within the sweet spot and each one earns its place: four read tools for activity analysis, five for the workout lifecycle, one for export. No redundant or filler tools are present.
Workouts have full CRUD and activities have a rich read/analysis/export surface, so the main workflows are covered. Minor gaps remain: no standalone rider-profile/settings tool (FTP only surfaces via get_workout), no route listing to attach to a created workout, and no activity delete or route browsing.
Maintenance
Related MCP Connectors
Strava MCP tools for AI: athletes, activities, segments, clubs, routes. Powered by HAPI MCP server.
Your own cycling data for your AI assistant: rides, power, climbs and routes. Read-only.
Read your workouts, history, and stats; create and schedule new workouts. Writes are additive only.
Your swim, bike and run training: readiness, HRV, sleep, workouts and race predictions. Read-only.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceMCP server to fetch Strava activities using OAuth authentication with automatic token refresh. Allows retrieving recent activities, activities by date range, activity details, and athlete stats.-
- AlicenseNot gradedqualityBmaintenanceProvides raw Garmin Connect data access for training analysis, enabling retrieval of activity summaries, lap data, time-series streams, comments with lactate, wellness metrics, and personal records through an MCP interface.MIT
- AlicenseBqualityBmaintenancePrivacy-first MCP server for Strava activities, streams, routes and training data.29235 npm3MIT
- AlicenseBqualityBmaintenanceMCP server for local fitness-data extraction and analysis from Garmin Connect, Intervals.icu, and Strava. Provides read-only analytical tools over DuckDB and targeted Strava enrichment.35469 npm1AGPL 3.0