intervals.mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INTERVALS_API_KEY | Yes | Your API key (Settings → API) | |
| INTERVALS_ATHLETE_ID | Yes | Your athlete ID (found in the intervals.icu URL, 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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_athleteB | Get athlete profile including sport zones and thresholds. |
| get_activitiesB | List activities with optional filters. Args: oldest: Start date in YYYY-MM-DD format (inclusive). newest: End date in YYYY-MM-DD format (inclusive). sport_type: Filter by sport type (e.g. 'Ride', 'Run', 'Swim'). |
| get_activity_detailA | Get full detail for a single activity including laps and intervals. Args: activity_id: The activity ID (visible in the intervals.icu URL). |
| get_fitnessB | Get CTL/ATL/TSB fitness time series. Args: oldest: Start date in YYYY-MM-DD format (inclusive). newest: End date in YYYY-MM-DD format (inclusive). |
| get_wellnessA | Get wellness data including HRV, resting HR, sleep, and fatigue scores. Args: oldest: Start date in YYYY-MM-DD format (inclusive). newest: End date in YYYY-MM-DD format (inclusive). |
| get_eventsB | Get planned workouts and races from the calendar. Args: oldest: Start date in YYYY-MM-DD format (inclusive). newest: End date in YYYY-MM-DD format (inclusive). |
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 6 tools
Each tool targets a distinct domain: activity listing vs. detailed retrieval, athlete profile, calendar events, fitness metrics (CTL/ATL/TSB), and wellness data. No overlap in purpose; the distinction between planned events and completed activities is clear.
Perfectly consistent verb_noun pattern using 'get_' prefix throughout. All use snake_case. The '_detail' suffix appropriately distinguishes single-resource retrieval from list operations without breaking the convention.
Six tools is ideal for this focused read-only integration covering the core intervals.icu data surfaces (activities, athlete, calendar, fitness, wellness). Each tool earns its place; neither bloated nor sparse.
Strong coverage of read operations for athlete analytics including list/detail views and time-series data. Minor gaps exist: no power curve retrieval, segment data, or write operations (create/update activities/events), but core analysis workflows are fully supported.