Garmin MCP Server
Related Servers
Alternatives to Garmin MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceA read-only remote MCP server that connects MCP clients such as Claude to a personal Garmin Connect account through Garmin's official Personal API. It lets users ask natural-language questions about recovery, HRV, sleep, Body Battery, stress, heart rate and recorded activities from phone or desktop.1,323 npmMIT
- AlicenseAqualityBmaintenanceA read-only MCP server that lets AI assistants query a user's own training, recovery, sleep, activity, and wellness data through the official Garmin Connect Personal API. It can run locally or be self-hosted on Cloudflare Workers for access from Claude and other MCP clients.27575 npmMIT
- AlicenseNot gradedqualityNot gradedmaintenanceA read-only remote MCP server that lets Claude query your own Garmin Connect wellness and activity data — sleep, HRV, Body Battery, stress, heart rate, daily summaries, and workout details — through Garmin's official Personal API, with OAuth sign-in so it works from mobile and desktop clients.MIT
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server that lets a chat assistant query Garmin Connect personal data such as activities, sleep, HRV, Body Battery, stress, and weight to act as a personal coach. It runs locally over stdio in Claude Desktop or as a hosted HTTP service secured with OAuth 2.1 and PKCE, and none of its tools can modify data.MIT
- AlicenseAqualityBmaintenanceEnables MCP-capable AI apps to query a user's own Garmin sleep, HRV, stress, Body Battery, heart-rate, activity, and body-metric data through Garmin's official Personal API in a read-only, locally run setup.1487 PyPI1MIT
- AlicenseNot gradedqualityNot gradedmaintenanceThis server provides a read-only remote connection between MCP clients and a Garmin Connect account. It allows users to query extensive personal health and activity data using natural language.MIT
TDQS
Scored across 21 tools
Most tools target clearly distinct Garmin data domains and actions, such as activities, sleep, HRV, weight, and profile settings. The main ambiguity comes from singular/range pairs like get_daily_summary vs. get_daily_summaries and get_sleep vs. get_sleep_summaries, though the descriptions clarify their intended use.
The tool set is overwhelmingly consistent snake_case and mostly follows a get_<resource> pattern, with search_activities as the main verb deviation. Singular/plural naming variants like summary/summaries and range-specific suffixes are readable but slightly inconsistent.
At 21 tools, the surface is somewhat large but reflects the broad Garmin wellness and activity domain. Each metric group is reasonably scoped, though some singular/range pairs could potentially be consolidated.
The server covers a wide range of read-only Garmin data: activities, workouts, daily wellness, sleep, HRV, SpO2, hydration, weight, and profile settings. Some secondary areas such as devices, training status, VO2 max, or personal records are absent, but core health and activity workflows are well covered.