garmin-mcp
Enables users to access and analyze Garmin Connect data through natural language, supporting multi-user setups, SQLite-backed history, and optional remote access via Cloudflare Tunnel.
README
Garmin MCP Server
Self-hosted Model Context Protocol server for Garmin Connect: multi-user, SQLite-backed history, HTTP/SSE for Claude custom connectors, optional Cloudflare Tunnel, and an agentic “sports companion” layer (bootstrap context, workout prompt, goals, flags).
Architecture
flowchart TD
Claude[ClaudeConnector] --> Tunnel[CloudflareTunnel]
Tunnel --> App[garmin-mcp]
App --> MW[ApiKeyAndRateLimit]
MW --> MCP[FastMCP_SSE]
MCP --> Tools[Tools]
Tools --> DB[(SQLite_WAL)]
Sync[SyncService] --> Garmin[Garmin_API]
Garmin --> Sync
Sync --> DB
Prerequisites
- Docker and Docker Compose
- Garmin account (see Garmin MFA below)
- Cloudflare account if using Tunnel
Quick start
- Clone this repository.
- Copy
config.example.yamltoconfig.yamland fill in credentials, API keys, encryption secrets, and paths. - Set
TUNNEL_TOKENin the environment (e.g..envnext todocker-compose.yml) if using Cloudflare Tunnel. - Run
docker compose up -d(ormake up). - Open Claude → Settings → Connectors → Add custom connector: base URL
https://<your-tunnel-host>/mcp(or your public URL), headerX-API-Key: <user api_key>.
Configuration reference
| Field | Type | Default | Description |
|---|---|---|---|
port |
int | 8765 |
HTTP port |
log_level |
string | info |
Logging level |
sync_interval_minutes |
int | 30 |
Background sync interval |
max_date_range_days |
int | 90 |
Max date span for tools |
users[].name |
string | — | Username (must match /sync/{username}) |
users[].api_key |
string | — | Secret for X-API-Key |
users[].db_path |
path | — | SQLite file |
users[].backup_path |
path | — | Backup directory (default example uses /data/backups/{name}/ outside the repo) |
users[].timezone |
string | — | IANA timezone for display |
users[].rate_limit |
int | 30 |
Requests per minute per user |
users[].initial_sync_days |
int | 365 |
First full history pull |
users[].flag_rules |
object | — | Thresholds for proactive flags |
Multi-user setup
Each users[] entry is isolated: its own Garmin credentials, API key, encrypted token file, SQLite DB, and backups.
Garmin MFA / Two-Factor Authentication
Garmin must have MFA disabled for automated login. Configure your account at:
https://account.garmin.com/account/security/
Rotating an API Key
- Edit
config.yamland update theapi_keyvalue for the relevant user. - Run
make down && make upto restart the container. - Update the
X-API-Keyheader value in the Claude custom connector settings for that user. - Verify with
make logsthat the server restarted cleanly.
Sports companion: custom instructions
Add this to Claude’s custom instructions so every session bootstraps fresh data:
You are my personal sports coach with access to my Garmin data.
At the start of every conversation, call get_my_context to load
my current goals, recent training history, and latest data before
responding to anything.
MCP prompt: analyze_new_workout
Registered as a named prompt. Use when the user asks to analyze the latest workout or last run; it follows the structured steps documented in the server (context → activities → detail → reasoning → suggest → feeling).
Makefile
| Target | Purpose |
|---|---|
make up |
docker compose up -d |
make down |
docker compose down |
make logs |
Follow logs |
make test |
Pytest suite |
make lint |
Ruff check + format check |
make format |
Apply Ruff formatter |
make sync |
scripts/sync_all.py — POST /sync/{user} for each user (server must be running) |
make backup |
POST /backup/all (set GARMIN_API_KEY to any user’s key) |
make shell |
Shell in garmin-mcp container |
make validate |
Compose config + config schema load |
Running tests
python -m venv .venv && .venv/bin/pip install -r requirements.txt
pytest tests/ -v
Troubleshooting
- Token expiry / auth errors: Check Garmin credentials; delete encrypted token file and restart; see logs.
- Port conflicts: Change
portinconfig.yamland compose port mapping. - Tunnel not connecting: Verify
TUNNEL_TOKENand Cloudflare route tohttp://garmin-mcp:8765. make syncfails: The server must be reachable athttp://127.0.0.1:8765(or setGARMIN_MCP_URL). Start withmake upfirst.- Backups in repo: Prefer
backup_pathunder/data/...(Docker volume). If you store backups inside the repo, extend.gitignoreaccordingly.
License
See LICENSE.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。