garmin-mcp
Provides read-only access to a user's Garmin Connect health and activity data through their normal Garmin account login. Exposes around 260 read methods covering activities (runs, rides, swims, strength with splits, laps, HR/power zones, weather, gear, and GPS file export), sleep, heart rate and resting HR, HRV, stress, Body Battery, SpO2, respiration, steps, floors, intensity minutes, hydration, weight and body composition, blood pressure, training readiness/status, VO2 max, race predictions, endurance and hill scores, lactate threshold, FTP, devices, goals, and badges. Also supports raw GET requests against any Garmin Connect API path and downloading activities as TCX/GPX/KML/CSV or original FIT files.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@garmin-mcp How did I sleep last night?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
garmin-mcp
This project is entirely vibe-coded. This line is the only line written by a human in the entire codebase.
A local MCP server that gives AI assistants read-only access to
your Garmin Connect health and activity data. It is built on the
community garminconnect library, so it uses your
normal Garmin account login. There is no official Garmin API key involved.
Everything runs on your machine. Your credentials are only used by garmin-mcp login; only session
tokens are stored (~/.garmin-mcp/garmin_tokens.json, mode 0600).
What you can ask
Activities (runs, rides, swims, strength, ... with splits, laps, HR/power zones, weather, gear, GPS file export), sleep, heart rate, resting HR, HRV, stress, Body Battery, SpO2, respiration, steps, floors, intensity minutes, hydration, weight and body composition, blood pressure, training readiness/status, VO2 max, race predictions, endurance and hill score, lactate threshold, FTP, devices, goals, badges, and more (about 260 read methods in total).
Related MCP server: garmin-mcp
Install
Requires macOS/Linux with uv (brew install uv).
git clone <this repo> garmin-mcp && cd garmin-mcp
uv sync
uv run garmin-mcp login # email, password, MFA code if enabled
uv run garmin-mcp status # verifyConnect it to a client
Claude Desktop (stdio)
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"garmin": {
"command": "uv",
"args": ["run", "--directory", "/absolute/path/to/garmin-mcp", "garmin-mcp", "serve"]
}
}
}OpenCode
Add to ~/.config/opencode/opencode.json
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"garmin-mcp": {
"type": "local",
"command": ["uv", "run", "garmin-mcp", "serve"],
"enabled": true,
"environment": {
"UV_WORKING_DIR": "/absolute/path/to/garmin-mcp"
}
}
}
}Claude Code / others
claude mcp add garmin -- uv run --directory /absolute/path/to/garmin-mcp garmin-mcp serveLocal HTTP server
uv run garmin-mcp serve --transport http --port 8765 # http://127.0.0.1:8765/mcpThe HTTP endpoint has no authentication and binds to 127.0.0.1 by default. Anything on your machine
can read your Garmin data through it. Don't expose it to a network.
Tools
Two toolsets (serve --toolset core|all):
Toolset | What you get |
| About 60 curated tools for the common data, plus |
| Every read method registered as its own tool (about 260). |
Always available: get_today (today's date in your Garmin timezone), garmin_api_get (raw GET against any
Garmin Connect API path), and download_activity (saves a TCX/GPX/KML/CSV or original FIT zip to
~/.garmin-mcp/downloads and returns the path).
Only read methods are exposed. Nothing can create, edit or delete data on your Garmin account.
Large responses (e.g. a full day of per-minute heart rate, or an activity's chart data) are automatically
downsampled to fit --max-chars (default 100000), and the result says so; ask for a shorter range to get full
resolution.
Configuration
Variable | Default | Purpose |
|
| Where session tokens live |
|
| Where |
| unset | Set to |
| unset | Optional: used by |
Tokens refresh automatically. If Garmin rejects them, tools return an error asking you to run
garmin-mcp login again. garmin-mcp logout deletes the saved tokens.
Development
uv run pytest
uv run ruff check . && uv run ruff format .Tests use a fake Garmin client and exercise the real MCP protocol (in-memory and over stdio); they need no account.
Notes
This relies on unofficial endpoints and may break if Garmin changes them. Logging in too often can get you rate limited, which is why tokens are reused.
Not affiliated with Garmin.
Available Tools
62 toolscount_activitiesBRead-only
Return total number of activities for the current user account. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: no named parameters. Returns: result
download_activityAIdempotent
Download an activity's raw file (GPS track, sensor data) to the local download directory and return its path. Reads from Garmin; only writes a local file.
Inputs: activity_id (required), format. Returns: result
garmin_api_getARead-only
Raw GET against the Garmin Connect API for endpoints that have no dedicated tool.
Read-only; the path must not contain a query string (use params).
Inputs: path (required), params. Returns: result
garmin_callARead-only
Run any read-only Garmin Connect data method by name (see garmin_list_methods).
Inputs: method (required), arguments. Returns: result
garmin_list_methodsARead-only
List every read-only Garmin Connect data method runnable with garmin_call, with
parameters and description. Use it to discover data without a dedicated tool (golf,
nutrition, gear, ECG, women's health, calendar, courses, ...).
Inputs: query. Returns: result
get_activitiesARead-only
Return a page of activities, newest first, optionally filtered by type. :param start: Starting activity offset, where 0 means the most recent activity :param limit: Number of activities to return :param activitytype: (Optional) Filter activities by type :param activitysubtype: (Optional) Filter activities further by sub-type. :return: List of activities from Garmin. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: limit, start, activitytype, activitysubtype. Returns: result
get_activities_by_dateARead-only
Return activities between two dates, optionally filtered by type. :param startdate: String in the format YYYY-MM-DD :param enddate: (Optional) String in the format YYYY-MM-DD :param activitytype: (Optional) Type of activity you are searching Possible values are [cycling, running, swimming, multi_sport, fitness_equipment, hiking, walking, other] :param sortorder: (Optional) sorting direction. By default, Garmin uses descending order by startLocal field. Use "asc" to get activities from oldest to newest. :return: list of JSON activities. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: startdate (required), enddate, sortorder, activitytype. Returns: result
get_activityBRead-only
Return activity summary, including basic splits. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: activity_id (required). Returns: result
get_activity_detailsCRead-only
Return activity details. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: activity_id (required), maxpoly, maxchart. Returns: result
get_activity_exercise_setsCRead-only
Return activity exercise sets. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: activity_id (required). Returns: result
get_activity_gearCRead-only
Return the gear linked to an activity. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: activity_id (required). Returns: result
get_activity_hr_in_timezonesCRead-only
Return the time spent in each heart rate zone during an activity. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: activity_id (required). Returns: result
get_activity_power_in_timezonesCRead-only
Return the time spent in each power zone during an activity. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: activity_id (required). Returns: result
get_activity_splitsCRead-only
Return activity splits. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: activity_id (required). Returns: result
get_activity_split_summariesCRead-only
Return activity split summaries. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: activity_id (required). Returns: result
get_activity_typed_splitsBRead-only
Return typed activity splits. Contains similar info to get_activity_splits, but for certain activity types (e.g., Bouldering), this contains more detail. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: activity_id (required). Returns: result
get_activity_typesBRead-only
Return all activity types and their parent types. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: no named parameters. Returns: result
get_activity_weatherCRead-only
Return activity weather. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: activity_id (required). Returns: result
get_blood_pressureCRead-only
Return blood pressure by day for 'startdate' format 'YYYY-MM-DD' through enddate 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: startdate (required), enddate. Returns: result
get_body_batteryCRead-only
Return body battery values by day for 'startdate' format 'YYYY-MM-DD' through enddate 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: startdate (required), enddate. Returns: result
get_body_battery_eventsARead-only
Return body battery events for date 'cdate' format 'YYYY-MM-DD'. The return value is a list of dictionaries, where each dictionary contains event data for a specific event. Events can include sleep, recorded activities, auto-detected activities, and naps. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: cdate (required). Returns: result
get_body_compositionBRead-only
Return available body composition data for 'startdate' format 'YYYY-MM-DD' through enddate 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: startdate (required), enddate. Returns: result
get_cycling_ftpBRead-only
Return cycling Functional Threshold Power (FTP) information. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: no named parameters. Returns: result
get_daily_heart_rate_statsBRead-only
Return resting / min / max heart rate per day. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: end (required), start (required). Returns: result
get_daily_stepsCRead-only
Fetch available steps data 'start' and 'end' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: end (required), start (required). Returns: result
get_daily_stress_statsBRead-only
Return overall stress level and stress durations per day. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: end (required), start (required). Returns: result
get_daily_summariesBRead-only
Return full daily summaries for a date range in one call. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: end (required), start (required). Returns: result
get_device_last_usedARead-only
Return the device that synced last. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: no named parameters. Returns: result
get_devicesBRead-only
Return available devices for the current user account. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: no named parameters. Returns: result
get_earned_badgesARead-only
Return all earned badges for the current user. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: no named parameters. Returns: result
get_endurance_scoreARead-only
Return endurance score by day for 'startdate' format 'YYYY-MM-DD' through enddate 'YYYY-MM-DD'. Using a single day returns the precise values for that day. Using a range returns values aggregated per aggregation period (weekly by default; the web app uses daily for its 4- and 12-week reports). (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: startdate (required), enddate, aggregation. Returns: result
get_fitnessage_dataBRead-only
Return Fitness Age data for current user. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: cdate (required). Returns: result
get_floorsBRead-only
Fetch available floors data 'cDate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: cdate (required). Returns: result
get_goalsARead-only
Return goals by status (active, future or past). :param status: Status of goals (valid options are "active", "future", or "past") :type status: str :param start: 1-based index of the first goal to retrieve :type start: int :param limit: Pagination limit when retrieving goals :type limit: int :return: list of goals in JSON format. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: limit, start, status. Returns: result
get_heart_ratesCRead-only
Fetch available heart rates data 'cDate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: cdate (required). Returns: result
get_hill_scoreCRead-only
Return hill score by day from 'startdate' format 'YYYY-MM-DD' to enddate 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: startdate (required), enddate. Returns: result
get_hrv_dataBRead-only
Return HRV (Heart Rate Variability) data for 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: cdate (required). Returns: result
get_hydration_dataARead-only
Return available hydration data 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: cdate (required). Returns: result
get_intensity_minutes_dataBRead-only
Return available Intensity Minutes data 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: cdate (required). Returns: result
get_lactate_thresholdBRead-only
Return running lactate threshold information, including heart rate, power, and speed. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: latest, end_date, start_date, aggregation. Returns: result
get_last_activityBRead-only
Return the most recent activity. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: no named parameters. Returns: result
get_lifetime_totalsARead-only
Return lifetime totals (distance, steps, calories, active days, ...). (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: no named parameters. Returns: result
get_max_metricsCRead-only
Return available max metric data for 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: cdate (required). Returns: result
get_personal_recordCRead-only
Return personal records for current user. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: months, include_history. Returns: result
get_progress_summary_between_datesARead-only
Return progress totals (distance, duration, ...) between two dates. :param startdate: String in the format YYYY-MM-DD :param enddate: String in the format YYYY-MM-DD :param metric: metric to be calculated in the summary: "elevationGain", "duration", "distance", "movingDuration" :param groupbyactivities: group the summary by activity type :return: list of JSON activities with their aggregated progress summary. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: enddate (required), startdate (required), metric, groupbyactivities. Returns: result
get_race_predictionsBRead-only
Return race predictions for the 5k, 10k, half marathon and marathon. Accepts either 0 parameters or all three: If all parameters are empty, returns the race predictions for the current date Or returns the race predictions for each day or month in the range provided. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: enddate, startdate. Returns: result
get_respiration_dataBRead-only
Return available respiration data 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: cdate (required). Returns: result
get_rhr_dayCRead-only
Return resting heart rate data for 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: cdate (required). Returns: result
get_sleep_dataBRead-only
Return sleep data for 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: cdate (required). Returns: result
get_sleep_stats_weeklyBRead-only
Return weekly sleep statistics (overallStats + per-week values). (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: end, weeks. Returns: result
get_spo2_dataBRead-only
Return available SpO2 data 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: cdate (required). Returns: result
get_stats_and_bodyARead-only
Return the daily summary and body composition for a date. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: cdate (required). Returns: result
get_steps_dataCRead-only
Fetch available steps data 'cDate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: cdate (required). Returns: result
get_stress_dataCRead-only
Return stress data for 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: cdate (required). Returns: result
get_todayARead-only
Today's date (YYYY-MM-DD) in the Garmin account's timezone. Use it to resolve relative dates such as "yesterday" or "last week" before querying other tools.
Inputs: no named parameters. Returns: result
get_training_readinessCRead-only
Return training readiness data for 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: cdate (required). Returns: result
get_training_statusBRead-only
Return training status data for current user. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: cdate (required). Returns: result
get_user_profileBRead-only
Return the user settings (user data, units, formats, sleep times). (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: no named parameters. Returns: result
get_user_statisticsBRead-only
Return the profile statistics block (totals per activity type). (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: no named parameters. Returns: result
get_user_summaryCRead-only
Return user activity summary for 'cdate' format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: cdate (required). Returns: result
get_weekly_activity_statsCRead-only
Return weekly activity aggregates (VO2 max, distance, duration, ...). (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: end (required), start (required), group_by_activity_type. Returns: result
get_weigh_insBRead-only
Get weigh-ins between startdate and enddate using format 'YYYY-MM-DD'. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)
Inputs: enddate (required), startdate (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 62 tools
Many tools overlap heavily: get_daily_heart_rate_stats vs get_heart_rates vs get_rhr_day; get_daily_stress_stats vs get_stress_data; get_steps_data vs get_daily_steps; and several activity-detail variants (get_activity, get_activity_details, get_activity_splits, get_activity_typed_splits, get_activity_split_summaries). Descriptions help in places, but an agent can easily choose the wrong endpoint for the same underlying data.
Most tools follow a get_<noun> snake_case pattern, but there are noticeable deviations: garmin_api_get, garmin_list_methods, garmin_call, download_activity, and get_today break the dominant convention. Minor inconsistencies like get_fitnessage_data and get_weigh_ins also reduce predictability.
62 tools is excessive for a read-only data server, especially because many endpoints are near-duplicates and generic escape hatches (garmin_api_get, garmin_call, garmin_list_methods) already cover undocumented data. Consolidation would make the surface far easier to navigate.
For a read-only Garmin Connect surface, coverage is broad: daily metrics, activities, sleep, body composition, training status, devices, goals, badges, raw API access, and downloads are all present. Some niche domains rely on the generic fallback rather than dedicated tools, but there are few obvious hard dead ends.
Related MCP Connectors
Garmin watch data for AI assistants: activities, sleep, HRV, recovery. Never writes to Garmin.
Garmin data in Claude & ChatGPT via the Garmin Health API. OAuth sign-in, no password sharing.
Explore Garmin activity and health data with your AI assistant.
Your Garmin, Oura, WHOOP, Hevy and 35 more fitness apps, queryable from your own AI.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to access and query Garmin Connect health and fitness data, including sleep, HRV, training load, and activities, with an optional coaching plugin for personalized training plans.9 npm4-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query live Garmin Connect health and fitness data, including daily metrics, activities, sleep analysis, and trends via natural language.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access Garmin Connect fitness and health data, including activities, heart rate, sleep, and device information.MIT
- AlicenseAqualityBmaintenanceEnables local, read-only access to Garmin Connect health and training data through MCP, letting assistants summarize recovery, sleep, activities, and more without uploading your data.24MIT