Intervals.icu MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INTERVALS_API_KEY | Yes | Your Intervals.icu API Key | |
| INTERVALS_ATHLETE_ID | Yes | Your Intervals.icu Athlete ID (e.g., i12345) |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_athlete_profileB | Get the profile of the configured athlete. |
| list_activitiesA | List activity summaries for a date range. Returns ONLY compact identification data (id, date, name, type, distance, moving_time, elevation, heart rate, speed, training load, fitness/fatigue, calories, source). To analyze an activity in depth, you MUST call get_activity — it returns 100+ fields including power, cadence, zones, weather, performance metrics, intervals, and more. |
| get_activityA | Get FULL details of a specific activity by ID. Returns 100+ fields far beyond what list_activities provides, including: power (avg, weighted, FTP, W', joules), cadence, pace/GAP, zone times (HR/power/pace), performance metrics (efficiency factor, variability index, decoupling, polarization index), weather conditions, temperature, RPE/feel, intervals summary, achievements, gear, and tags. Always use this when answering questions about a specific activity. |
| list_wellnessA | List wellness data (sleep, fatigue, etc.) for the athlete within a date range. |
| list_workoutsA | List all workouts in the athlete's library. |
| create_workoutC | Create a new workout in the library. |
| list_eventsA | List calendar events (planned workouts, notes, races, etc.) within a date range. Returns event details including workout descriptions/steps. |
| create_eventC | Create a new event on the calendar (must be in the future). |
| update_eventC | Update a future event on the calendar. |
| delete_future_eventB | Delete a future event from the calendar. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool targets a distinct resource and action (create, read, list, update, delete) with clear boundaries. No overlap; get vs list are well-differentiated.
All tools follow a consistent verb_noun pattern (e.g., create_event, list_activities) using lowercase snake_case with no mixing of conventions.
10 tools is within the ideal range for a domain-specific server, covering key operations on activities, events, workouts, wellness, and athlete profile without unnecessary bloat.
Covers CRUD for events and read for most resources, but missing update/delete for workouts and update/delete for activities. Minor gaps that agents can work around.