Garmin Connect

What it is

A Garmin Connect client built around running, with 24 tools covering activity detail down to the split, weekly and monthly volume, training and HRV metrics, sleep and Body Battery, shoe mileage, and a workout builder that uploads to Garmin.

What you get

• Activities at split resolution: get_recent_activities lists runs up to a count capped at 100, get_activities_by_date takes a start_date and end_date, and get_activity_detail, get_activity_splits and get_activity_hr_zones open one run's stamina, per-kilometre splits and heart-rate zone distribution — 47 fields in all, from pace and cadence through running dynamics, power, Grade Adjusted Pace and gradient.
• Trail runs read as terrain rather than one average: get_activity_typed_splits returns ClimbPro climb segments with their grade and Grade Adjusted Pace, and get_activity_weather returns the temperature, humidity and wind the run happened in.
• Volume trends without a spreadsheet: get_weekly_running_summary aggregates over weeks capped at 12, and get_monthly_running_summary returns a month alongside its comparison with the one before.
• Training metrics against your own baseline: get_training_status and get_training_readiness for a date, get_vo2max_and_fitness for VO2 max and fitness age, get_race_predictions for 5K, 10K, half and full marathon times, and get_lactate_threshold for threshold heart rate and pace across a date range.
• Recovery in its own tools: get_heart_rate_data and get_hrv_data for a date, get_sleep_data for the night, get_daily_wellness for stress, Body Battery, SpO2 and respiration, and get_weekly_wellness_summary over weeks capped at 4.
• Records, goals and gear: get_personal_records covers 1K through marathon, get_goals filters by active, completed or all, and get_running_gear returns each pair of shoes with its cumulative distance and wear rate.
• create_running_workout assembles a structured session from warmup, interval, recovery, rest, cooldown and repeat steps — each ending on duration_seconds or distance_meters, each able to target pace, heart_rate, cadence or power — and uploads it to Garmin for the watch to pick up; get_workouts lists what is already saved.

Requirements

Python 3.10+, the uv package manager, and a Garmin Connect account. Authenticate once with scripts/auth.py, which prompts for an MFA code when the account uses one and stores OAuth tokens in ~/.garminconnect/; putting GARMIN_EMAIL and GARMIN_PASSWORD in .env lets an expired token refresh itself instead of prompting again.

Setup effort

Build from source — git clone https://github.com/leewnsdud/garmin-connect-mcp.git

Tools you get

24 tools named in the project's documentation. Twenty-three read; the one write, create_running_workout, builds a structured running session and uploads it to your Garmin watch. The server is running-specific, not a general Garmin bridge.

Requires

• Python 3.10+
• uv
• A Garmin Connect account

Where it runs

The documented client runs the server on your machine.