Server facts
garminmcp MCP Server
Project
- Author
- davidmosiah
- Repository
- github.com/davidmosiah/garminmcp
- License
- Not specified
- Category
- Data & Analytics
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 13
- Last commit
- Data as of
Overview
Training and recovery reviews in garminmcp draw on Garmin Connect records for sleep, HRV, stress, Body Battery and movement. Daily and weekly summary tools combine available signals into check-ins, scorecards and suggested actions, while date-specific tools let agents examine individual metrics. Activity workflows cover recent workouts, details, laps, weather and heart-rate zones. For closer inspection, an activity-series tool provides calculated statistics and a downsampled metric timeline without returning GPS. A separate wellness-context tool normalizes selected recovery and movement signals for recommendation engines.
Connection checks, a data inventory and example payloads help agents establish what is configured and available before requesting personal records. Authentication happens locally, tokens remain on the user's machine, and tools do not return credentials. Summary is the default privacy mode; structured and raw modes are also configurable, with raw referring to Garmin Connect JSON rather than continuous sensor telemetry. Access uses unofficial personal tokens, not an official Garmin Health API partnership, and private endpoint changes can disrupt it. Some metrics depend on device or account support. These workflows support personal review, not diagnosis or treatment.
garminmcp setup notes
- garminmcp records stdio only; confirm a network transport upstream before planning remote access.
- garminmcp has no recorded license; confirm reuse terms in its repository.