anup-shesh/garmin-local-mcp

Overview

Local-first Garmin data warehouse with an analysis-grade MCP server. Sync once, analyze forever even when the API is down.

Best for

Best for
Developers who want to locally archive and analyze their Garmin health data without relying on the API

Use cases

• Store Garmin health data locally for long-term analysis
• Run queries against personal fitness data without live API dependency
• Build custom dashboards or apps on top of synced Garmin data

How to use

Install

uvx garmin-local-mcp --help

Tools exposed

• auth_status
• sync_status
• get_day
• query_metrics
• list_activities
• get_activity
• import_fit
• request_delay_seconds
• baseline_window_days
• GARMIN_MCP_DATA_DIR

Tested with

Claude Desktop, Claude Code, Cursor

Example client config

{\n  "mcpServers": {\n    "garmin": {\n      "command": "garmin-local-mcp",\n      "args": ["serve"]\n    }\n  }\n}

Notes

Local-first Garmin data warehouse with an analysis-grade MCP server. Sync once, analyze forever even when the API is down.

2 stars on GitHub. Last updated 2026-07-11. Licensed MIT.

Use cases

• Store Garmin health data locally for long-term analysis
• Run queries against personal fitness data without live API dependency
• Build custom dashboards or apps on top of synced Garmin data

Pros

• Local-first design ensures privacy and offline access
• Analysis-grade MCP server supports standard tool integration
• Sync once and remain independent of API availability

Cons

• Very new with only 2 GitHub stars, indicating limited community adoption
• Requires Python environment setup and configuration
• Documentation and stability may be minimal at this stage

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.