mcp · handle garmin_athletics_mcp · source page
garmin_connect_mcp · job 82%Garmin AI Connector · job 83%Garmin Assistant · job 82%blocks · job 74%Garmin Personal MCP · job 76%durely insights · job 80%garmin-mcp · job 76%Garmin Connect to ChatGPT MCP · job 78%Running Companion · job 83%leap · job 74%Paceva for Garmin · job 80%garmin-owl · job 79%Garmin Connect MCP · job 82%Nolio MCP Server · job 74%SisRUN MCP · job 77%Garmin Local Archive · job 75%Zone Two · job 75%Garmin MCP · job 84%Garmin Connect China MCP · job 77%Kailo MCP Server · job 76%Antevo MCP · job 78%Huawei MCP Connector · job 76%ghealth-mcp · job 75%Garmin Connect API · job 74%Threshold · job 88%coach · job 76%AthleteData MCP Server · job 73%mcp-strava · job 75%hybridlog · job 78%ownmetrics-mcp · job 84%Garmin Health MCP · job 86%garmin-cn-ai-trainlab · job 79%garmin-watch-mcp · job 80%Aidlab MCP · job 79%Garmin Personal API MCP · job 85%Garmin MCP Server · job 73%RunFuel MCP · job 75%Garmin Connect MCP Server · job 80%Percentages are graph-similarity metadata, not suitability scores. A graph edge answers “is it connected” — plan fit and comparable cost are checked below.
Pick the exact reference and alternative series. Each history is separate; gaps stay gaps.
This view calls the same get_evidence tool your agent would — chart, table and MCP response describe the same records. Watch the reference series