No sign-in: a real cyclist's indoor rides, read-only. Ask your AI about his power and heart rate.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
The rider's body settings (FTP, FTP history, max HR, weight, age in years, units), the dates of their first and last ride, the ride count and when the app last synced. ftp_history only holds FTPs a test replaced ("Use as FTP"); an FTP the rider typed in is not recorded there.
This tool takes no arguments.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http rawwatts-demo https://app.rawwatts.com/mcp/marco
The rider's body settings (FTP, FTP history, max HR, weight, age in years, units), the dates of their first and last ride, the ride count and when the app last synced. ftp_history only holds FTPs a test replaced ("Use as FTP"); an FTP the rider typed in is not recorded there.
No arguments.
{
"type": "object",
"title": "get_athleteArguments",
"properties": {}
}Best average power per duration (5 s to 60 min) over a period, with the ride each best came from. Dates YYYY-MM-DD, inclusive; both optional (default: all rides).
| Argument | Type | Description |
|---|---|---|
| to_date | any | |
| from_date | any |
{
"type": "object",
"title": "get_power_curveArguments",
"properties": {
"to_date": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "To Date",
"default": null
},
"from_date": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "From Date",
"default": null
}
}
}One ride's full summary as the app computed it: stats (incl. normalized power), laps, power curve, power zones, left/right balance, heart rate, DFA-alpha1 per minute (experimental), the workout ridden and the FTP used.
| Argument | Type | Description |
|---|---|---|
| id* | integer |
{
"type": "object",
"title": "get_rideArguments",
"required": [
"id"
],
"properties": {
"id": {
"type": "integer",
"title": "Id"
}
}
}A ride's second-by-second data averaged down to resolution_s (default 30; at most 720 points, so long rides get a coarser resolution). fields from: power, target, hr, cadence, right_pct, speed, distance, step. Default: power, hr, cadence. t_s is the start of each interval in recorded seconds.
| Argument | Type | Description |
|---|---|---|
| id* | integer | |
| fields | any | |
| resolution_s | integer |
{
"type": "object",
"title": "get_ride_seriesArguments",
"required": [
"id"
],
"properties": {
"id": {
"type": "integer",
"title": "Id"
},
"fields": {
"anyOf": [
{
"type": "array",
"items": {
"type": "string"
}
},
{
"type": "null"
}
],
"title": "Fields",
"default": null
},
"resolution_s": {
"type": "integer",
"title": "Resolution S",
"default": 30
}
}
}Per week (Monday-Sunday) for the last `weeks` weeks (default 8, max 104): rides, hours, kJ and seconds per power zone (Coggan 1-7, by each ride's FTP).
| Argument | Type | Description |
|---|---|---|
| weeks | integer |
{
"type": "object",
"title": "get_training_summaryArguments",
"properties": {
"weeks": {
"type": "integer",
"title": "Weeks",
"default": 8
}
}
}The rider's rides, newest first: id, local start, duration, kJ, average and max power, average and max heart rate, kind (free, ramp, rampLite, edge, workout). Dates are YYYY-MM-DD in the rider's local time, both inclusive. limit: 1-500, default 50. Ids follow the order the app synced the rides, not the ride dates.
| Argument | Type | Description |
|---|---|---|
| limit | integer | |
| to_date | any | |
| from_date | any |
{
"type": "object",
"title": "list_ridesArguments",
"properties": {
"limit": {
"type": "integer",
"title": "Limit",
"default": 50
},
"to_date": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "To Date",
"default": null
},
"from_date": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "From Date",
"default": null
}
}
}Every workout set as text: the rider's own (read-only for you) and each assistant's, with who wrote it. The workout format is in save_workout's description.
No arguments.
{
"type": "object",
"title": "list_workoutsArguments",
"properties": {}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 17, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.