igpsport-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IGPSPORT_FTP | No | FTP in watts (optional) | |
| IGPSPORT_LTHR | No | Lactate threshold heart rate in bpm (optional) | |
| IGPSPORT_PASSWORD | Yes | Password | |
| IGPSPORT_USERNAME | Yes | iGPSport account (phone number) | |
| IGPSPORT_CACHE_DIR | No | Cache directory, default ~/.cache/igpsport-mcp (optional) | |
| IGPSPORT_LOG_LEVEL | No | Log level, default INFO (optional) |
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 |
|---|---|
| list_activitiesC | List rides with optional ISO-8601 date range and paging (cached, units fixed). |
| get_activity_summaryA | Derived metrics for one ride: NP/IF/TSS/work, HR & power zone time. |
| get_activity_streamsB | Time-series channels as compact bare arrays. Channels default to power+hr; resolution one of 1s/5s/10s/30s/1min (default 10s to keep tokens sane). |
| get_activity_lapsC | Per-lap splits with per-lap NP computed from the record stream. |
| get_athlete_profileA | Athlete training parameters (FTP/LTHR from config) with HR/power zone bounds. |
| get_athlete_statsC | Aggregate distance/duration/elevation over week|month|year|all. |
| compare_activitiesB | Compare 2-5 rides across metrics with per-metric delta% and a narrative hint. |
| analyze_training_loadB | CTL/ATL/TSB daily trend + current form interpretation over the last N days. |
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 8 tools
Each tool targets a distinct aspect: training load analysis, activity comparison, lap splits, raw streams, summary metrics, athlete profile, aggregate stats, and activity listing. No functional overlap.
All tool names follow a consistent verb_noun pattern (underscore-separated) with 'get_' for most retrievals and 'analyze_'/'compare_' for specific operations. No mixing of conventions.
8 tools cover the domain of cycling/fitness data retrieval without being excessive. Each tool serves a clear purpose, and the count is within the ideal 3-15 range.
The tool set covers core operations: listing, summary, streams, laps, athlete profile, stats, training load, and comparison. A minor gap is the lack of route/segment data, but the core analytics are well represented.