{"id":"taxuspt-garmin-mcp","name":"garmin_mcp","af_score":52.5,"security_score":64.0,"reliability_score":28.8,"what_it_does":"An MCP server that connects to Garmin Connect (via the python-garminconnect library) and exposes fitness/health data and related operations as a large set of MCP tools for MCP-compatible clients (e.g., Claude Desktop). Includes an auth CLI to pre-authenticate and persist OAuth tokens for MFA and subsequent use.","best_when":"You want a local MCP toolset to query your Garmin Connect data through an MCP client, and you can run a one-time/occasional pre-auth flow to handle Garmin login + possible MFA.","avoid_when":"You need a hosted SaaS API with no local credentials/token handling, or you require strict rate-limit SLAs and clearly published API error codes for programmatic retries beyond MCP-level behavior.","last_evaluated":"2026-03-30T13:33:40.325061+00:00","has_mcp":true,"has_api":false,"auth_methods":["Pre-auth via garmin-mcp-auth CLI (saves OAuth tokens to ~/.garminconnect or a configured token path)","Environment-variable credentials (GARMIN_EMAIL, GARMIN_PASSWORD) for initial auth / interactive mode","MFA handled during the pre-auth / interactive auth flow"],"has_free_tier":false,"known_gotchas":["MFA may require a one-time pre-auth step because MCP servers run without an interactive terminal","Token expiry is periodic (README suggests ~6 months), requiring re-auth with --force-reauth","Some high-data-volume endpoints (e.g., activity details with large GPS/chart data) are skipped; agents must use the lighter get_activity() tools instead","Claude Desktop may fail to spawn the process if uvx is not in PATH; use full path to uvx"],"error_quality":0.0}