garmin_mcp
Verified Safeby Taxuspt
Overview
Connects to Garmin Connect to expose fitness and health data to MCP-compatible clients like Claude.
Installation
npx @modelcontextprotocol/inspector uv run garmin-mcpEnvironment Variables
- GARMIN_EMAIL
- GARMIN_EMAIL_FILE
- GARMIN_PASSWORD
- GARMIN_PASSWORD_FILE
- GARMINTOKENS
- GARMINTOKENS_BASE64
Security Notes
The server handles Garmin Connect credentials by reading them from environment variables or specified files, and stores OAuth tokens locally in user-specified directories (`~/.garminconnect` by default). The README provides good advice on using `chmod 600` for credential files. Multi-Factor Authentication (MFA) requires an initial interactive login, which is explicitly handled. No obvious 'eval' or malicious patterns were found. Minor risk of exposing internal error details in tool responses, but acceptable for a personal server. Overall, secure practices are followed for a local application.
Similar Servers
intervals-mcp-server
Connects AI models (Claude, ChatGPT) with the Intervals.icu API to retrieve and manage athlete fitness data, including activities, events, and wellness metrics.
hevy-mcp
An MCP server enabling AI assistants to access and manage workout data, routines, exercise templates, and webhooks through the Hevy fitness tracking API.
pierre_mcp_server
A multi-tenant web dashboard and API server for managing and monitoring fitness data (activities, sleep, recovery, nutrition) and AI-powered fitness intelligence.
pinax-mcp
Connects MCP-compatible clients (e.g., Claude Desktop) to remote MCP servers, specifically The Graph Token API, by acting as a bridge between stdio and HTTP/SSE transports.