mcp-garmin
Read-only access to Garmin Connect health and fitness data, including daily health metrics, activities, workouts, body composition, and profile information.
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., "@mcp-garmin Show my daily summary for today"
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.
mcp-garmin
MCP server for Garmin Connect health and fitness data. Read-only access to daily health metrics, activities, workouts, and body composition via the python-garminconnect library.
Prerequisites
Python 3.14+
A Garmin Connect account
Related MCP server: Garmin MCP
Authentication
Garmin Connect uses email/password authentication with optional MFA. The library persists session tokens to ~/.garminconnect/garmin_tokens.json after initial login.
First-time setup
Run the interactive login command to establish tokens. This handles MFA prompts:
# Set credentials (or the CLI will prompt you)
export GARMIN_EMAIL="you@example.com"
export GARMIN_PASSWORD="your-password"
# Interactive login -- prompts for MFA if enabled
uvx mcp-garmin-loginRunning the server
The MCP server requires GARMIN_EMAIL and GARMIN_PASSWORD environment variables. It reuses tokens saved by the login step and refreshes them automatically.
export GARMIN_EMAIL="you@example.com"
export GARMIN_PASSWORD="your-password"Configuration
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"garmin": {
"command": "uvx",
"args": ["mcp-garmin"],
"env": {
"GARMIN_EMAIL": "you@example.com",
"GARMIN_PASSWORD": "your-password"
}
}
}
}Claude Code
claude mcp add garmin -- uvx mcp-garminSet GARMIN_EMAIL and GARMIN_PASSWORD in your shell environment.
Tools
All date parameters use ISO format (YYYY-MM-DD).
Daily Health
Tool | Description |
| Steps, calories, distance, active minutes |
| Heart rate data |
| Sleep stages and metrics |
| Detailed stress levels |
| All-day stress summary |
| Body Battery (energy) levels |
| Detailed step data |
| Heart Rate Variability |
| Blood oxygen saturation |
| Respiratory rate |
| Training readiness score |
| Intensity minutes |
| Resting heart rate |
Activities
Tool | Description |
| List recent activities (paginated) |
| Activities within a date range |
| All activities for a specific date |
| Most recent activity |
| Single activity by ID |
| Detailed metrics (laps, charts) |
| Split/lap data |
| Weather during activity |
| Heart rate zone distribution |
| Equipment used |
| Strength training sets |
Workouts
Tool | Description |
| List saved workout templates |
| Single workout by ID |
Body Composition
Tool | Description |
| Body composition over a date range |
| Weight measurements over a date range |
Profile & Fitness
Tool | Description |
| Profile information |
| VO2 max and fitness metrics |
| Calculated fitness age |
| Training status |
| Personal bests |
Development
uv sync
uv run pytest tests/ -x -q
uv run ruff check src/ tests/
uv run pyright src/Available Tools
32 toolsget_activitiesC
List recent activities, newest first.
Args: start: Zero-based index to start from. limit: Maximum number of activities to return (1-100).
Inputs: start, limit. Returns: result
get_activities_by_dateA
Get activities within a date range, optionally filtered by type.
Args: start_date: Start date in YYYY-MM-DD format. end_date: End date in YYYY-MM-DD format. activity_type: Optional activity type filter (e.g. "running", "cycling").
Inputs: start_date (required), end_date (required), activity_type. Returns: result
get_activityB
Get a single activity by its ID.
Args: activity_id: Garmin activity ID.
Inputs: activity_id (required). Returns: result
get_activity_detailsC
Get detailed metrics for an activity (laps, charts, etc.).
Args: activity_id: Garmin activity ID.
Inputs: activity_id (required). Returns: result
get_activity_exercise_setsA
Get strength training exercise sets for an activity.
Args: activity_id: Garmin activity ID.
Inputs: activity_id (required). Returns: result
get_activity_gearB
Get equipment/gear used in an activity.
Args: activity_id: Garmin activity ID.
Inputs: activity_id (required). Returns: result
get_activity_hr_zonesB
Get heart rate zone distribution for an activity.
Args: activity_id: Garmin activity ID.
Inputs: activity_id (required). Returns: result
get_activity_splitsC
Get split/lap data for an activity.
Args: activity_id: Garmin activity ID.
Inputs: activity_id (required). Returns: result
get_activity_weatherC
Get weather conditions during an activity.
Args: activity_id: Garmin activity ID.
Inputs: activity_id (required). Returns: result
get_body_batteryB
Get Body Battery (energy) levels for a given date.
Args: date: Date in YYYY-MM-DD format.
Inputs: date (required). Returns: result
get_body_compositionB
Get body composition data for a date range.
Args: start_date: Start date in YYYY-MM-DD format. end_date: End date in YYYY-MM-DD format.
Inputs: start_date (required), end_date (required). Returns: result
get_daily_summaryB
Get daily activity summary (steps, calories, distance, active minutes).
Args: date: Date in YYYY-MM-DD format.
Inputs: date (required). Returns: result
get_fitness_ageA
Get calculated fitness age for a given date.
Args: date: Date in YYYY-MM-DD format.
Inputs: date (required). Returns: result
get_heart_ratesA
Get heart rate data for a given date.
Args: date: Date in YYYY-MM-DD format.
Inputs: date (required). Returns: result
get_hrv_dataA
Get Heart Rate Variability (HRV) data for a given date.
Args: date: Date in YYYY-MM-DD format.
Inputs: date (required). Returns: result
get_intensity_minutesB
Get intensity minutes data for a given date.
Args: date: Date in YYYY-MM-DD format.
Inputs: date (required). Returns: result
get_last_activityB
Get the most recent activity.
Inputs: no named parameters. Returns: result
get_max_metricsA
Get VO2 max and related fitness metrics for a given date.
Args: date: Date in YYYY-MM-DD format.
Inputs: date (required). Returns: result
get_personal_recordsA
Get personal best records across all activities.
Inputs: no named parameters. Returns: result
get_respiration_dataB
Get respiratory rate data for a given date.
Args: date: Date in YYYY-MM-DD format.
Inputs: date (required). Returns: result
get_resting_heart_rateB
Get resting heart rate for a given date.
Args: date: Date in YYYY-MM-DD format.
Inputs: date (required). Returns: result
get_server_versionA
Return the installed version of the mcp-garmin server.
Inputs: no named parameters. Returns: result
get_sleep_dataB
Get sleep stages and metrics for a given date.
Args: date: Date in YYYY-MM-DD format.
Inputs: date (required). Returns: result
get_spo2_dataA
Get blood oxygen saturation (SpO2) data for a given date.
Args: date: Date in YYYY-MM-DD format.
Inputs: date (required). Returns: result
get_steps_dataB
Get detailed step data for a given date.
Args: date: Date in YYYY-MM-DD format.
Inputs: date (required). Returns: result
get_stress_dataC
Get stress levels throughout the day.
Args: date: Date in YYYY-MM-DD format.
Inputs: date (required). Returns: result
get_training_readinessA
Get training readiness score for a given date.
Args: date: Date in YYYY-MM-DD format.
Inputs: date (required). Returns: result
get_training_statusC
Get current training status for a given date.
Args: date: Date in YYYY-MM-DD format.
Inputs: date (required). Returns: result
get_user_profileA
Get the user's Garmin Connect profile information.
Inputs: no named parameters. Returns: result
get_weigh_insB
Get weight measurements for a date range.
Args: start_date: Start date in YYYY-MM-DD format. end_date: End date in YYYY-MM-DD format.
Inputs: start_date (required), end_date (required). Returns: result
get_workoutC
Get a saved workout template by ID.
Args: workout_id: Garmin workout ID.
Inputs: workout_id (required). Returns: result
get_workoutsA
List saved workout templates.
Inputs: no named parameters. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 32 tools
Each tool has a distinct and well-defined purpose, with clear differentiation among activity sub-tools (details, splits, gear, etc.) and between list/single retrieval functions. No two tools appear to do the same thing.
All tools follow a consistent 'get_<specific_data>' pattern using snake_case, with no mixing of conventions or verb styles. This makes the tool set highly predictable.
32 tools is on the higher side, but given the comprehensive nature of Garmin data (many distinct metrics like HRV, SpO2, body battery, etc.), the count is justifiable for a read-only data retrieval server. Slight over-scoping but not excessive.
The server covers virtually all major Garmin data categories: activities (with detailed breakdowns), daily summaries, body metrics, sleep, heart rate, stress, training readiness, and more. No obvious gaps for a read-only interface.
Related MCP Connectors
MCP server for Withings health data — sleep, activity, heart, and body metrics.
Remote MCP server for training, nutrition, wellness, and performance data with OAuth 2.0.
Unofficial Garmin Connect access: sleep, HRV, training, activities, workouts and weight.
Multi-tenant hosted MCP server for Oura Ring — 21 read-only tools, OAuth per user.
Related MCP Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server that provides comprehensive access to Garmin Connect data including sleep analytics, health metrics, activities, and training volume analysis.1645 npm8MIT
- AlicenseAqualityDmaintenanceMCP server that exposes Garmin Connect health and activity data (steps, sleep, stress, activities, etc.) via tools for querying, analysis, and visualization.17Apache 2.0
- AlicenseAqualityDmaintenanceMCP server for reading and querying Garmin Connect data, including activities, strength history, recovery, trends, and optionally creating workouts.12MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Garmin Connect that enables users to access and manage their personal health and fitness data, including daily summaries, heart rate, sleep, HRV, stress, body composition, activities, and training readiness, with secure per-user authentication.Functional Source , Version 1.1, ALv2 Future