All connectors
Garmin

garmin-mcp-unofficial

Garmin Connect MCP connector

A Garmin Connect MCP server for agents that need rich wellness, sleep, stress, Body Battery, training and activity context.

SleepHRVBody BatteryStressTraining ReadinessShared profile
Outdoor cardio training with wearable devices and route context
Local Garmin Connect

Best for endurance athletes and daily agents that need a broad view of sleep, stress, Body Battery, training readiness and recent activities.

MCP server answers

The Garmin Connect MCP server is the local process provided by garmin-mcp-unofficial. Add its MCP configuration to a compatible client and it exposes the provider records listed on this page to that client. It is not an official Garmin Connect product and Delx does not host a copy of the data.

Compare this connector with the other wellness paths
What is the Garmin Connect MCP server?

The Garmin Connect MCP server is the local process provided by garmin-mcp-unofficial. Add its MCP configuration to a compatible client and it exposes the provider records listed on this page to that client. It is not an official Garmin Connect product and Delx does not host a copy of the data.

How do I install Garmin Connect MCP?

Run npx -y garmin-mcp-unofficial setup --auth, then npx -y garmin-mcp-unofficial doctor. The Quick Start section below contains the client configuration and provider-specific setup.

What can an agent read from Garmin Connect?

The available records start with Sleep duration, stages and score, HRV status and overnight HRV, Body Battery and events, Stress samples and daily summary. Check Data Availability for scope, device and export limitations before using any result.

Quick Start

terminal
npx -y garmin-mcp-unofficial setup --auth
npx -y garmin-mcp-unofficial doctor
mcp-client.json
{
  "mcpServers": {
    "garmin": {
      "command": "npx",
      "args": ["-y", "garmin-mcp-unofficial"]
    }
  }
}
  1. 01

    Run setup to write local MCP configuration.

  2. 02

    Run auth --install-helper or setup --auth for local Garmin login.

  3. 03

    Tokens are saved under ~/.garmin-mcp with user-only permissions.

Data Availability

Available

Sleep duration, stages and score

Available when supported by the device/account.

Available

HRV status and overnight HRV

Available on supported devices/accounts.

Available

Body Battery and events

Charge and drain context for each day.

Available

Stress samples and daily summary

Per-day stress context.

Conditional

Training readiness and training status

Depends on device/account support.

Available

Activities, details, splits and zones

Recent activities and detail payloads.

Not exposed

Continuous device telemetry

Not exposed by Garmin Connect web endpoints.

Agent Tools

Profile and onboarding

  • garmin_profile_get
  • garmin_profile_update
  • garmin_onboarding

Start here

  • garmin_connection_status
  • garmin_daily_summary
  • garmin_weekly_summary

Auth and diagnostics

  • garmin_capabilities
  • garmin_agent_manifest
  • garmin_auth_instructions
  • garmin_privacy_audit

Profile and devices

  • garmin_get_profile
  • garmin_get_user_settings
  • garmin_list_devices
  • garmin_get_primary_training_device

Daily wellness

  • garmin_get_daily_summary
  • garmin_get_steps_day
  • garmin_get_sleep_day
  • garmin_get_heart_day
  • garmin_get_hrv_day
  • garmin_get_stress_day
  • garmin_get_body_battery_day
  • garmin_get_training_readiness_day

Activities and body

  • garmin_list_activities
  • garmin_get_activity_details
  • garmin_get_weight_range

Prompts and Resources

Prompts

  • garmin_daily_checkin
  • garmin_weekly_review
  • garmin_intraday_investigation

Resources

  • garmin://capabilities
  • garmin://agent-manifest
  • garmin://summary/daily
  • garmin://summary/weekly

Privacy Model

No Garmin developer app is required.
The MCP does not store the user's Garmin password.
Local tokens are saved with user-only permissions.
Private endpoint drift should be treated as integration drift, not user error.
Profile and goals persist locally to ~/.delx-wellness/profile.json (mode 0600); shared with all 14 Delx Wellness connectors and never uploaded.