Garminmcp MCP Server

What the code does

We read the source, 2 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

  const run = spawnSync(python, [helperPath, config.tokenPath], {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add garminmcp -- npx -y garmin-mcp-unofficial

{
  "mcpServers": {
    "garminmcp": {
      "command": "npx",
      "args": [
        "-y",
        "garmin-mcp-unofficial"
      ]
    }
  }
}

[mcp_servers.garminmcp]
command = "npx"
args = ["-y", "garmin-mcp-unofficial"]

{
  "mcpServers": {
    "garminmcp": {
      "command": "npx",
      "args": [
        "-y",
        "garmin-mcp-unofficial"
      ]
    }
  }
}

{
  "servers": {
    "garminmcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "garmin-mcp-unofficial"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: GARMIN_TOKEN_PATH (Optional local path for Garmin Connect tokens. Defaults to ~/.garmin-mcp/garmin_tokens.json. Create it with garmin-mcp-server auth (self-contained Node login, no Python)), GARMIN_PRIVACY_MODE (Optional payload mode: summary, structured, or raw. Defaults to structured. raw means full supported Garmin Connect payloads, not unrestricted raw sensor telemetry), GARMIN_CACHE (Optional SQLite cache toggle. Set to true or sqlite to enable), GARMIN_CACHE_PATH (Optional local SQLite cache path. Defaults to ~/.garmin-mcp/cache.sqlite), GARMIN_DOMAIN (Optional Garmin domain override. Use garmin.cn only for China accounts; default is garmin.com), GARMIN_NO_CACHE (Set to true to bypass the in-memory HTTP response cache (60s TTL for GET only). POST/PUT/DELETE and 4xx/5xx responses are never cached regardless).