garmin-givemydata
Related Servers
Alternatives to garmin-givemydata
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceSyncs your own Garmin Personal API data into a local SQLite archive and lets any MCP-capable AI assistant query sleep, HRV, stress, body battery, training and activity trends through natural language, with optional interactive charts. Everything runs locally with your own API key, so private health data stays on your machine.76 PyPI1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to read Garmin Connect data — sleep, heart rate, stress, HRV, body composition, activities, steps, training status/readiness and VO2max trends — through a read-only set of 14 MCP tools. It also generates visualized daily and weekly health reports as Markdown or self-contained HTML+SVG, with credential redaction, dual auth modes, and a mock mode for testing without a real account.1MIT
- AlicenseNot gradedqualityDmaintenanceA local MCP server that exposes your Garmin Connect data—sleep, HRV, training readiness, workouts, and more—to any MCP-compatible AI assistant. Runs entirely on your machine and keeps your Garmin credentials private.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query a local archive of Garmin Connect activities, sleep, HRV, and stress data through read-only MCP tools.1MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to retrieve and analyze Garmin Connect health data, including daily summaries, sleep, HRV, workouts, and raw FIT files, while also supporting SQL queries on the underlying database.10-
- AlicenseAqualityAmaintenanceArchives Garmin Connect health data locally (steps, HR, sleep, body battery) as JSON, no cloud, and also pulls context data (weather, pollen, air quality). Built-in MCP server (with SQLite cache) exposes the archive for querying via LLM tool calls.1127GPL 3.0
TDQS
Scored across 48 tools
Many tools have clearly distinct purposes, but significant overlap exists among metric-specific tools (e.g., garmin_heart_rate vs garmin_hrv vs garmin_hr_zones; garmin_body_battery vs garmin_stress vs garmin_respiration). The presence of catch-all tools like garmin_query and garmin_health_summary alongside specialized ones increases ambiguity about when to use which.
All tools follow a consistent snake_case pattern with the 'garmin_' prefix, making names predictable and easy to recognize as a cohesive set.
48 tools is excessive for a personal health data server, likely overwhelming an agent and causing selection confusion. While the domain is broad, the surface is bloated with many highly specific metrics that could be consolidated.
The toolset covers nearly every Garmin Connect data type: activities, sleep, stress, body battery, training metrics, nutrition, gear, and more. Some gaps remain (e.g., no explicit write/update operations, but those may be out of scope for a read-only client), but overall coverage is extensive.