Skip to main content
Glama
147,734 tools. Last updated 2026-05-27 15:15

"Garmin" matching MCP tools:

  • Lists all workouts in a date range — compact overview with type, duration, distance, pace, and heart rate. Use this tool first for an overview. For details on a single workout, use get_workout_detail. The workout ID in the output can be used with get_workout_detail and get_workout_samples. Parameters: - start_date: Start date in YYYY-MM-DD format - end_date: End date in YYYY-MM-DD format - activity_type: Optional. Filter: 'RUNNING', 'CYCLING', 'STRENGTH_TRAINING', etc. Matches all type-aliases — 'CYCLING' also returns ROAD_BIKING / MOUNTAIN_BIKING / INDOOR_CYCLING etc. - prefer_provider: Optional per-query override (e.g. 'WHOOP', 'GARMIN'). For each duplicate-cluster, the row from this provider wins (if present). Clusters without this provider remain on the default picker — no data is lost.
    Connector
  • Retrieves body measurement data: weight, body fat, muscle mass, and BMI. Parameters: - start_date: Start date in YYYY-MM-DD format - end_date: End date in YYYY-MM-DD format - prefer_provider: Optional. Per-query soft-override (e.g. 'WITHINGS', 'GARMIN').
    Connector
  • Retrieves sleep data for the user over a specified date range. Shows sleep duration, sleep stages (deep, REM, light), HRV, SpO2, breathing rate, and sleep score. Parameters: - start_date: Start date in YYYY-MM-DD format - end_date: End date in YYYY-MM-DD format - source: Optional. Hard provider filter e.g. 'GARMIN' or 'OURA' — only this provider's rows are returned. - prefer_provider: Optional soft override. Influences duplicate-cluster picking only; other nights remain visible.
    Connector
  • Shows trends and developments for a specific health metric over time. Compares the current period with the previous (equally long) period. Parameters: - metric: One of: 'hrv', 'sleep_duration', 'sleep_score', 'sleep_efficiency', 'readiness', 'resting_hr', 'steps', 'active_minutes', 'weight', 'body_fat', 'stress', 'strain', 'vo2max', 'training_load' - period: Time period: '7d', '30d', or '90d' (default: '30d') - prefer_provider: Optional. Per-query soft-override (e.g. 'OURA', 'GARMIN'). Influences which provider's data is shown when multiple devices report the same metric.
    Connector
  • Shows the daily summary for a specific date: steps, active time, calories, resting heart rate, HRV, and stress level. Parameters: - date: Date in YYYY-MM-DD format - prefer_provider: Optional per-query soft-override (e.g. 'OURA', 'GARMIN').
    Connector
  • Retrieves training activities for the user over a specified date range. Shows distance, duration, pace, heart rate, calories, and training load. Parameters: - start_date: Start date in YYYY-MM-DD format - end_date: End date in YYYY-MM-DD format - activity_type: Optional. Filter: 'RUNNING', 'CYCLING', 'STRENGTH_TRAINING', etc. Matches all type-aliases — 'CYCLING' also returns ROAD_BIKING / MOUNTAIN_BIKING / INDOOR_CYCLING etc. - prefer_provider: Optional. Per-query soft-override (e.g. 'WHOOP', 'GARMIN'). Influences duplicate-cluster picking. Clusters without this provider remain on default picker.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • PaceOAuth

    Pace is a remote MCP server that exposes wearable and fitness data to Claude via the Model Context Protocol. It connects to Garmin, Oura, Whoop, Polar, Fitbit and 20+ devices and provides 15 tools for querying sleep, activity, recovery, and training data. Hosted on Google Cloud Run, OAuth 2.1 authentication, Streamable HTTP transport. Instructions: First you need to create an account at: https://pacetraining.co and connect your wearables. After that you can connect the remote Server via Custom Connector in Claude and OAuth 2.1 Flow startet.

  • AI cycling coach: training plans, workouts, nutrition, strength training, Strava, Garmin and Wahoo.