Garth MCP Server — Garmin Connect Health Data

Garth MCP server enabling AI agents to access Garmin Connect health and fitness data — fetching activity history, sleep data, heart rate metrics, running/cycling stats, and health body battery data, integrating Garmin's fitness tracking into agent-driven health analytics and personal wellness workflows.

Evaluated Mar 06, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Productivity garmin fitness health mcp-server garmin-connect wearables activity-tracking
⚙ Agent Friendliness
66
/ 100
Can an agent use this?
🔒 Security
73
/ 100
Is it safe for agents?
⚡ Reliability
62
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
65
Documentation
68
Error Messages
65
Auth Simplicity
72
Rate Limits
62

🔒 Security

TLS Enforcement
90
Auth Strength
68
Scope Granularity
65
Dep. Hygiene
68
Secret Handling
72

Unofficial API. Credentials locally stored — secure. Health data sensitive. GDPR applies. Community MCP.

⚡ Reliability

Uptime/SLA
65
Version Stability
62
Breaking Changes
60
Error Recovery
60
AF Security Reliability

Best When

A Garmin device user wants AI agents to analyze their fitness and health data from Garmin Connect for coaching, trend analysis, or personal health tracking.

Avoid When

You don't use Garmin devices, or need real-time biometric streaming — use Apple HealthKit or Fitbit MCPs for those ecosystems.

Use Cases

  • Fetching recent Garmin activity data from health coaching agents
  • Analyzing sleep patterns from wellness tracking agents
  • Reviewing running and cycling metrics from training planning agents
  • Monitoring heart rate variability from health analytics agents
  • Building personalized fitness recommendations from workout planning agents
  • Integrating Garmin data into holistic health dashboards from quantified-self agents

Not For

  • Non-Garmin device users (Fitbit, Apple Watch, Whoop users need different MCPs)
  • Real-time streaming data (Garmin Connect API is not real-time streaming)
  • Medical diagnosis purposes (consumer fitness data, not medical grade)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
Yes
Webhooks
No

Authentication

Methods: username_password
OAuth: No Scopes: No

Garmin Connect username and password required. Uses Garth Python library (unofficial Garmin Connect API client). No official Garmin Connect API for third-party — uses internal endpoints.

Pricing

Model: free
Free tier: Yes
Requires CC: No

Community MCP using Garth (unofficial Garmin Connect client). Free.

Agent Metadata

Pagination
none
Idempotent
Full
Retry Guidance
Not documented

Known Gotchas

  • Uses unofficial Garmin Connect internal API — can break without notice after Garmin updates
  • Garmin may implement MFA/2FA that disrupts automation
  • Data sync latency — activities may take hours to appear in Garmin Connect
  • Community MCP from matin (Garth library author) — well-maintained for unofficial API
  • Health data is sensitive — treat with appropriate privacy controls
  • MFA/CAPTCHA may block automated login — monitor for auth failures

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Garth MCP Server — Garmin Connect Health Data.

$99

Scores are editorial opinions as of 2026-03-06.

5208
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered