intervals.icu-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOOL_ROUTING | No | Enable fastembed semantic tool discovery | false |
| INTERVALS_API_KEY | Yes | Your Intervals.icu API key (Required) | |
| INTERVALS_BASE_URL | No | Intervals.icu API base URL | https://intervals.icu/api/v1 |
| INTERVALS_ATHLETE_ID | No | Athlete ID | 0 |
| ENABLE_CONTEXTFORGE_GATEWAY | No | Enable IBM ContextForge SSE gateway on port 8000 | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_athlete_profileA | Fetch athlete profile details, including FTP, LTHR, weight, max HR, and training zones. Use to inspect baseline athletic physiological metrics and training zone configurations. Args: athlete_id: Athlete ID (defaults to "0" for the authenticated athlete). |
| list_activitiesA | List completed workout activities within a date range. Use when retrieving activity summaries across a date range. To fetch detailed power/HR streams or intervals for a single activity, use get_activity. Args: oldest: Start date in YYYY-MM-DD format (e.g. "2026-07-01"). newest: End date in YYYY-MM-DD format (e.g. "2026-07-26"). athlete_id: Athlete ID (defaults to "0" for authenticated athlete). |
| get_activityA | Get full details and detailed metrics for a single activity. Use when analyzing specific workout metrics (e.g. Normalized Power, TSS, HR zones). To list multiple activities across dates, use list_activities. Args: activity_id: The unique ID of the activity. |
| update_activityA | Update metadata fields on an activity. Only specified fields are updated. Use when editing activity titles, descriptions, types, or gear assignment. To post a comment message, use add_activity_message instead. Args: activity_id: ID of the activity to update. name: New name for the activity. description: Updated description or notes. type: Activity type (e.g., "Ride", "Run", "Swim", "WeightTraining"). gear: List of gear names or IDs used. |
| delete_activityA | Delete an activity by ID from Intervals.icu calendar. Use to permanently remove duplicate or invalid uploaded activity files. Args: activity_id: Unique activity ID to delete. |
| list_activity_messagesA | Retrieve comments and coach messages associated with an activity. Use to view discussion thread on an activity. To post a new message, use add_activity_message. Args: activity_id: Activity ID. |
| add_activity_messageA | Post a comment/note to an activity conversation thread. Use to add athlete/coach feedback to a workout. To edit activity description directly, use update_activity instead. Args: activity_id: Activity ID. text: Comment or message text to attach. |
| list_eventsA | List calendar events and planned workouts between dates. Use when browsing planned workouts, notes, or race events on the calendar. To fetch details of a specific planned event, use get_event. Args: oldest: Start date (YYYY-MM-DD). newest: End date (YYYY-MM-DD). athlete_id: Athlete ID (defaults to "0"). |
| get_eventA | Fetch details of a single calendar event or planned workout. Use when inspecting target workout steps or race plans for a specific calendar item. To list events across a date range, use list_events. Args: event_id: Calendar event ID. athlete_id: Athlete ID (defaults to "0"). |
| create_eventA | Create a new planned workout, race event, or note on the calendar. Use when scheduling upcoming training or race events. To modify an existing calendar event, use update_event. Args: start_date_local: Local start time in YYYY-MM-DDTHH:MM:SS format (e.g. "2026-07-27T08:00:00"). name: Title of event/workout. description: Workout steps or description text. type: Activity type (e.g. "Ride", "Run", "Swim"). category: Event category (e.g. "WORKOUT", "RACE", "NOTE"). athlete_id: Athlete ID (defaults to "0"). |
| update_eventA | Update an existing calendar event or planned workout. Use when modifying workout targets, start dates, or titles. To schedule a new event, use create_event. Args: event_id: Calendar event ID to update. start_date_local: Updated local start time (YYYY-MM-DDTHH:MM:SS). name: Updated name. description: Updated workout description or details. athlete_id: Athlete ID (defaults to "0"). |
| delete_eventA | Delete a calendar event or planned workout by ID. Use to remove canceled workouts or events from the training calendar. Args: event_id: ID of the event to delete. athlete_id: Athlete ID (defaults to "0"). |
| list_wellnessA | List daily wellness records in a date range. Use when tracking trends in sleep, HRV, weight, and readiness over time. To inspect a single day's wellness record, use get_wellness. Args: oldest: Start date (YYYY-MM-DD). newest: End date (YYYY-MM-DD). athlete_id: Athlete ID (defaults to "0"). |
| get_wellnessA | Fetch wellness record for a specific date. Use when examining a single day's physiological metrics. To list metrics across multiple days, use list_wellness. Args: date: Date string in YYYY-MM-DD format. athlete_id: Athlete ID (defaults to "0"). |
| update_wellnessA | Update daily wellness metrics for a given date. Use to log or update daily sleep, weight, HRV, and subjective readiness. Updates only specified fields. Args: date: Date in YYYY-MM-DD format. weight: Body weight in kg. resting_hr: Resting heart rate in bpm. hrv: Heart rate variability. sleep_secs: Total sleep duration in seconds. readiness: Readiness score. fatigue: Subjective fatigue score. mood: Subjective mood score. comments: Optional daily notes/comments. athlete_id: Athlete ID (defaults to "0"). |
| list_workout_foldersA | List workout folders in the athlete library. Use when browsing workout library structure. To list workouts within a folder, use list_workouts. Args: athlete_id: Athlete ID (defaults to "0"). |
| list_workoutsA | List structured library workouts. Use when browsing reusable workout templates. To schedule a workout onto the calendar, use create_event. Args: folder_id: Optional workout folder ID to filter by. athlete_id: Athlete ID (defaults to "0"). |
| route_toolsA | Find tools relevant to your task. Call this FIRST, then use call_routed_tool to invoke them. Args: query: Natural-language description of what you want to do (e.g. "get athlete FTP"). |
| call_routed_toolA | Invoke a tool returned by route_tools. Args: name: Exact tool name from route_tools output. arguments: JSON object of arguments. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jelmervdm/intervals.icu-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server