Garmin MCP for Claude: Garmin ships no server, so Wellness Project is the one that works.

What Claude does with your Garmin data. Once the connector is added, Claude calls tools on the Wellness Project MCP server. list_runs returns your runs, list_workouts returns your other sessions, list_sleep returns nightly sleep, and list_wearable_data returns daily steps and heart rate. Claude asks for the date range it needs and reads those rows, so answers come from your own history.

Example prompts for Garmin MCP in Claude. Try "What was my weekly running volume over the last four weeks?", "How has my sleep trended this month?", "Did my sleep get shorter the week my mileage went up?" or "Summarize the Garmin workouts from the last two weeks."

Not every Garmin number crosses over. Wellness Project only sees what Garmin Connect writes to Apple Health or Health Connect. Garmin HRV does not cross either bridge, and Garmin-only scores such as Body Battery and Training Status stay inside Garmin Connect.

Want the longer walkthrough? Read how to connect Garmin to Claude.

GitHub is full of unmaintained device-mcp repos you would have to clone, configure, and keep running yourself. Wellness Project is the hosted, native MCP server. You connect once and it stays connected.

No self-hosting, no tokens to refresh by hand, no broken community repo. The same data Coach Jamie reads is the data your AI reads.

Want to see the tool surface first? The Wellness Project MCP server and tool catalog are documented publicly on GitHub.

Wellness Project MCP vs a self-hosted script. A self-hosted Garmin MCP script from GitHub needs a Python environment, your own Garmin Connect credentials, and someone to keep it running and updated, and it usually reads just the one device. Wellness Project's MCP endpoint is hosted, needs no setup beyond connecting your account, and reads every source you have connected, not just Garmin.