Garmin 기반 지표, 웰니스 트렌드, 운동 실행 데이터를 포함한 Intervals.icu 훈련 데이터를 AI 어시스턴트가 분석할 수 있게 합니다.
다른 이름 futureweb/intervals-mcp-server, intervals-mcp-server, futureweb-intervals-mcp
- 스타
- 14
- Tools
- 52
- 다운로드, 30일
- —
- 최신 버전
- 1.0.0b2
- 마지막 커밋
- 2026년 11월 1일
- 라이선스
- GPL-3.0
Futureweb Intervals MCP란?
Garmin 기반 지표, 웰니스 트렌드, 운동 실행 데이터를 포함한 Intervals.icu 훈련 데이터를 AI 어시스턴트가 분석할 수 있게 합니다. 52개 도구를 제공합니다. 예: get_gear_list, get_gear_details, get_athlete_profile.
프로젝트 README에서 생성된 요약
Futureweb Intervals MCP server 정보
Futureweb Intervals MCP는 AI 어시스턴트가 Intervals.icu의 훈련 데이터를 분석할 수 있는 기능을 제공합니다. 이 서버는 ChatGPT 또는 Claude와 같은 클라이언트를 사용하여 복잡한 생리학적 지표를 해석하고자 하는 선수와 코치를 위해 설계되었습니다. 서버는 Intervals.icu API에 연결되며, 표준 동기화 과정에서 누락되기 쉬운 VO2max, 지구력, 수면 상세 정보와 같은 지표를 복원하는 Garmin Intervals Bridge의 데이터를 읽도록 구성할 수 있습니다.
사용자는 로컬에서 서버와 상호작용하거나 내장된 OAuth 2.1 시스템을 통해 원격으로 액세스할 수 있습니다. 안전을 위해 기본적으로 읽기 전용으로 설정되어 있지만, 특정 작업을 위해 쓰기 권한을 활성화할 수 있습니다. 활동 보고서, 웰니스 트렌드, 영양 및 운동 실행을 검토하기 위한 다양한 전문 도구를 제공합니다. 이 시스템은 AI 모델로 전송되는 데이터 양을 관리할 수 있도록 다양한 상세 수준을 제공하여 토큰 효율성을 높이도록 구축되었습니다.
활용 사례
- 1웰니스 및 회복 모니터링개인 기준 데이터를 바탕으로 웰니스 트렌드 및 회복 스냅샷 요약을 요청합니다.
- 2산악 등반 추적한 해 동안 등반한 특정 정상이나 산악 고개를 식별합니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Futureweb Intervals MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Futureweb Intervals MCP 설치
$ claude mcp add --env 'API_KEY=<YOUR_API_KEY>' --env 'ATHLETE_ID=<ATHLETE_ID>' intervals-mcp-server -- uvx futureweb-intervals-mcpCursor에 Futureweb Intervals MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"intervals-mcp-server": {
"command": "uvx",
"args": [
"futureweb-intervals-mcp"
],
"env": {
"API_KEY": "<YOUR_API_KEY>",
"ATHLETE_ID": "<ATHLETE_ID>"
}
}
}
}VS Code에 Futureweb Intervals MCP 설치
.vscode/mcp.json
{
"servers": {
"intervals-mcp-server": {
"type": "stdio",
"command": "uvx",
"args": [
"futureweb-intervals-mcp"
],
"env": {
"API_KEY": "<YOUR_API_KEY>",
"ATHLETE_ID": "<ATHLETE_ID>"
}
}
}
}VS Code CLI에 Futureweb Intervals MCP 설치
$ code --add-mcp '{"name":"intervals-mcp-server","type":"stdio","command":"uvx","args":["futureweb-intervals-mcp"],"env":{"API_KEY":"<YOUR_API_KEY>","ATHLETE_ID":"<ATHLETE_ID>"}}'Claude Desktop에 Futureweb Intervals MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"intervals-mcp-server": {
"command": "uvx",
"args": [
"futureweb-intervals-mcp"
],
"env": {
"API_KEY": "<YOUR_API_KEY>",
"ATHLETE_ID": "<ATHLETE_ID>"
}
}
}
}Codex에 Futureweb Intervals MCP 설치
$ codex mcp add intervals-mcp-server --env 'API_KEY=<YOUR_API_KEY>' --env 'API_KEY=<YOUR_API_KEY>' --env 'ATHLETE_ID=<ATHLETE_ID>' --env 'ATHLETE_ID=<ATHLETE_ID>' -- uvx futureweb-intervals-mcpCodex config.toml에 Futureweb Intervals MCP 설치
~/.codex/config.toml
[mcp_servers.intervals-mcp-server] command = "uvx" args = ["futureweb-intervals-mcp"] [mcp_servers.intervals-mcp-server.env] API_KEY = "<YOUR_API_KEY>" ATHLETE_ID = "<ATHLETE_ID>"
Gemini CLI에 Futureweb Intervals MCP 설치
$ gemini mcp add -s user -e 'API_KEY=<YOUR_API_KEY>' -e 'API_KEY=<YOUR_API_KEY>' -e 'ATHLETE_ID=<ATHLETE_ID>' -e 'ATHLETE_ID=<ATHLETE_ID>' intervals-mcp-server uvx -- futureweb-intervals-mcpGemini settings.json에 Futureweb Intervals MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"intervals-mcp-server": {
"command": "uvx",
"args": [
"futureweb-intervals-mcp"
],
"env": {
"API_KEY": "<YOUR_API_KEY>",
"ATHLETE_ID": "<ATHLETE_ID>"
}
}
}
}HostedMCP가 2026년 11월 16일에 실행 확인
futureweb-intervals-mcp 1.0.0b2을(를) 네트워크와 키가 없는 격리된 컨테이너에서 이 명령으로 실행했습니다. 응답하며 도구 52개를 보여 주었습니다.
Futureweb Intervals MCP 도구 52
tools/list로 서버에서 직접 읽음get_gear_list읽기 전용Use to find gear ids and get an overview of the athlete's bikes, shoes and components (read-only). One row per item: id, type, name, default-for, activity count, distance in km and retired flag. Details of one item (components, reminders, filters): get_gear_details; activities on a gear: get_activities(gear_id=...).
get_gear_details읽기 전용Use for the details of one gear item (bike, shoes, component; read-only). Distance, time and activity count, purchase and retirement dates, notes, the bike a component belongs to, the activity type filters that assign activities automatically, maintenance reminders with their usage, and for a bike its components (frame, power meter, chain, tyres ...) with their own mileage. Which power meter recorded an activity is not derived from gear: get_activity_details shows the power meter and serial from the device file. Activities on this gear: get_activities(gear_id=...).
get_athlete_profile읽기 전용Use for who the athlete is: name, sex, date of birth, location, time zone, units, weight, height, resting HR, bikes and shoes, training plan and coach (read-only). Also one line per sport setting (FTP, indoor FTP, LTHR, max HR, threshold pace). Only coaching-relevant fields: account internals such as e-mail, API keys or OAuth scopes are never returned. The profile's time zone defines "today" for all tools. Details: get_sport_settings, get_training_zones, get_gear_list.
get_sport_settings읽기 전용Use for the current thresholds and settings per sport (a group of activity types such as Ride, GravelRide/MountainBikeRide or Run/TrailRun; read-only). Per sport setting: FTP and indoor FTP, W', Pmax, the latest Intervals.icu eFTP estimate, LTHR and max HR, threshold pace with pace units, load models, default outdoor/indoor gear, warm-up/cool-down times and the power, HR and pace zones with absolute ranges. The thresholds in force for a past activity are in get_activity_details (snapshot stored with the activity). Zones only: get_training_zones; change thresholds: update_sport_settings.
get_training_zones읽기 전용Use for the power, heart rate and pace zones of each sport setting (read-only). Power zones in % of FTP with watts from the current FTP and the sweet spot range, HR zones in bpm, pace zones in % of threshold speed with the pace from the threshold pace; each zone has its name, bounds and absolute range. Current settings only. Thresholds and other settings: get_sport_settings.
get_custom_items읽기 전용Use to list the athlete's custom items (charts, custom activity, interval and wellness fields, streams, zones ...) with id, name, type and description (read-only). Also refreshes the cached definitions the other tools use to label custom fields. Full definition of one item: get_custom_item_by_id.
get_custom_item_by_id읽기 전용Use for the full definition of one custom item: name, type, description, visibility, index and its content configuration as JSON (code, value type, units, options, aggregate ...; read-only). Ids: get_custom_items.
get_activities읽기 전용Use to find activities and their ids in a date range (default the last 30 days up to today, 10 per page), e.g. all rides on one bike over a season. Returns one summary block per activity (Intervals.icu load, power, HR, feel/RPE, gear), one line each with detail_level=compact, or JSON records with units and local/UTC start. Filters: sport types, gear, power meter name. Any filter, sort, offset, compact or json gives a paged listing with the total and the next offset. Unnamed activities are hidden unless include_unnamed; nothing outside the date range is listed. Read-only. One activity in depth: get_activity_report. Method: intervals://methods/activity-data (get_guide).
get_activity_details읽기 전용Use when one activity's full summary, thresholds or device custom fields are needed beyond get_activity_report. Returns the summary (time, distance, Intervals.icu load, power, HR, cadence, feel/RPE, FTP and thresholds used, device and power meter), fueling, weather, W′ balance and source, plus every custom activity field with a value (device metrics such as training effect, recovery time, stamina, sweat loss), read from the athlete's own definitions with name, code, value and units; 'no value' = null/NaN on Intervals.icu. full adds time in zones, running dynamics and other raw fields. Read-only. Method: intervals://methods/activity-data (get_guide).
get_activity_intervals읽기 전용Use for per-interval numbers of one activity (laps or detected efforts): power, HR, cadence, speed, intensity, custom interval fields and groups. Cadence follows the sport: steps per minute on foot (2 x the stored per-leg value), rpm otherwise. stream_types adds start/end/min/max/mean/delta of any stream per interval from the recorded samples, e.g. stamina drop or a second power meter (list_activity_streams shows what exists). include_planned_types shows the planned step matched to each interval and the time beyond the plan; the Intervals.icu type is kept. Without intervals use analyze_climbs. Read-only; 2 API calls, +1 for streams, +1 for a paired event. Methods: intervals://methods/activity-data, intervals://methods/execution (get_guide).
get_activity_streams읽기 전용Use for the raw time-series samples of one activity (power, HR, cadence, altitude or any custom stream such as Stamina) when summaries are not enough. Default output is a per-stream summary (units, statistics, first/last values); full gives a CSV table, json one object with arrays (empty/null = no value). Default streams: time, watts, heartrate, cadence, altitude, distance, velocity_smooth; "all" = every stream. full/json return at most max_points samples (default 2000) and say where to continue; slice by index or time, downsample keeps every n-th sample. time = seconds since start, pauses appear as jumps. Read-only. Discover streams with list_activity_streams. Method: intervals://methods/activity-data (get_guide).
list_activity_streams읽기 전용Use before get_activity_streams or get_activity_intervals(stream_types=...) to see which data streams one activity has. Lists the standard streams and the athlete's custom streams present on the activity (e.g. stamina, potential stamina, performance condition, grade adjusted speed, gear selection, battery) with type code, display name, units and description, plus the power fields of the file. include_stats downloads the streams and adds per-stream sample counts and start/end/min/max/mean. Read-only. Method: intervals://methods/activity-data (get_guide).
| get_gear_list | Use to find gear ids and get an overview of the athlete's bikes, shoes and components (read-only). One row per item: id, type, name, default-for, activity count, distance in km and retired flag. Details of one item (components, reminders, filters): get_gear_details; activities on a gear: get_activities(gear_id=...). | 읽기 전용 |
| get_gear_details | Use for the details of one gear item (bike, shoes, component; read-only). Distance, time and activity count, purchase and retirement dates, notes, the bike a component belongs to, the activity type filters that assign activities automatically, maintenance reminders with their usage, and for a bike its components (frame, power meter, chain, tyres ...) with their own mileage. Which power meter recorded an activity is not derived from gear: get_activity_details shows the power meter and serial from the device file. Activities on this gear: get_activities(gear_id=...). | 읽기 전용 |
| get_athlete_profile | Use for who the athlete is: name, sex, date of birth, location, time zone, units, weight, height, resting HR, bikes and shoes, training plan and coach (read-only). Also one line per sport setting (FTP, indoor FTP, LTHR, max HR, threshold pace). Only coaching-relevant fields: account internals such as e-mail, API keys or OAuth scopes are never returned. The profile's time zone defines "today" for all tools. Details: get_sport_settings, get_training_zones, get_gear_list. | 읽기 전용 |
| get_sport_settings | Use for the current thresholds and settings per sport (a group of activity types such as Ride, GravelRide/MountainBikeRide or Run/TrailRun; read-only). Per sport setting: FTP and indoor FTP, W', Pmax, the latest Intervals.icu eFTP estimate, LTHR and max HR, threshold pace with pace units, load models, default outdoor/indoor gear, warm-up/cool-down times and the power, HR and pace zones with absolute ranges. The thresholds in force for a past activity are in get_activity_details (snapshot stored with the activity). Zones only: get_training_zones; change thresholds: update_sport_settings. | 읽기 전용 |
| get_training_zones | Use for the power, heart rate and pace zones of each sport setting (read-only). Power zones in % of FTP with watts from the current FTP and the sweet spot range, HR zones in bpm, pace zones in % of threshold speed with the pace from the threshold pace; each zone has its name, bounds and absolute range. Current settings only. Thresholds and other settings: get_sport_settings. | 읽기 전용 |
| get_custom_items | Use to list the athlete's custom items (charts, custom activity, interval and wellness fields, streams, zones ...) with id, name, type and description (read-only). Also refreshes the cached definitions the other tools use to label custom fields. Full definition of one item: get_custom_item_by_id. | 읽기 전용 |
| get_custom_item_by_id | Use for the full definition of one custom item: name, type, description, visibility, index and its content configuration as JSON (code, value type, units, options, aggregate ...; read-only). Ids: get_custom_items. | 읽기 전용 |
| get_activities | Use to find activities and their ids in a date range (default the last 30 days up to today, 10 per page), e.g. all rides on one bike over a season. Returns one summary block per activity (Intervals.icu load, power, HR, feel/RPE, gear), one line each with detail_level=compact, or JSON records with units and local/UTC start. Filters: sport types, gear, power meter name. Any filter, sort, offset, compact or json gives a paged listing with the total and the next offset. Unnamed activities are hidden unless include_unnamed; nothing outside the date range is listed. Read-only. One activity in depth: get_activity_report. Method: intervals://methods/activity-data (get_guide). | 읽기 전용 |
| get_activity_details | Use when one activity's full summary, thresholds or device custom fields are needed beyond get_activity_report. Returns the summary (time, distance, Intervals.icu load, power, HR, cadence, feel/RPE, FTP and thresholds used, device and power meter), fueling, weather, W′ balance and source, plus every custom activity field with a value (device metrics such as training effect, recovery time, stamina, sweat loss), read from the athlete's own definitions with name, code, value and units; 'no value' = null/NaN on Intervals.icu. full adds time in zones, running dynamics and other raw fields. Read-only. Method: intervals://methods/activity-data (get_guide). | 읽기 전용 |
| get_activity_intervals | Use for per-interval numbers of one activity (laps or detected efforts): power, HR, cadence, speed, intensity, custom interval fields and groups. Cadence follows the sport: steps per minute on foot (2 x the stored per-leg value), rpm otherwise. stream_types adds start/end/min/max/mean/delta of any stream per interval from the recorded samples, e.g. stamina drop or a second power meter (list_activity_streams shows what exists). include_planned_types shows the planned step matched to each interval and the time beyond the plan; the Intervals.icu type is kept. Without intervals use analyze_climbs. Read-only; 2 API calls, +1 for streams, +1 for a paired event. Methods: intervals://methods/activity-data, intervals://methods/execution (get_guide). | 읽기 전용 |
| get_activity_streams | Use for the raw time-series samples of one activity (power, HR, cadence, altitude or any custom stream such as Stamina) when summaries are not enough. Default output is a per-stream summary (units, statistics, first/last values); full gives a CSV table, json one object with arrays (empty/null = no value). Default streams: time, watts, heartrate, cadence, altitude, distance, velocity_smooth; "all" = every stream. full/json return at most max_points samples (default 2000) and say where to continue; slice by index or time, downsample keeps every n-th sample. time = seconds since start, pauses appear as jumps. Read-only. Discover streams with list_activity_streams. Method: intervals://methods/activity-data (get_guide). | 읽기 전용 |
| list_activity_streams | Use before get_activity_streams or get_activity_intervals(stream_types=...) to see which data streams one activity has. Lists the standard streams and the athlete's custom streams present on the activity (e.g. stamina, potential stamina, performance condition, grade adjusted speed, gear selection, battery) with type code, display name, units and description, plus the power fields of the file. include_stats downloads the streams and adds per-stream sample counts and start/end/min/max/mean. Read-only. Method: intervals://methods/activity-data (get_guide). | 읽기 전용 |
도구 52개 모두 보기도구 수 줄이기
get_activity_messages읽기 전용Use to read the notes and comments on one activity: author, time, type and text of each message (read-only).
get_events읽기 전용Use to see the athlete's calendar: planned workouts, races, notes and other events of a date range (default today to 30 days ahead). Each event shows its category (Workout, Race A/B/C, Note ...), sport (Ride, Run ...), planned time and load, and the paired activity once it has been done. Full workout steps: get_event_by_id. Plan phases and weekly targets: get_training_plan.
get_event_by_id읽기 전용Use to read one calendar event completely, e.g. to read back a workout right after writing it. Returns category and sport, planned time and load, the paired activity and the full workout document (steps, planned time in zones).
get_training_plan읽기 전용Use for the season view: the assigned training plan, plan phases, weekly targets, races with priority and events that set the fitness model (read-only). Reads the training plan assigned to the athlete and the calendar entries of the annual plan: PLAN (phases/blocks), TARGET (weekly load, time or distance targets), RACE_A/B/C, SEASON_START, and set eFTP / set fitness and fatigue / fitness days. Default range: 30 days back to 180 days ahead. Single workouts: get_events.
get_athlete_power_curves읽기 전용Use for an athlete's best power per duration over whole periods: season bests, progress between seasons or date ranges. Returns watts and W/kg per duration for this season, last season and/or a custom range, each with the activity that set it. Defaults: Ride, 5 s to 60 min, both seasons; durations that are not curve points are left out. Read-only, one API call. One activity: get_best_efforts; HR and pace: get_hr_curves, get_pace_curves. Method: intervals://methods/comparisons (get_guide).
get_hr_curves읽기 전용Use for the highest average heart rate an athlete sustained per duration over one or more periods (e.g. comparing periods; with get_pace_curves the same pace at a lower HR). Returns bpm per duration for each curve (default the last 90 days) with the activity that set it; durations without data are listed as not available. Read-only, one API call. Power: get_athlete_power_curves. Method: intervals://methods/comparisons (get_guide).
get_pace_curves읽기 전용Use for an athlete's best times per distance over one or more periods: PBs, comparing periods, progress in running or swimming. Returns the best time and pace (min/km; min/100 m for Swim and OpenWaterSwim) per distance for each curve (default the last 90 days) with the activity that set it; optionally gradient-adjusted pace. Distances not on the curve are listed as not available. Read-only, one API call. HR side: get_hr_curves. Method: intervals://methods/comparisons (get_guide).
get_best_efforts읽기 전용Use for the peak efforts of one activity: best average power, HR or speed over durations (s) or distances (m), e.g. peak 5 s to 20 min power or the fastest km of a run (velocity_smooth with distances). Returns per effort the average (W, bpm or m/s with pace) and its position as elapsed h:mm:ss and sample indices (usable as start_index / end_index); windows spanning a recording pause are flagged. Default durations 5 s to 60 min; longer than the activity = not available. Read-only; one API call per duration or distance plus 1-2. Several activities: compare_best_efforts; period bests: get_athlete_power_curves. Method: intervals://methods/comparisons (get_guide).
compare_best_efforts읽기 전용Use to compare peak efforts (e.g. 1 / 5 / 20 min power) of several activities side by side: development over a block, races, or whether a new bike or power meter reads differently. Returns a matrix of activities (date, sport, gear, FTP at the time) by duration with the best average of the stream, and the best activity per duration. Activities come from activity_ids or a date range (default the last 90 days), filtered by sport and gear; newest first, limit 10 (max 25), at most 10 durations. Power meters of different bikes are not calibrated against each other; no verdict. Read-only; one API call per activity and duration (up to 250) plus the list and gear calls. One activity in detail: get_best_efforts. Method: intervals://methods/comparisons (get_guide).
find_similar_intervals읽기 전용Use to find earlier activities with intervals of a given length and intensity (% of FTP), or like the main set of a reference activity, ranked by comparability. Pass min/max_secs and min/max_intensity, or reference_activity_id (window from its main set: length ±25 %, intensity ±8 points of FTP; explicit values win; only the 365 days before it unless start_date is given). Returns per activity date, sport, interval summary, load, FTP at the time, gear, power meter, compliance and a comparability score 0-100 with reasons. Sport defaults to one family (other families are counted, "all" keeps every sport); watts of different power meters are not comparable, use % of FTP. Read-only; one API call (+2 with a reference, +1 gear catalog). Details: get_activity_intervals; same workout over time: compare_workouts. Method: intervals://methods/comparisons (get_guide).
get_activity_histogram읽기 전용Use for the time distribution of one activity independent of zone definitions: how polarised a ride was, time above FTP, the pace spread of a run. Returns the seconds and % of recorded time in each power (W), heart rate (bpm), pace or grade-adjusted pace bucket, as computed by Intervals.icu; pace and GAP buckets are speeds in m/s shown with the pace range. bucket_size applies to power and hr only. Read-only, one API call. Method: intervals://methods/comparisons (get_guide).
compare_workouts읽기 전용Use to compare repeated executions of the same workout over time (e.g. every 3 x 10 min threshold session) on truly comparable work intervals. Activities by name search (query), activity_ids or a date range (default the last 90 days); limit 8 (max 12). WORK intervals are split into main set (similar length and intensity), surges, other and excluded; the main set gets time-weighted power, NP, HR, max HR, cadence, W/bpm. Only activities matching the reference pattern (reference_activity_id, else the newest; length ±25 %, intensity ±8 points of FTP) are compared; trends first -> last with n (< 3 not reliable). RPE is whole-activity only; gear and power meter differences are flagged; no verdict. Read-only; one API call per activity plus 1-3 (one more per id with activity_ids). Method: intervals://methods/comparisons (get_guide).
get_power_hr_efficiency읽기 전용Use to track power-to-heart-rate efficiency (W per bpm at the same power) over weeks. Puts every WORK interval of at least min_interval_secs with power and HR into the power band of its average power; returns per activity and band the count and time-weighted W, HR and W/bpm, and per band the oldest vs the newest group of activities (each counts once; at least 3 per group, else not reliable) compared with the day-to-day SD. Default the last 90 days of rides, limit 30 (max 60); trends per gear when several power meters are involved; filters for gear, indoor/outdoor and interval start time. Heat, fatigue, cadence and sensors move the ratio: statistics only, no fitness verdict. Read-only; one API call per activity plus 2. Method: intervals://methods/comparisons (get_guide).
get_fatigue_resistance읽기 전용Use for fatigue resistance: best power fresh vs after the athlete's work thresholds kJ0 / kJ1 (Intervals.icu fatigued power curves). Reads the sport settings first. When they hold no kJ thresholds no fatigued values are shown: the tool explains the setting and (suggest_thresholds) proposes thresholds from body mass and recent rides, never saved. Otherwise returns watts per duration fresh and after kJ0 / kJ1 with the change in %, for one activity or for athlete curves (default 42d); a fatigued curve without data is reported as missing, one equal to fresh as identical, without a change. Read-only, 2-5 API calls. Within one long ride: get_long_ride_fatigue_profile. Method: intervals://methods/comparisons (get_guide).
compare_power_streams읽기 전용Use to compare two power meters recorded on the same ride (watts vs secondary_power by default), on one ride or across several rides. One ride (activity_id): offset in W and % (secondary - primary), per power band, in stable 30/60 s windows, drift over the ride quarters, lag, best efforts of each stream and the samples excluded as coasting, missing or outliers. Several rides (no activity_id, or activity_ids): the rides that carry the second stream (default 180 days to end_date, newest first, limit 10, max 20), each compared on its own and summarised per bike and power meter with median, between-ride SD and range. No calibration and no correction factor; sensors are named only from the file's device data. Read-only. Method: intervals://methods/power-meters (get_guide).
analyze_workout_execution읽기 전용Use to check how a planned workout was executed, or without a plan to evaluate each detected interval of one activity. The plan comes from planned_workout_doc, event_id or the event paired with the activity. Planned steps (repeats expanded) are aligned with the intervals by order, duration or distance and target intensity, never by names; laps that split one effort are merged. Per step: planned vs actual moving time, target (W, bpm or pace) vs actual, time in target, HR response, cadence, fade, Pw:HR drift (work steps of 10 min or more) and custom stream changes, with deviation notes and an alignment confidence. Time past a step's plan and training after the plan are reported apart. Unpaired: up to three candidate events, nothing is paired. Read-only. Method: intervals://methods/execution (get_guide).
analyze_climbs읽기 전용Use for activities without useful intervals (tours, mountain hikes, trail runs) to split the recording into climbs, descents, sections in between and pauses. Per segment: time and sample indices, moving time, distance, gain/loss, average and steepest grade, VAM, speed, power, NP, HR, cadence and start/end/min/max/mean/delta of every custom stream. Defaults follow the sport (foot vs bike); implausible grades are flagged and each segment gets a grade confidence. Slow scrambling counts as moving, real pauses as pause. Climb gains are not the activity's total elevation gain. Text lists up to max_segments segments. Read-only, 2 API calls (activity, all streams). Method: intervals://methods/climbs (get_guide).
get_training_load읽기 전용Use for acute and chronic training load in detail: acute (default 7 d) and chronic (28 d) Intervals.icu load, acute:chronic ratio (coupled daily means), Foster monotony and strain, deload-like weeks, per sport family with the primary sport, ISO weeks, and CTL/ATL/form/ramp at the end date (read-only). Rest days count as 0; sessions without a load are counted, not added. Device loads (custom fields such as a Garmin training load) are listed apart on their own scale, never added. With the default end date and nothing recorded today yet, the windows end yesterday. Reference ranges (ACWR 0.8-1.3, monotony > 2.0) are shown with sources as context; small samples are flagged; no verdict. Overview: get_coach_context; planned load: get_load_projection. Method: intervals://methods/load (get_guide).
get_load_projection읽기 전용Use for future fitness: CTL, ATL and form projected over the planned workouts in the calendar, or a what-if scenario (sessions or weekly templates not in the calendar) against the calendar plan (read-only, nothing is written). Starts from Intervals.icu's CTL/ATL at the end of yesterday plus today's completed load; planned workouts without a load are reported, not guessed. Returns end values, lowest form, highest ramp, ISO weeks with plan statistics, race days, Intervals.icu's own projection, a model check and weeks outside commonly cited ranges (ramp 5-8 CTL/week, monotony > 2.0, no rest day). With target_date, target_form or a scenario: the target day (default the next RACE_A) at the start of the day; target_form adds a search for the load of the last taper_days that reaches it. Arithmetic, not a forecast; no verdict. Method and scenario format: intervals://methods/load (get_guide).
get_activity_data_audit읽기 전용Use to check where an activity's data came from and what is missing, or without activity_id how complete the data of a period is. One activity: source (sync, upload, Strava stub), upload and analysis times, filtered duplicates, recording stops, FIT laps vs intervals and edits, sensors, streams vs those usual for the sport with coverage, custom fields with value / zero placeholder / none, fields the Garmin Intervals Bridge could fill. Period (default 28 days to end_date): per sport how many activities have power, HR, GPS, weather, custom streams and fields. Facts and counts, no verdict; read-only, 1-3 API requests. Method: intervals://methods/activity-data (get_guide).
get_activity_report읽기 전용Use first for any question about one activity: overview, plan vs execution, power meter check, climbs and data quality in one call (read-only, 3-4 API requests). The overview has thresholds, device, sport-assigned custom fields, fueling, weather and W′ balance. With a paired event or planned_workout_doc the plan-vs-execution analysis follows (as analyze_workout_execution), otherwise the intervals; a second-power-meter check only with enough valid paired samples; climbs without intervals or above 500 m gain; then data-quality notes. compact = core numbers and up to 5 key findings. Full detail: get_activity_details, analyze_workout_execution, compare_power_streams, analyze_climbs, get_activity_data_audit. Methods: intervals://methods/activity-data, intervals://methods/execution (get_guide).
get_fueling_analysis읽기 전용Use for carbohydrate, fluid and sodium intake of one activity (activity_id) or of the long sessions of a period (default the last 90 days, sessions of at least min_minutes; read-only). Carbs used (Intervals.icu estimate) and ingested (logged total) in g and g/h, the ingested share of used, kcal and kJ, and fluid intake, sodium and sweat loss per hour where custom fields exist (found by units and name). One activity also gets the intake per hour from a custom intake stream, if there is one. Period: statistics per sport family, by duration and by intensity, Spearman correlations from 8 sessions, with sample sizes. Not logged is never 0; used minus ingested is no 1:1 energy deficit; no targets. Method: intervals://methods/fueling (get_guide).
get_recovery_snapshot읽기 전용Use for the recovery and readiness context of one day in one call (default today; read-only, numbers only, no readiness verdict). For the day and days_back days before: native wellness values, CTL/ATL/form/ramp rate, subjective scores, custom wellness fields with a value (e.g. Body Battery from a sync bridge), missing values and the record's update time; recorded SICK/INJURED entries; personal baselines of baseline_metrics (7-day and 42-day mean, median, SD, latest value vs baseline with z-score; small samples flagged); the activities of those days with loads and device fields; the planned events of the day. Today is flagged preliminary and a line (JSON today_completeness) names the usual fields not yet in today's record, grouped by when they usually arrive: not yet available, not normal. Trends: get_wellness_trends. Method: intervals://methods/wellness (get_guide).
get_wellness_trends읽기 전용Use for multi-day wellness trends against the athlete's own baseline (default the 42 days ending today; read-only, statistics only). Per metric with units: the daily values of the last 14 days with trailing means, period statistics, a personal baseline (the 42 days ending at end_date), the latest value vs that baseline (difference, %, z-score), rolling means, the last 7 days vs the 7 before and outliers (|z| >= 2.5). Missing days are never filled in; for physiological metrics a stored 0 counts as missing. Small samples are flagged (baseline under 14 values, correlation under 30 paired days). Weight adds a 7/14/28-day slope in kg per week. Optional correlations (Pearson, Spearman, with lag) are associations, not causes. One day in context: get_recovery_snapshot. Method: intervals://methods/wellness (get_guide).
get_nutrition_summary읽기 전용Use for food intake, calorie balance and weight trend over a period (default the 28 days ending today; read-only). Per day: logged kcal, carbohydrates, protein and fat, the device's total and active burn and balance (custom wellness fields, codes configurable) and weight. Per window (default 7/14/28 days): intake totals and means over logged days only, days without logged intake, burn mean, balance total and mean on logged days, weight change and slope in kg per week. A day without logged intake is never 0 kcal; the device burn is an estimate; a calorie balance does not measure fat change. Optionally the Intervals.icu training load per day. Method: intervals://methods/wellness (get_guide).
get_training_summary읽기 전용Use for training totals of a period grouped by ISO week, month, sport (activity type), gear or in total, including custom activity fields (read-only). Per group and in total: sessions, moving/elapsed time, distance, elevation, Intervals.icu load with the power/HR/pace load sums, time-weighted intensity, CTL/ATL/form/ramp at the end of the group's week or month, time in power (sweet spot apart) and HR zones, sport and gear splits, feel and RPE, sessions of 3 h or more, the longest session, trainer sessions. Numeric custom fields are aggregated by units and meaning: additive values summed, device loads summed apart from the Intervals.icu load, estimates as latest value and change, per-activity values as mean/median/range. Missing values are skipped, never counted as 0. Per-week view in one call: get_weekly_summary. Method: intervals://methods/summary (get_guide).
get_intensity_distribution읽기 전용Use for the training intensity distribution of a period (default the last 4 weeks, read-only): Intervals.icu's time in zones of each activity mapped to the three-zone model (Z1 below the first threshold, Z2 between, Z3 above the second). Returns Z1/Z2/Z3 shares and hours, the polarization index (Treff et al. 2019), the class (Base, Polarized, Pyramidal, Threshold, HIT) and hard sessions and days for the period, per sport family and per ISO week, and the drift between the two halves. The mapping depends on the zone basis and the zone count of the athlete's model. Activities without zone data are never counted as easy; the coverage is reported. Statistics only, no verdict. Overview: get_coach_context. Method: intervals://methods/intensity (get_guide).
get_durability읽기 전용Use for aerobic durability: Intervals.icu's aerobic decoupling (power:HR, or pace:HR for runs without power; drift between the halves in %) of steady long cycling and running sessions and the efficiency factor trend (read-only, default the last 6 weeks). Sessions pass a quality filter (min_minutes moving, few stops, HR, rides with power, variability index up to max_vi, temperature up to max_temp_c, optionally indoor or outdoor only); excluded ones are counted per reason. Per sport family: median, range, quartiles, sessions above drift_threshold_pct (5 % commonly cited) and the last recent_days against the window. Fewer than 8 qualifying sessions are flagged as a small sample; mixed indoor/outdoor, bikes/shoes or power meters are noted. Statistics only, no verdict. Per interval and bike: get_power_hr_efficiency. Method: intervals://methods/durability (get_guide).
get_long_ride_fatigue_profile읽기 전용Use to see how long rides change at matched power as work accumulates: HR, W/bpm, cadence and Garmin stamina in steady segments of a power band (default 75-85 % FTP) before vs after work thresholds. Phases by work (default 750 / 1,500 kJ, or kJ/kg) are compared with the phase before the first threshold. Threshold crossings and climbs carry the prior work (kJ, kJ/kg, kJ and time above FTP, efforts above FTP). Rides from activity_ids or the long rides of a period (default 180 days, reaching the highest threshold; limit 6, max 12). Across rides: median and range of the changes with n, small samples flagged. Statistics only, no verdict. Read-only; one stream call per ride plus 1-4 (one more per id with activity_ids). Fresh vs fatigued power curves: get_fatigue_resistance. Method: intervals://methods/fatigue (get_guide).
get_submax_test_trends읽기 전용Use to follow the submaximal fatigue tests Intervals.icu detects (#SFT) over the weeks: which are valid benchmarks and how HR responds. Lists the tests of the period (default 180 days; limit 30, max 60) with target, average, CV, end HR, efficiency factor and HR recovery (HRRc; not measured is never 0). Valid: on target, steady, not ignored and (check_context) not inside a longer work interval, not continued, not after hard riding; excluded tests carry the reason. Valid tests are trended per sport family and test type (power and pace never pooled) and ISO week: n, change, slope, SD. Statistics only, no verdict. Read-only; 2 API calls plus 2 per power test with check_context. Method: intervals://methods/fatigue (get_guide).
get_coach_context읽기 전용Use first for a weekly or general training review: load, intensity, recovery, durability and plan for one end date in one compact call (read-only, about 2-3k characters). Combines 7/28-day Intervals.icu load with acute:chronic ratio, monotony, strain and CTL/ATL/form; the three-zone intensity of 7 and 28 days; recovery markers (HRV, resting HR, sleep) against personal baselines with a z-score; durability; recorded SICK/INJURED entries; top sessions; and, when the end date is today, planned workouts of the next 7 days and the next race. For today it names wellness fields not yet recorded (not yet available, not normal). A method line states windows and rules; small samples are flagged; missing values are never 0; no verdict. Details: get_training_load, get_intensity_distribution, get_durability, get_recovery_snapshot, get_load_projection. Method: intervals://methods/load (get_guide).
preview_workout읽기 전용Use to show the athlete how a drafted workout will look before writing it: renders the workout document as Intervals.icu workout text with its totals (no API call, nothing written). Expands repeats, sums planned duration and distance, counts steps with targets and open-ended steps, and shows the text add_or_update_event would send. Full check list: validate_workout.
validate_workout읽기 전용Use before every workout write (add_or_update_event, add_events_bulk, create_library_workout) to check a drafted workout document; read-only, nothing is written. Checks durations or distances per step, repeat blocks, target units per sport and plausible values, ramps and ranges, warm-up and cool-down, the step sum against moving_time and the sport; with start_date it lists the events already on that day and flags a same-name event as a possible duplicate. Format: intervals://workout-syntax (get_guide). Show the result to the athlete before writing.
get_server_status읽기 전용Use to check the connection when tools are missing or fail: server version, enabled permission classes and tool set, registered and hidden tools, whether Intervals.icu answers, and the athlete's custom field and stream counts. The API key is never shown.
get_guide읽기 전용Use when the short tool descriptions are not enough: read the workout syntax before writing a workout, or how an analysis works (method, windows, filters, caveats). Returns the same Markdown as the resources intervals://guide, intervals://workout-syntax and intervals://methods/<topic>. Static text, no athlete data.
get_weekly_summary읽기 전용Use for a quick per-week overview from Intervals.icu's athlete summary (read-only, one API call). Per ISO week (from Monday): sessions, moving time, distance and training load, a split per sport category, time in HR zones (non-zero zones only) and CTL/ATL/form/ramp at the end of the week (the latest day with data for the current week). Sessions without HR (e.g. strength) are counted. Rows of other (followed or coached) athletes are ignored. Grouping by month, sport or gear, separate power/HR/pace loads and custom fields: get_training_summary. Method: intervals://methods/summary (get_guide).
get_plan_compliance읽기 전용Use to compare planned workouts with the activities done in a date range (read-only, two API calls). Planned workouts (calendar WORKOUT events) are linked to activities by the event's paired_activity_id or the activity's paired_event_id; each pair shows planned vs actual duration and load with the deviation in %. An activity counts for one event only. Unlinked past workouts are missed, those of today or later upcoming (athlete's local date). Activities without a planned workout are unplanned; those linked to a workout outside the range are listed apart. Completion = completed / (completed + missed). NOTE events with training availability, allowed sports or a maximum training time are listed too. Method: intervals://methods/summary (get_guide).
get_workout_library읽기 전용Use to list the athlete's workout library: folders and plans with their workouts and ids (read-only). One workout in detail: get_library_workout.
get_library_workout읽기 전용Use to read one library workout (steps, planned time, load, targets), e.g. to reuse it with add_or_update_event or validate_workout. Ids: get_workout_library.
get_wellness_data읽기 전용Use for the raw daily wellness records of a date range (default the last 30 days; read-only). Per day as stored: CTL/ATL and eFTP per sport, vitals (weight, resting HR, HRV, SpO2 ...), sleep, subjective scores, nutrition, steps and comments; include_all_fields adds every other field, custom wellness fields labelled with name and units. When the range includes today, a line names the usual fields not yet in today's record, grouped by when they usually arrive: not yet available, not normal. Long ranges are paged by day: a note gives the start_date to continue with. Baselines and trends: get_recovery_snapshot, get_wellness_trends, get_nutrition_summary. Method: intervals://methods/wellness (get_guide).
| get_activity_messages | Use to read the notes and comments on one activity: author, time, type and text of each message (read-only). | 읽기 전용 |
| get_events | Use to see the athlete's calendar: planned workouts, races, notes and other events of a date range (default today to 30 days ahead). Each event shows its category (Workout, Race A/B/C, Note ...), sport (Ride, Run ...), planned time and load, and the paired activity once it has been done. Full workout steps: get_event_by_id. Plan phases and weekly targets: get_training_plan. | 읽기 전용 |
| get_event_by_id | Use to read one calendar event completely, e.g. to read back a workout right after writing it. Returns category and sport, planned time and load, the paired activity and the full workout document (steps, planned time in zones). | 읽기 전용 |
| get_training_plan | Use for the season view: the assigned training plan, plan phases, weekly targets, races with priority and events that set the fitness model (read-only). Reads the training plan assigned to the athlete and the calendar entries of the annual plan: PLAN (phases/blocks), TARGET (weekly load, time or distance targets), RACE_A/B/C, SEASON_START, and set eFTP / set fitness and fatigue / fitness days. Default range: 30 days back to 180 days ahead. Single workouts: get_events. | 읽기 전용 |
| get_athlete_power_curves | Use for an athlete's best power per duration over whole periods: season bests, progress between seasons or date ranges. Returns watts and W/kg per duration for this season, last season and/or a custom range, each with the activity that set it. Defaults: Ride, 5 s to 60 min, both seasons; durations that are not curve points are left out. Read-only, one API call. One activity: get_best_efforts; HR and pace: get_hr_curves, get_pace_curves. Method: intervals://methods/comparisons (get_guide). | 읽기 전용 |
| get_hr_curves | Use for the highest average heart rate an athlete sustained per duration over one or more periods (e.g. comparing periods; with get_pace_curves the same pace at a lower HR). Returns bpm per duration for each curve (default the last 90 days) with the activity that set it; durations without data are listed as not available. Read-only, one API call. Power: get_athlete_power_curves. Method: intervals://methods/comparisons (get_guide). | 읽기 전용 |
| get_pace_curves | Use for an athlete's best times per distance over one or more periods: PBs, comparing periods, progress in running or swimming. Returns the best time and pace (min/km; min/100 m for Swim and OpenWaterSwim) per distance for each curve (default the last 90 days) with the activity that set it; optionally gradient-adjusted pace. Distances not on the curve are listed as not available. Read-only, one API call. HR side: get_hr_curves. Method: intervals://methods/comparisons (get_guide). | 읽기 전용 |
| get_best_efforts | Use for the peak efforts of one activity: best average power, HR or speed over durations (s) or distances (m), e.g. peak 5 s to 20 min power or the fastest km of a run (velocity_smooth with distances). Returns per effort the average (W, bpm or m/s with pace) and its position as elapsed h:mm:ss and sample indices (usable as start_index / end_index); windows spanning a recording pause are flagged. Default durations 5 s to 60 min; longer than the activity = not available. Read-only; one API call per duration or distance plus 1-2. Several activities: compare_best_efforts; period bests: get_athlete_power_curves. Method: intervals://methods/comparisons (get_guide). | 읽기 전용 |
| compare_best_efforts | Use to compare peak efforts (e.g. 1 / 5 / 20 min power) of several activities side by side: development over a block, races, or whether a new bike or power meter reads differently. Returns a matrix of activities (date, sport, gear, FTP at the time) by duration with the best average of the stream, and the best activity per duration. Activities come from activity_ids or a date range (default the last 90 days), filtered by sport and gear; newest first, limit 10 (max 25), at most 10 durations. Power meters of different bikes are not calibrated against each other; no verdict. Read-only; one API call per activity and duration (up to 250) plus the list and gear calls. One activity in detail: get_best_efforts. Method: intervals://methods/comparisons (get_guide). | 읽기 전용 |
| find_similar_intervals | Use to find earlier activities with intervals of a given length and intensity (% of FTP), or like the main set of a reference activity, ranked by comparability. Pass min/max_secs and min/max_intensity, or reference_activity_id (window from its main set: length ±25 %, intensity ±8 points of FTP; explicit values win; only the 365 days before it unless start_date is given). Returns per activity date, sport, interval summary, load, FTP at the time, gear, power meter, compliance and a comparability score 0-100 with reasons. Sport defaults to one family (other families are counted, "all" keeps every sport); watts of different power meters are not comparable, use % of FTP. Read-only; one API call (+2 with a reference, +1 gear catalog). Details: get_activity_intervals; same workout over time: compare_workouts. Method: intervals://methods/comparisons (get_guide). | 읽기 전용 |
| get_activity_histogram | Use for the time distribution of one activity independent of zone definitions: how polarised a ride was, time above FTP, the pace spread of a run. Returns the seconds and % of recorded time in each power (W), heart rate (bpm), pace or grade-adjusted pace bucket, as computed by Intervals.icu; pace and GAP buckets are speeds in m/s shown with the pace range. bucket_size applies to power and hr only. Read-only, one API call. Method: intervals://methods/comparisons (get_guide). | 읽기 전용 |
| compare_workouts | Use to compare repeated executions of the same workout over time (e.g. every 3 x 10 min threshold session) on truly comparable work intervals. Activities by name search (query), activity_ids or a date range (default the last 90 days); limit 8 (max 12). WORK intervals are split into main set (similar length and intensity), surges, other and excluded; the main set gets time-weighted power, NP, HR, max HR, cadence, W/bpm. Only activities matching the reference pattern (reference_activity_id, else the newest; length ±25 %, intensity ±8 points of FTP) are compared; trends first -> last with n (< 3 not reliable). RPE is whole-activity only; gear and power meter differences are flagged; no verdict. Read-only; one API call per activity plus 1-3 (one more per id with activity_ids). Method: intervals://methods/comparisons (get_guide). | 읽기 전용 |
| get_power_hr_efficiency | Use to track power-to-heart-rate efficiency (W per bpm at the same power) over weeks. Puts every WORK interval of at least min_interval_secs with power and HR into the power band of its average power; returns per activity and band the count and time-weighted W, HR and W/bpm, and per band the oldest vs the newest group of activities (each counts once; at least 3 per group, else not reliable) compared with the day-to-day SD. Default the last 90 days of rides, limit 30 (max 60); trends per gear when several power meters are involved; filters for gear, indoor/outdoor and interval start time. Heat, fatigue, cadence and sensors move the ratio: statistics only, no fitness verdict. Read-only; one API call per activity plus 2. Method: intervals://methods/comparisons (get_guide). | 읽기 전용 |
| get_fatigue_resistance | Use for fatigue resistance: best power fresh vs after the athlete's work thresholds kJ0 / kJ1 (Intervals.icu fatigued power curves). Reads the sport settings first. When they hold no kJ thresholds no fatigued values are shown: the tool explains the setting and (suggest_thresholds) proposes thresholds from body mass and recent rides, never saved. Otherwise returns watts per duration fresh and after kJ0 / kJ1 with the change in %, for one activity or for athlete curves (default 42d); a fatigued curve without data is reported as missing, one equal to fresh as identical, without a change. Read-only, 2-5 API calls. Within one long ride: get_long_ride_fatigue_profile. Method: intervals://methods/comparisons (get_guide). | 읽기 전용 |
| compare_power_streams | Use to compare two power meters recorded on the same ride (watts vs secondary_power by default), on one ride or across several rides. One ride (activity_id): offset in W and % (secondary - primary), per power band, in stable 30/60 s windows, drift over the ride quarters, lag, best efforts of each stream and the samples excluded as coasting, missing or outliers. Several rides (no activity_id, or activity_ids): the rides that carry the second stream (default 180 days to end_date, newest first, limit 10, max 20), each compared on its own and summarised per bike and power meter with median, between-ride SD and range. No calibration and no correction factor; sensors are named only from the file's device data. Read-only. Method: intervals://methods/power-meters (get_guide). | 읽기 전용 |
| analyze_workout_execution | Use to check how a planned workout was executed, or without a plan to evaluate each detected interval of one activity. The plan comes from planned_workout_doc, event_id or the event paired with the activity. Planned steps (repeats expanded) are aligned with the intervals by order, duration or distance and target intensity, never by names; laps that split one effort are merged. Per step: planned vs actual moving time, target (W, bpm or pace) vs actual, time in target, HR response, cadence, fade, Pw:HR drift (work steps of 10 min or more) and custom stream changes, with deviation notes and an alignment confidence. Time past a step's plan and training after the plan are reported apart. Unpaired: up to three candidate events, nothing is paired. Read-only. Method: intervals://methods/execution (get_guide). | 읽기 전용 |
| analyze_climbs | Use for activities without useful intervals (tours, mountain hikes, trail runs) to split the recording into climbs, descents, sections in between and pauses. Per segment: time and sample indices, moving time, distance, gain/loss, average and steepest grade, VAM, speed, power, NP, HR, cadence and start/end/min/max/mean/delta of every custom stream. Defaults follow the sport (foot vs bike); implausible grades are flagged and each segment gets a grade confidence. Slow scrambling counts as moving, real pauses as pause. Climb gains are not the activity's total elevation gain. Text lists up to max_segments segments. Read-only, 2 API calls (activity, all streams). Method: intervals://methods/climbs (get_guide). | 읽기 전용 |
| get_training_load | Use for acute and chronic training load in detail: acute (default 7 d) and chronic (28 d) Intervals.icu load, acute:chronic ratio (coupled daily means), Foster monotony and strain, deload-like weeks, per sport family with the primary sport, ISO weeks, and CTL/ATL/form/ramp at the end date (read-only). Rest days count as 0; sessions without a load are counted, not added. Device loads (custom fields such as a Garmin training load) are listed apart on their own scale, never added. With the default end date and nothing recorded today yet, the windows end yesterday. Reference ranges (ACWR 0.8-1.3, monotony > 2.0) are shown with sources as context; small samples are flagged; no verdict. Overview: get_coach_context; planned load: get_load_projection. Method: intervals://methods/load (get_guide). | 읽기 전용 |
| get_load_projection | Use for future fitness: CTL, ATL and form projected over the planned workouts in the calendar, or a what-if scenario (sessions or weekly templates not in the calendar) against the calendar plan (read-only, nothing is written). Starts from Intervals.icu's CTL/ATL at the end of yesterday plus today's completed load; planned workouts without a load are reported, not guessed. Returns end values, lowest form, highest ramp, ISO weeks with plan statistics, race days, Intervals.icu's own projection, a model check and weeks outside commonly cited ranges (ramp 5-8 CTL/week, monotony > 2.0, no rest day). With target_date, target_form or a scenario: the target day (default the next RACE_A) at the start of the day; target_form adds a search for the load of the last taper_days that reaches it. Arithmetic, not a forecast; no verdict. Method and scenario format: intervals://methods/load (get_guide). | 읽기 전용 |
| get_activity_data_audit | Use to check where an activity's data came from and what is missing, or without activity_id how complete the data of a period is. One activity: source (sync, upload, Strava stub), upload and analysis times, filtered duplicates, recording stops, FIT laps vs intervals and edits, sensors, streams vs those usual for the sport with coverage, custom fields with value / zero placeholder / none, fields the Garmin Intervals Bridge could fill. Period (default 28 days to end_date): per sport how many activities have power, HR, GPS, weather, custom streams and fields. Facts and counts, no verdict; read-only, 1-3 API requests. Method: intervals://methods/activity-data (get_guide). | 읽기 전용 |
| get_activity_report | Use first for any question about one activity: overview, plan vs execution, power meter check, climbs and data quality in one call (read-only, 3-4 API requests). The overview has thresholds, device, sport-assigned custom fields, fueling, weather and W′ balance. With a paired event or planned_workout_doc the plan-vs-execution analysis follows (as analyze_workout_execution), otherwise the intervals; a second-power-meter check only with enough valid paired samples; climbs without intervals or above 500 m gain; then data-quality notes. compact = core numbers and up to 5 key findings. Full detail: get_activity_details, analyze_workout_execution, compare_power_streams, analyze_climbs, get_activity_data_audit. Methods: intervals://methods/activity-data, intervals://methods/execution (get_guide). | 읽기 전용 |
| get_fueling_analysis | Use for carbohydrate, fluid and sodium intake of one activity (activity_id) or of the long sessions of a period (default the last 90 days, sessions of at least min_minutes; read-only). Carbs used (Intervals.icu estimate) and ingested (logged total) in g and g/h, the ingested share of used, kcal and kJ, and fluid intake, sodium and sweat loss per hour where custom fields exist (found by units and name). One activity also gets the intake per hour from a custom intake stream, if there is one. Period: statistics per sport family, by duration and by intensity, Spearman correlations from 8 sessions, with sample sizes. Not logged is never 0; used minus ingested is no 1:1 energy deficit; no targets. Method: intervals://methods/fueling (get_guide). | 읽기 전용 |
| get_recovery_snapshot | Use for the recovery and readiness context of one day in one call (default today; read-only, numbers only, no readiness verdict). For the day and days_back days before: native wellness values, CTL/ATL/form/ramp rate, subjective scores, custom wellness fields with a value (e.g. Body Battery from a sync bridge), missing values and the record's update time; recorded SICK/INJURED entries; personal baselines of baseline_metrics (7-day and 42-day mean, median, SD, latest value vs baseline with z-score; small samples flagged); the activities of those days with loads and device fields; the planned events of the day. Today is flagged preliminary and a line (JSON today_completeness) names the usual fields not yet in today's record, grouped by when they usually arrive: not yet available, not normal. Trends: get_wellness_trends. Method: intervals://methods/wellness (get_guide). | 읽기 전용 |
| get_wellness_trends | Use for multi-day wellness trends against the athlete's own baseline (default the 42 days ending today; read-only, statistics only). Per metric with units: the daily values of the last 14 days with trailing means, period statistics, a personal baseline (the 42 days ending at end_date), the latest value vs that baseline (difference, %, z-score), rolling means, the last 7 days vs the 7 before and outliers (|z| >= 2.5). Missing days are never filled in; for physiological metrics a stored 0 counts as missing. Small samples are flagged (baseline under 14 values, correlation under 30 paired days). Weight adds a 7/14/28-day slope in kg per week. Optional correlations (Pearson, Spearman, with lag) are associations, not causes. One day in context: get_recovery_snapshot. Method: intervals://methods/wellness (get_guide). | 읽기 전용 |
| get_nutrition_summary | Use for food intake, calorie balance and weight trend over a period (default the 28 days ending today; read-only). Per day: logged kcal, carbohydrates, protein and fat, the device's total and active burn and balance (custom wellness fields, codes configurable) and weight. Per window (default 7/14/28 days): intake totals and means over logged days only, days without logged intake, burn mean, balance total and mean on logged days, weight change and slope in kg per week. A day without logged intake is never 0 kcal; the device burn is an estimate; a calorie balance does not measure fat change. Optionally the Intervals.icu training load per day. Method: intervals://methods/wellness (get_guide). | 읽기 전용 |
| get_training_summary | Use for training totals of a period grouped by ISO week, month, sport (activity type), gear or in total, including custom activity fields (read-only). Per group and in total: sessions, moving/elapsed time, distance, elevation, Intervals.icu load with the power/HR/pace load sums, time-weighted intensity, CTL/ATL/form/ramp at the end of the group's week or month, time in power (sweet spot apart) and HR zones, sport and gear splits, feel and RPE, sessions of 3 h or more, the longest session, trainer sessions. Numeric custom fields are aggregated by units and meaning: additive values summed, device loads summed apart from the Intervals.icu load, estimates as latest value and change, per-activity values as mean/median/range. Missing values are skipped, never counted as 0. Per-week view in one call: get_weekly_summary. Method: intervals://methods/summary (get_guide). | 읽기 전용 |
| get_intensity_distribution | Use for the training intensity distribution of a period (default the last 4 weeks, read-only): Intervals.icu's time in zones of each activity mapped to the three-zone model (Z1 below the first threshold, Z2 between, Z3 above the second). Returns Z1/Z2/Z3 shares and hours, the polarization index (Treff et al. 2019), the class (Base, Polarized, Pyramidal, Threshold, HIT) and hard sessions and days for the period, per sport family and per ISO week, and the drift between the two halves. The mapping depends on the zone basis and the zone count of the athlete's model. Activities without zone data are never counted as easy; the coverage is reported. Statistics only, no verdict. Overview: get_coach_context. Method: intervals://methods/intensity (get_guide). | 읽기 전용 |
| get_durability | Use for aerobic durability: Intervals.icu's aerobic decoupling (power:HR, or pace:HR for runs without power; drift between the halves in %) of steady long cycling and running sessions and the efficiency factor trend (read-only, default the last 6 weeks). Sessions pass a quality filter (min_minutes moving, few stops, HR, rides with power, variability index up to max_vi, temperature up to max_temp_c, optionally indoor or outdoor only); excluded ones are counted per reason. Per sport family: median, range, quartiles, sessions above drift_threshold_pct (5 % commonly cited) and the last recent_days against the window. Fewer than 8 qualifying sessions are flagged as a small sample; mixed indoor/outdoor, bikes/shoes or power meters are noted. Statistics only, no verdict. Per interval and bike: get_power_hr_efficiency. Method: intervals://methods/durability (get_guide). | 읽기 전용 |
| get_long_ride_fatigue_profile | Use to see how long rides change at matched power as work accumulates: HR, W/bpm, cadence and Garmin stamina in steady segments of a power band (default 75-85 % FTP) before vs after work thresholds. Phases by work (default 750 / 1,500 kJ, or kJ/kg) are compared with the phase before the first threshold. Threshold crossings and climbs carry the prior work (kJ, kJ/kg, kJ and time above FTP, efforts above FTP). Rides from activity_ids or the long rides of a period (default 180 days, reaching the highest threshold; limit 6, max 12). Across rides: median and range of the changes with n, small samples flagged. Statistics only, no verdict. Read-only; one stream call per ride plus 1-4 (one more per id with activity_ids). Fresh vs fatigued power curves: get_fatigue_resistance. Method: intervals://methods/fatigue (get_guide). | 읽기 전용 |
| get_submax_test_trends | Use to follow the submaximal fatigue tests Intervals.icu detects (#SFT) over the weeks: which are valid benchmarks and how HR responds. Lists the tests of the period (default 180 days; limit 30, max 60) with target, average, CV, end HR, efficiency factor and HR recovery (HRRc; not measured is never 0). Valid: on target, steady, not ignored and (check_context) not inside a longer work interval, not continued, not after hard riding; excluded tests carry the reason. Valid tests are trended per sport family and test type (power and pace never pooled) and ISO week: n, change, slope, SD. Statistics only, no verdict. Read-only; 2 API calls plus 2 per power test with check_context. Method: intervals://methods/fatigue (get_guide). | 읽기 전용 |
| get_coach_context | Use first for a weekly or general training review: load, intensity, recovery, durability and plan for one end date in one compact call (read-only, about 2-3k characters). Combines 7/28-day Intervals.icu load with acute:chronic ratio, monotony, strain and CTL/ATL/form; the three-zone intensity of 7 and 28 days; recovery markers (HRV, resting HR, sleep) against personal baselines with a z-score; durability; recorded SICK/INJURED entries; top sessions; and, when the end date is today, planned workouts of the next 7 days and the next race. For today it names wellness fields not yet recorded (not yet available, not normal). A method line states windows and rules; small samples are flagged; missing values are never 0; no verdict. Details: get_training_load, get_intensity_distribution, get_durability, get_recovery_snapshot, get_load_projection. Method: intervals://methods/load (get_guide). | 읽기 전용 |
| preview_workout | Use to show the athlete how a drafted workout will look before writing it: renders the workout document as Intervals.icu workout text with its totals (no API call, nothing written). Expands repeats, sums planned duration and distance, counts steps with targets and open-ended steps, and shows the text add_or_update_event would send. Full check list: validate_workout. | 읽기 전용 |
| validate_workout | Use before every workout write (add_or_update_event, add_events_bulk, create_library_workout) to check a drafted workout document; read-only, nothing is written. Checks durations or distances per step, repeat blocks, target units per sport and plausible values, ramps and ranges, warm-up and cool-down, the step sum against moving_time and the sport; with start_date it lists the events already on that day and flags a same-name event as a possible duplicate. Format: intervals://workout-syntax (get_guide). Show the result to the athlete before writing. | 읽기 전용 |
| get_server_status | Use to check the connection when tools are missing or fail: server version, enabled permission classes and tool set, registered and hidden tools, whether Intervals.icu answers, and the athlete's custom field and stream counts. The API key is never shown. | 읽기 전용 |
| get_guide | Use when the short tool descriptions are not enough: read the workout syntax before writing a workout, or how an analysis works (method, windows, filters, caveats). Returns the same Markdown as the resources intervals://guide, intervals://workout-syntax and intervals://methods/<topic>. Static text, no athlete data. | 읽기 전용 |
| get_weekly_summary | Use for a quick per-week overview from Intervals.icu's athlete summary (read-only, one API call). Per ISO week (from Monday): sessions, moving time, distance and training load, a split per sport category, time in HR zones (non-zero zones only) and CTL/ATL/form/ramp at the end of the week (the latest day with data for the current week). Sessions without HR (e.g. strength) are counted. Rows of other (followed or coached) athletes are ignored. Grouping by month, sport or gear, separate power/HR/pace loads and custom fields: get_training_summary. Method: intervals://methods/summary (get_guide). | 읽기 전용 |
| get_plan_compliance | Use to compare planned workouts with the activities done in a date range (read-only, two API calls). Planned workouts (calendar WORKOUT events) are linked to activities by the event's paired_activity_id or the activity's paired_event_id; each pair shows planned vs actual duration and load with the deviation in %. An activity counts for one event only. Unlinked past workouts are missed, those of today or later upcoming (athlete's local date). Activities without a planned workout are unplanned; those linked to a workout outside the range are listed apart. Completion = completed / (completed + missed). NOTE events with training availability, allowed sports or a maximum training time are listed too. Method: intervals://methods/summary (get_guide). | 읽기 전용 |
| get_workout_library | Use to list the athlete's workout library: folders and plans with their workouts and ids (read-only). One workout in detail: get_library_workout. | 읽기 전용 |
| get_library_workout | Use to read one library workout (steps, planned time, load, targets), e.g. to reuse it with add_or_update_event or validate_workout. Ids: get_workout_library. | 읽기 전용 |
| get_wellness_data | Use for the raw daily wellness records of a date range (default the last 30 days; read-only). Per day as stored: CTL/ATL and eFTP per sport, vitals (weight, resting HR, HRV, SpO2 ...), sleep, subjective scores, nutrition, steps and comments; include_all_fields adds every other field, custom wellness fields labelled with name and units. When the range includes today, a line names the usual fields not yet in today's record, grouped by when they usually arrive: not yet available, not normal. Long ranges are paged by day: a note gives the start_date to continue with. Baselines and trends: get_recovery_snapshot, get_wellness_trends, get_nutrition_summary. Method: intervals://methods/wellness (get_guide). | 읽기 전용 |
구성
API_KEY필수비밀Intervals.icu API key (Settings > Developer Settings)
API_KEY필수비밀Intervals.icu API key (Settings > Developer Settings)
ATHLETE_ID필수Intervals.icu athlete ID
ATHLETE_ID필수Intervals.icu athlete ID
ATHLETE_TIMEZONETime zone for 'today' and default date ranges, e.g. Europe/Vienna; default: the Intervals.icu athlete profile
ATHLETE_TIMEZONETime zone for 'today' and default date ranges, e.g. Europe/Vienna; default: the Intervals.icu athlete profile
INTERVALS_OAUTH_CLIENT_IDMCP_AUTHMCP_PERMISSIONSEnabled tool classes: read (default, read-only), read,write, or all (adds destructive and admin tools)
MCP_PERMISSIONSEnabled tool classes: read (default, read-only), read,write, or all (adds destructive and admin tools)
MCP_TENANCYMCP_TOOLSETfull (every tool of the enabled classes) or core (curated coaching set)
MCP_TOOLSETfull (every tool of the enabled classes) or core (curated coaching set)
MCP_TRANSPORTOAUTH_ALLOWED_ATHLETESOAUTH_LOGINOAUTH_TOKEN_KEY_FILE
| 이름 | 설명 | 유형 |
|---|---|---|
| API_KEY | Intervals.icu API key (Settings > Developer Settings) | 필수비밀 |
| API_KEY | Intervals.icu API key (Settings > Developer Settings) | 필수비밀 |
| ATHLETE_ID | Intervals.icu athlete ID | 필수 |
| ATHLETE_ID | Intervals.icu athlete ID | 필수 |
| ATHLETE_TIMEZONE | Time zone for 'today' and default date ranges, e.g. Europe/Vienna; default: the Intervals.icu athlete profile | |
| ATHLETE_TIMEZONE | Time zone for 'today' and default date ranges, e.g. Europe/Vienna; default: the Intervals.icu athlete profile | |
| INTERVALS_OAUTH_CLIENT_ID | — | |
| MCP_AUTH | — | |
| MCP_PERMISSIONS | Enabled tool classes: read (default, read-only), read,write, or all (adds destructive and admin tools) | |
| MCP_PERMISSIONS | Enabled tool classes: read (default, read-only), read,write, or all (adds destructive and admin tools) | |
| MCP_TENANCY | — | |
| MCP_TOOLSET | full (every tool of the enabled classes) or core (curated coaching set) | |
| MCP_TOOLSET | full (every tool of the enabled classes) or core (curated coaching set) | |
| MCP_TRANSPORT | — | |
| OAUTH_ALLOWED_ATHLETES | — | |
| OAUTH_LOGIN | — | |
| OAUTH_TOKEN_KEY_FILE | — |
자동 검사
2026년 11월 16일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능futureweb/intervals-mcp-server is public and reachablegithub.com/futureweb/intervals-mcp-server ↗통과
- 패키지가 이 저장소를 소스로 명시futureweb-intervals-mcp names futureweb/intervals-mcp-server as sourcepypi.org/project/futureweb-intervals-mcp/ ↗통과
- 빌드 출처(Sigstore 증명)Sigstore attestation for futureweb-intervals-mcppypi.org/project/futureweb-intervals-mcp/ ↗통과
- 오픈 소스 라이선스 (OSI)GPL-3.0spdx.org/licenses/GPL-3.0.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-01github.com/futureweb/intervals-mcp-server ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음No popular package one edit away from futureweb-intervals-mcp통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음31 resolved dependencies checked; no critical advisoryosv.dev ↗통과
- 모델에 대한 숨겨진 지침 없음52 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨No tool named like delete, drop or exec통과
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기Futureweb Intervals MCP
Advanced Intervals.icu MCP server for ChatGPT, Claude and every MCP client: Garmin-enriched metrics, every custom field and stream, recovery insights and endurance performance analysis.
A Model Context Protocol server that lets AI assistants read and analyse your Intervals.icu training data the way a coach would: activities with every custom field and stream, intervals, wellness against personal baselines, thresholds and zones, planned-versus-executed workouts, climbs, dual power meters, best efforts, efficiency and fatigue resistance, nutrition and weight, training summaries and the calendar. It runs where you run it, talks only to the Intervals.icu API and exposes nothing that writes unless you enable it.
Continuation of mvilanova/intervals-mcp-server. The original project is no longer actively developed (last commit on 2 August 2026, 29 pull requests left open). This community-maintained fork carries it on: the useful open pull requests were reviewed and merged with their authors credited, the bugs fixed, and the server rebuilt around coaching analysis, Garmin data and safe remote access. Not affiliated with Intervals.icu or Garmin.
Companion project: the Garmin Intervals Bridge puts back the metrics Garmin strips from the files it sends to Intervals.icu (stamina, training effect, recovery time, VO₂max, running dynamics, sleep and HRV details …). This MCP is built to read all of it, but works just as well without the bridge.
For the mountains: intervals-summits writes the summits, huts and
passes of your activities into custom fields (Summits, SummitCount). This MCP reads them like
any other field, so your assistant knows which summits a tour reached: ask which ones you climbed
this year, or how often.
Contents
- Highlights
- Works with the Garmin Intervals Bridge
- Tools
- Quick start
- Route-aware outdoor workouts
- Connect an AI client
- Sharing the server with friends
- Configuration
- Permissions and security
- Project status and roadmap
- Documentation
- Development
- Credits and license
Highlights
- Every custom item, resolved dynamically. Custom activity fields, interval fields, streams and wellness fields are read from your own definitions and reported with name, code, value and units. Nothing device-specific is hard-coded; null, NaN, zero and absent stay distinct, fields that do not belong to the sport are kept apart, and device loads are never mixed with the Intervals.icu load.
- Streams at full resolution. Any stream as summary, CSV or JSON, sliced by index or time, downsampled and paged, plus per-interval statistics of any stream (for example the stamina drop of each interval).
- Coaching analysis instead of raw dumps. One-call activity report, planned versus executed per step (also for deleted events and rides extended beyond the plan), climbs and descents, second power meter check, best efforts, similar intervals, repeated workouts over time, power-to-heart-rate efficiency, fatigue resistance, training load (acute:chronic ratio, monotony, strain), three-zone intensity distribution with polarization index, aerobic durability, load projection over the plan, recovery snapshot with 42-day baselines, wellness trends and correlations, nutrition and weight trends, weekly and monthly summaries. Statistics with their sample sizes; the interpretation stays with the coach.
- Token-efficient.
detail_level(compact,standard,full) andoutput_format="json"on the heavy tools, a compact tool catalogue (about 23k tokens for read and write, an optional core set of about 10k), 13 ready-made coaching prompts and method guides as MCP resources and throughget_guide. - Safe remote access. Built-in OAuth 2.1 server with "Continue with Intervals.icu"
sign-in, a consent page with per-connection permissions, client metadata documents with
private_key_jwt(ChatGPT), PKCE and RFC 9207. Streamable HTTP (/mcp) and SSE from one process. - Safe, verifiable writes. Workouts are validated before they are written,
dry_runshows the exact request, a second identical event on the same day is refused, and every write reads back what Intervals.icu stored and parsed. - Route-aware outdoor workouts. Steps that end on the lap button (
until_lap_press) let you start the next interval where the road suits it, e.g. at the foot of a climb, while the work steps stay timed. Confirmed on a Garmin Edge 1040 on the bike (see below). - Read-only by default. Tools are grouped into permission classes (
read,write,destructive,admin) enforced on the server; onlyreadis active unless you enable more. - Tested. More than 1,100 tests on synthetic data, ruff, mypy, CodeQL, pinned GitHub Actions, build and Docker smoke tests on every pull request.
Works with the Garmin Intervals Bridge
Garmin device ──► Garmin Connect ──► official sync ──► Intervals.icu activity (filtered FIT)
│ ▲
└── Garmin Intervals Bridge ──────────┘ restores custom fields, streams, wellness
│
Futureweb Intervals MCP (this project)
│
ChatGPT / Claude / any MCP client
The Garmin Intervals Bridge writes the metrics Garmin filters out into the custom activity fields, custom streams and wellness fields you defined in Intervals.icu. The MCP reads those definitions at run time, so every restored value shows up in the tools automatically:
| Restored by the bridge | Where the MCP shows it |
|---|---|
| Training effect, EPOC, Garmin training load, recovery time, VO₂max, performance condition, stamina start/end, sweat loss, temperatures | get_activity_details, get_activity_report, get_training_summary, get_training_load (device loads apart from the Intervals.icu load), get_fueling_analysis (sweat loss per hour), get_activity_data_audit (which fields still hold a zero placeholder or no value) |
| Stamina and potential stamina, second power meter, grade-adjusted speed, gear selection, running dynamics streams | get_activity_streams, get_activity_intervals, analyze_workout_execution, analyze_climbs, compare_power_streams |
| Night SpO₂, respiration, sleeping HR, HRV details, Body Battery, sleep stages and stress, readiness, nutrition | get_wellness_data, get_recovery_snapshot, get_wellness_trends, get_nutrition_summary |
The MCP never contacts Garmin; the bridge is optional and other devices or sync tools that fill custom items get the same treatment. Worked examples and notes on reading the device metrics correctly: docs/GARMIN_BRIDGE.md.
Tools
67 tools; 52 of them only read. Write tools are marked ✎ (write), ✖ (destructive) or
⚙ (admin) and are hidden unless their class is enabled. Most tools accept output_format="json"
and detail_level (compact first). Tools never take an API key: credentials come only from
the server environment.
The catalogue is kept small for the AI client: short descriptions that say when to use a tool,
a description and (where the values are fixed) an enum for every parameter, and text results
without a duplicate structured copy. Method details and the workout format live in MCP resources
(intervals://methods/<topic>, intervals://workout-syntax) and in get_guide(topic) for clients
that only call tools. tools/list is about 22.7k tokens at MCP_PERMISSIONS=read,write
(was 42.0k; cl100k); see Tool sets for a smaller set.
Activity analysis
| Tool | What it does |
|---|---|
get_activity_report |
Complete analysis in one call: overview with fueling (carbs used/ingested per hour, sweat loss, energy), weather (temperature, feels-like, wind, head/tailwind share) and W′ balance (max depletion, time below 75/50/25 % of W′), plan vs execution or intervals, second power meter check, climbs, data-quality notes (source, upload and analysis times, recording stops, zero placeholders); include_route_history compares earlier activities on the same Intervals.icu route (time, power, W/kg, HR, weather, stamina); detail_level compact (core numbers, one context line and key findings, about 2-2.5k characters), standard or full |
get_activity_data_audit |
Provenance and data quality of one activity: source and file (Garmin sync, Garmin export or bridge upload, Strava stub), upload and analysis times, filtered duplicates, recording stops and gaps, FIT laps vs intervals and manual edits, device and sensor identity, streams usual for the sport but missing, per-stream coverage, custom fields with value / zero placeholder / none and what the Garmin Intervals Bridge could fill; without an activity, the per-sport data coverage of a period |
analyze_workout_execution |
Planned vs executed per step (duration, target adherence, time in range, HR response, fade, Pw:HR drift with the Intervals.icu decoupling sign, stamina). A step may span any number of laps; with device auto-laps step boundaries inside laps are placed at the intensity change (lap presses are kept), steps without a lap of their own are found between their neighbours, and a caveat with alignment_confidence says how far per-step results can be trusted. Open-ended targets (top zone) are lower bounds, distance steps are compared on distance. Steps are capped at their planned duration, longer intervals are split for the analysis, and riding beyond the plan is reported separately with its load and extra efforts. Tolerances for start shift, pauses and step length; planned_workout_doc for deleted events; matching events suggested read-only |
analyze_climbs |
Climbs, descents and pauses with power, NP, HR, VAM and custom streams per segment; grade smoothed over a distance window (raw grade optional), grade confidence high/medium/low per segment (no grade below the minimum horizontal distance, raw included), real pauses vs slow movement, sport profiles for riding, running and hiking, data-quality flags |
compare_power_streams |
Sample-aligned comparison of two power meters: offset, power bands, stable windows, drift, lag; without activity_id (date range or activity_ids) every ride with a second power stream is compared on its own and summarised per bike, indoor/outdoor, primary meter and second power source with n, median, between-ride SD and range (overall, per power band, stable windows), drift, lag, outliers and rides far from the median; never a correction factor |
get_best_efforts |
Best efforts of one activity for durations or distances, with their elapsed-time windows (end index exclusive); windows across a recording pause are flagged |
get_activity_histogram |
Time distribution of power, heart rate, pace or GAP |
Activities and streams
| Tool | What it does |
|---|---|
get_activities |
List with sport, gear and power meter filters, sorting, paging, compact or JSON output; without start_date the 30 days before end_date (or today) |
get_activity_details |
Summary, thresholds used (FTP, eFTP, LTHR, zones), device and power meter, running dynamics, every custom field with units, fueling, weather, W′ balance and source/freshness |
get_activity_intervals |
Intervals and groups, custom interval fields, per-interval statistics of any stream, optionally the planned step type next to the Intervals.icu type |
list_activity_streams, get_activity_streams |
Discover and fetch any stream: summary, CSV or JSON, slicing, downsampling, paging (2000 samples per page by default) |
get_activity_messages, add_activity_message ✎, update_activity ✎ |
Notes and comments, RPE, feel, name, description (dry_run shows the exact request) |
Performance over time
| Tool | What it does |
|---|---|
compare_best_efforts |
Best efforts across activities (ids, date range, sport, gear) side by side; ids are de-duplicated and capped to the limit before any request |
find_similar_intervals |
Activities with comparable intervals, from a reference activity or a given length and intensity; same sport family by default, ranked by comparability, with gear and power meter context; with a reference the 365 days before it by default (window shown, start_date for any range) |
compare_workouts |
Repeated workouts over time, comparing only comparable work intervals (reference activity, sport family, length, intensity, reps, FTP range); the reference activity is always fetched and always the pattern, with a name search the 365 days before it are listed; surges kept apart, time-weighted means, power, HR, cadence and whole-activity RPE trends, gear and power meter flags |
get_power_hr_efficiency |
Watts per heartbeat per power band and bike over time, with minimum sample sizes and filters for gear, indoor/outdoor and interval position |
get_fatigue_resistance |
Best power fresh vs after the athlete's kJ thresholds; without configured thresholds it explains the setting and suggests values instead of showing pseudo results |
get_long_ride_fatigue_profile |
HR, W/bpm, cadence and Garmin stamina at matched power in steady segments before vs after work thresholds (default 750 / 1,500 kJ, or kJ/kg), for given rides or the long rides of a period; prior work at every threshold and climb (kJ, kJ/kg, kJ and time above FTP, efforts above FTP), climbs after N hours with stamina at start and end, median and range across rides, method stated, small samples flagged |
get_submax_test_trends |
Submaximal fatigue tests detected by Intervals.icu (#SFT) with a validity filter (target tolerance, CV, ignored, detected inside a regular workout, hard riding before, optional HR recovery) and reasons for every excluded test; HR at the end, efficiency factor, HRRc and HR course trended per sport family and test type (power and pace never pooled) and ISO week over the valid tests only |
get_training_load |
Acute and chronic load, acute:chronic ratio, Foster monotony and strain (rest days as 0), deload-like weeks, per sport with the primary sport, ISO week table, CTL/ATL/form/ramp; device loads kept separate; reference ranges with sources, no verdict |
get_intensity_distribution |
Three-zone distribution from power, HR or pace zones (mapping by zone count; GAP zone times where Intervals.icu uses them), polarization index after Treff et al. 2019, class, hard sessions and days, drift between the halves, per sport and week, zone coverage, a caveat when totals mix power and HR zones |
get_durability |
Aerobic decoupling of steady long sessions after a quality filter (excluded sessions per reason), median and count above 5 %, recent vs window with a stability band, efficiency factor trend; qualifying share per sport, fewer than 8 sessions flagged, mixed indoor/outdoor, bikes or power meters pointed out; heat filter on the device sensor or the activity's weather / feels-like temperature (temperature_source), sessions list both temperatures |
get_load_projection |
CTL, ATL and form projected over the planned workouts (42/7-day model), missing planned loads reported, race days, Intervals.icu's own projection and a model check for comparison; says prominently when nothing is planned. What-if simulation (scenario): sessions or weekly templates that are not in the calendar (load given or estimated as hours x IF² x 100), added to or replacing the plan, compared with the calendar plan; form at a target day or the next RACE_A and a grid search for the load of the last days that reaches a given form range; per-week plan statistics (ramp, monotony, longest session, rest days) with commonly cited ranges and sources. Nothing is written |
get_athlete_power_curves, get_hr_curves, get_pace_curves |
Season and date-range curves |
get_training_summary |
Totals per week, month, sport or gear with the Intervals.icu load (power, else HR, else pace per activity) and the overlapping per-method sums, time in power zones (sweet spot apart) and HR zones, CTL/ATL at the end of each week or month; custom fields aggregated by units and meaning (sums only where they make sense, otherwise mean, median, range or change); an explicit detail_level also selects the JSON parts (without it the JSON is complete) |
get_weekly_summary, get_plan_compliance |
Weekly review and planned-vs-done overview |
Wellness and recovery
| Tool | What it does |
|---|---|
get_recovery_snapshot |
Today and the previous days, 42-day baselines, recent load and planned sessions in one call; names the usual wellness fields today's record does not have yet (not yet available, not normal); health markers: SICK/INJURED calendar entries on the day or ended in the 14 days before and a wellness injury score of 3-4, as recorded, with a hint to ask the athlete before planning intensity (no assessment, nothing skipped) |
get_coach_context |
Recommended first call for a weekly analysis: overview in about 2-2.5k characters with load, fitness, intensity distribution (per-sport split when zone bases mix), HRV / resting HR / sleep 7-day means against the 42 days before them (z against the week-to-week spread of the prior 90 days), durability, recorded SICK/INJURED entries (health markers, as in get_recovery_snapshot), top sessions, the plan of the next 7 days, today's not-yet-available wellness fields and a method line (windows, coupled ACWR, threshold_as, hard-session rule); an explicit detail_level also selects the JSON parts (without it the JSON is complete) |
get_wellness_trends |
Rolling means, baselines, outliers, week-over-week changes, correlations, eFTP per sport; requested period, lookback and baseline window stated separately, small samples flagged |
get_nutrition_summary |
Intake, device burn, energy balance on logged days, weight trend, training load per day |
get_fueling_analysis |
Fueling of one activity or the long sessions of a period: carbs used (Intervals.icu estimate) and ingested per moving hour, ingested share of used, energy, fluid intake, sodium and sweat loss from custom fields found by units and name (device-file zeros treated as placeholders); per sport family, and within it per duration and intensity, with sample sizes, logging coverage and Spearman correlations from 8 sessions; no targets |
get_wellness_data, update_wellness ✎ |
Daily records (include_all_fields adds every custom wellness field; without start_date the 30 days before end_date or today), with a line naming the usual fields today's record does not have yet (night/morning values, daily metrics such as VO2max or endurance score, and day totals apart); subjective scores (dry_run shows the exact request) |
Athlete, gear, calendar and workouts
| Tool | What it does |
|---|---|
get_athlete_profile, get_sport_settings, get_training_zones |
Profile, per-sport thresholds, zones with absolute ranges |
update_sport_settings ⚙ |
Validated change of FTP, LTHR, max HR or threshold pace (pace with its unit, e.g. 4:30/km); dry_run shows the request with the current values |
get_gear_list, get_gear_details |
Bikes, shoes and components with mileage and maintenance reminders |
get_events, get_event_by_id, get_training_plan |
Calendar with the full workout document; plan phases, weekly targets, races |
validate_workout, preview_workout |
Check and render a workout document before writing it, including lap-press steps (count and planning estimate) |
add_or_update_event ✎, add_or_update_note ✎, add_events_bulk ⚙, delete_event ✖, delete_events_by_date_range ✖ |
Calendar changes: workouts are validated before they are written, dry_run returns the exact request, a new event is refused when that day already has the same one (allow_duplicate), the answer reads back what Intervals.icu stored and parsed (steps parsed vs sent, parse warnings); deletions name what was deleted; the range delete previews by default |
get_workout_library, get_library_workout, create_library_workout ✎, add_event_from_library ✎, delete_library_workout ✖ |
Workout library (dry run, duplicate check when scheduling, read-back, deletions name what was deleted) |
Custom items and server
| Tool | What it does |
|---|---|
get_custom_items, get_custom_item_by_id, create_custom_item ⚙, update_custom_item ⚙, delete_custom_item ✖ |
Custom field, stream and chart definitions (create_custom_item and update_custom_item with dry_run; update: the content after the merge) |
get_server_status |
Version, enabled permissions, tool set, hidden tools, transport and sign-in mode, API check (also --doctor) |
get_guide |
Usage guide, workout syntax and method guides (the resources below) for clients that only call tools |
Prompts: recovery_check, workout_deep_dive, weekly_training_review,
training_load_review, performance_progression, `long_ride_climbing_analy
Futureweb Intervals MCP 질문
Futureweb Intervals MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --env 'API_KEY=<YOUR_API_KEY>' --env 'ATHLETE_ID=<ATHLETE_ID>' intervals-mcp-server -- uvx futureweb-intervals-mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Futureweb Intervals MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Futureweb Intervals MCP는 어떤 도구를 제공하나요?
52개 도구를 제공합니다. 예: get_gear_list, get_gear_details, get_athlete_profile, get_sport_settings, get_training_zones.
Garmin 데이터와 함께 사용할 수 있나요?
네, Garmin 기반 지표와 함께 작동하도록 설계되었습니다. 특히 Garmin Intervals Bridge와 함께 사용하면 VO2max 및 회복 시간과 같은 지표를 복원할 수 있습니다.
보안 및 인증은 어떻게 처리하나요?
'Continue with Intervals.icu' 로그인을 제공하는 내장 OAuth 2.1 서버를 사용하며, 안전한 액세스를 위해 PKCE 및 private_key_jwt를 지원합니다.