igpsport-mcp
Related Servers
Alternatives to igpsport-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server that lets you ask questions about your Garmin training history in plain language. It ingests FIT files into DuckDB locally and exposes typed tools for analyzing activities, streams, and summaries.9MIT
- AlicenseAqualityBmaintenanceEnables natural-language access to Intervals.icu training data, wellness metrics, activities, events, and workout management through MCP-compatible clients.64MIT
- AlicenseAqualityBmaintenanceAn MCP server that transforms Garmin data into compact, verdict-first coaching reports for LLMs, computing metrics like CTL/ATL/TSB and ACWR to answer training readiness questions.14Apache 2.0
- AlicenseNot gradedqualityAmaintenanceA read-only MCP server that lets Claude Desktop, Claude Code, Codex and GitHub Copilot query WHOOP recovery, sleep, HRV, strain and workout data through natural language, answering questions about personal baselines, trends and sleep debt. It also rebuilds HYROX sessions, tracks triathlon load and readiness with auditable evidence, and serves a chart-first local dashboard.16 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables querying workouts, fitness metrics (CTL/ATL/TSB), and power personal records from TrainingPeaks using natural language.2MIT
- AlicenseAqualityDmaintenanceEnables interaction with Intervals.icu data, including activities, wellness, and calendar events, via natural language.1029 npm1MIT
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.