Garmin Connect MCP Server

Garmin Connect 러닝 데이터를 LLM에 제공하는 MCP(Model Context Protocol) 서버입니다.

Local serverstdioPython

What is the Garmin Connect MCP MCP server?

Garmin Connect MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Garmin Connect MCP directly instead of describing what you should do. Garmin Connect 러닝 데이터를 LLM에 제공하는 MCP(Model Context Protocol) 서버입니다.

What the assistant can call

Once Garmin Connect MCP is connected, these are the calls the assistant has available:

  • GARMIN_EMAIL — Garmin Connect 이메일
  • GARMIN_PASSWORD — Garmin Connect 비밀번호
  • GARMIN_TOKEN_DIR — 토큰 저장 경로
  • GARMINTOKENS — Base64 인코딩 토큰 (CI/Docker용)
  • get_recent_activities — 최근 러닝 활동 목록 (GAP, RWD 포함)
  • get_activities_by_date — 날짜 범위로 러닝 활동 조회
  • get_activity_detail — 활동 상세 정보 (스태미나, 임팩트 로드 포함)
  • get_activity_splits — km별 스플릿 데이터
  • get_activity_weather — 활동 중 날씨 조건 (온도, 습도, 풍속)
  • get_activity_typed_splits — ClimbPro 경사 구간 분석 (등급, GAP)
  • get_weekly_running_summary — 주간 러닝 요약
  • get_monthly_running_summary — 월간 러닝 요약 + 전월 비교

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Choosing this one

Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Garmin Connect MCP's toolset — GARMIN_EMAIL, GARMIN_PASSWORD, GARMIN_TOKEN_DIR and 11 more — is a fair guide to whether it matches your workflow. It is maintained by leewnsdud; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Garmin Connect MCP.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the garmin connect mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
GARMIN_EMAILGarmin Connect 이메일
GARMIN_PASSWORDGarmin Connect 비밀번호
GARMIN_TOKEN_DIR토큰 저장 경로
GARMINTOKENSBase64 인코딩 토큰 (CI/Docker용)
get_recent_activities최근 러닝 활동 목록 (GAP, RWD 포함)
get_activities_by_date날짜 범위로 러닝 활동 조회
get_activity_detail활동 상세 정보 (스태미나, 임팩트 로드 포함)
get_activity_splitskm별 스플릿 데이터
get_activity_weather활동 중 날씨 조건 (온도, 습도, 풍속)
get_activity_typed_splitsClimbPro 경사 구간 분석 (등급, GAP)
get_weekly_running_summary주간 러닝 요약
get_monthly_running_summary월간 러닝 요약 + 전월 비교
get_training_status훈련 상태
get_training_readiness훈련 준비도 점수

How to install the Garmin Connect MCP MCP server

{
  "mcpServers": {
    "garmin-mcp": {
      "command": "/Users/<username>/.local/bin/uv",
      "args": [
        "--directory",
        "/path/to/garmin-mcp",
        "run",
        "garmin-mcp"
      ]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Garmin Connect MCP to GARMIN EMAIL.
  • Use Garmin Connect MCP to GARMIN PASSWORD.
  • Use Garmin Connect MCP to GARMIN TOKEN DIR.

Frequently asked questions

It connects Garmin Connect MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (GARMIN_EMAIL, GARMIN_PASSWORD, GARMIN_TOKEN_DIR, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Garmin Connect MCP directly.