# io.github.slaat/garmin-connect-workouts-mcp (npm · garmin-connect-workouts-mcp)

Turn plain language into real workouts on your Garmin watch: pace, HR, power, intervals, swim sets.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `garmin-connect-workouts-mcp`: 78/100 (this document), [markdown](https://verifymcp.io/servers/slaat-garmin-connect-workouts-mcp/garmin-connect-workouts-mcp.md), [page](https://verifymcp.io/servers/slaat-garmin-connect-workouts-mcp/garmin-connect-workouts-mcp)

## Channel facts

- Registry: `npm`
- Package: `garmin-connect-workouts-mcp`
- Version: `1.1.3`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 35 of 121 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 17 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1247 tokens (~155/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.slaat/garmin-connect-workouts-mcp server?

io.github.slaat/garmin-connect-workouts-mcp runs locally as an npm package, launched with npx -y garmin-connect-workouts-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add slaat-garmin-connect-workouts-mcp -- npx -y garmin-connect-workouts-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "slaat-garmin-connect-workouts-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "garmin-connect-workouts-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "slaat-garmin-connect-workouts-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "garmin-connect-workouts-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add slaat-garmin-connect-workouts-mcp -- npx -y garmin-connect-workouts-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "slaat-garmin-connect-workouts-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "garmin-connect-workouts-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add slaat-garmin-connect-workouts-mcp --command npx --arg -y --arg garmin-connect-workouts-mcp
```

### Hermes

```yaml
mcp_servers:
  slaat-garmin-connect-workouts-mcp:
    command: "npx"
    args: ["-y", "garmin-connect-workouts-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "slaat-garmin-connect-workouts-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "garmin-connect-workouts-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add slaat-garmin-connect-workouts-mcp -t stdio -c npx -a -y garmin-connect-workouts-mcp
```

### Other

```json
{
  "mcpServers": {
    "slaat-garmin-connect-workouts-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "garmin-connect-workouts-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 74, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-03 (score 70, +26)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.87

### 2026-09-02 (score 44)

First indexed and scored.

## MCP tools (8)

### `create_garmin_workout` (~286 tokens)

Create a new structured workout in Garmin Connect from typed steps: durations, pace/HR/power/cadence targets, repeat blocks for intervals, and swim-specific stroke/equipment/pool-length fields. Use to add a workout; to change one that exists, use update_garmin_workout instead. Returns the new workoutId and a Connect link. Returns a re-auth message, not an exception, if no valid session exists. Example: [{kind:'step', intensity:'warmup', duration:{type:'time', value:10, unit:'min'}}, {kind:'repeat', iterations:5, steps:[...]}].

Input parameters:

- `name` (string, required): Workout name, shown in Garmin Connect and on the device.
- `poolLength` (number): Swimming only - pool length for this workout, e.g. 25. Only valid when sport is 'swimming'.
- `poolLengthUnit` (string): Swimming only - unit for poolLength. Defaults to 'm' when poolLength is given without a unit.
- `sport` (string): Sport for this workout: running, cycling, or swimming. Governs which target types apply and whether stroke/equipment/poolLength are used. Defaults to running.
- `steps` (array, required): The ordered list of steps and repeat blocks that make up the workout, in the order they should be performed.

### `list_garmin_workouts` (~127 tokens)

List workouts stored in the Garmin Connect account, most recent first, with each workout's name, sport, and workoutId. Use this to find a workoutId to pass to get_garmin_workout, update_garmin_workout, delete_garmin_workout, or schedule_garmin_workout. Read-only. If no valid session exists, returns a message asking you to run authenticate_garmin rather than throwing.

Input parameters:

- `limit` (integer): Maximum number of workouts to return, most recent first. Defaults to 20, capped at 100.

### `get_garmin_workout` (~127 tokens)

Fetch the complete stored structure (all steps, targets, repeat blocks) of one workout by its workoutId, as raw JSON. Use this to inspect a workout, or to get its full contents before calling update_garmin_workout, which replaces the entire workout rather than patching it. Read-only. If no valid session exists, returns a message asking you to run authenticate_garmin rather than throwing.

Input parameters:

- `workoutId` (number, required): The numeric Garmin workout id, as returned by create_garmin_workout or listed by list_garmin_workouts.

### `update_garmin_workout` (~269 tokens)

Replace the entire contents (name, sport, steps, pool settings) of an existing workout, identified by workoutId, keeping its id. This is a full overwrite, not a partial patch - fields you omit are dropped. Call get_garmin_workout first to see the current contents before changing them. If no valid session exists, returns a message asking you to run authenticate_garmin rather than throwing.

Input parameters:

- `name` (string, required): Workout name, shown in Garmin Connect and on the device.
- `poolLength` (number): Swimming only - pool length for this workout, e.g. 25. Only valid when sport is 'swimming'.
- `poolLengthUnit` (string): Swimming only - unit for poolLength. Defaults to 'm' when poolLength is given without a unit.
- `sport` (string, required): Sport for this workout: running, cycling, or swimming. Governs which target types apply and whether stroke/equipment/poolLength are used.
- `steps` (array, required): The ordered list of steps and repeat blocks that make up the workout, in the order they should be performed.
- `workoutId` (number, required): The numeric Garmin workout id, as returned by create_garmin_workout or listed by list_garmin_workouts.

### `delete_garmin_workout` (~112 tokens)

Permanently delete a workout from Garmin Connect by workoutId. This is irreversible - there is no undo or trash. Use list_garmin_workouts or get_garmin_workout first to confirm you have the right workoutId. If no valid session exists, returns a message asking you to run authenticate_garmin rather than throwing.

Input parameters:

- `workoutId` (number, required): The numeric Garmin workout id, as returned by create_garmin_workout or listed by list_garmin_workouts.

### `schedule_garmin_workout` (~154 tokens)

Put an existing workout on the Garmin Connect calendar for a specific date, so it appears as a planned session and can sync to a device. Requires a workoutId already created via create_garmin_workout or found via list_garmin_workouts - this tool does not create workouts. If no valid session exists, returns a message asking you to run authenticate_garmin rather than throwing.

Input parameters:

- `date` (string, required): Calendar date to schedule the workout on, in YYYY-MM-DD format, e.g. '2026-09-15'.
- `workoutId` (number, required): The numeric Garmin workout id, as returned by create_garmin_workout or listed by list_garmin_workouts.

### `check_garmin_auth` (~81 tokens)

Probe whether the stored Garmin Connect session is still valid, using a cheap authenticated request rather than a local expiry check (Garmin's session cookie does not carry a reliable expiry). Use this first when unsure whether the other tools will work. Returns a message telling you to run authenticate_garmin if the session is missing or has expired; never throws.

### `authenticate_garmin` (~91 tokens)

Authenticate with Garmin Connect by opening a real browser window at connect.garmin.com for you to log in normally, then capture and store only the resulting session cookies and CSRF token (never your password). Run this whenever check_garmin_auth reports no valid session, or any other tool returns its 'not authenticated' message. Requires a local display; will not work in a headless-only environment.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/slaat-garmin-connect-workouts-mcp/garmin-connect-workouts-mcp#diagnostics

## Score history

- 2026-09-20: 78
- 2026-09-19: 78
- 2026-09-18: 77
- 2026-09-17: 77
- 2026-09-16: 76
- 2026-09-15: 76
- 2026-09-14: 76
- 2026-09-13: 75
- 2026-09-12: 75
- 2026-09-11: 74
- 2026-09-10: 74
- 2026-09-09: 70
- 2026-09-08: 70
- 2026-09-07: 70
- 2026-09-06: 70
- 2026-09-05: 70
- 2026-09-04: 70
- 2026-09-03: 70
- 2026-09-02: 44

## Common questions

### What is the io.github.slaat/garmin-connect-workouts-mcp server?

io.github.slaat/garmin-connect-workouts-mcp is listed in the public MCP registry as io.github.slaat/garmin-connect-workouts-mcp. Turn plain language into real workouts on your Garmin watch: pace, HR, power, intervals, swim sets. This page covers its npm package (garmin-connect-workouts-mcp).

### Is the io.github.slaat/garmin-connect-workouts-mcp server safe to use?

io.github.slaat/garmin-connect-workouts-mcp scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.slaat/garmin-connect-workouts-mcp server expose?

io.github.slaat/garmin-connect-workouts-mcp exposes 8 tools: create_garmin_workout, list_garmin_workouts, get_garmin_workout, update_garmin_workout, delete_garmin_workout, and 3 more. Their descriptions and schemas cost roughly 1,247 tokens of context every time the server is loaded.

### Is the io.github.slaat/garmin-connect-workouts-mcp server still maintained?

io.github.slaat/garmin-connect-workouts-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.slaat/garmin-connect-workouts-mcp server under?

io.github.slaat/garmin-connect-workouts-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/garmin-connect-workouts-mcp
- Socket report: https://socket.dev/npm/package/garmin-connect-workouts-mcp
- Repository: https://github.com/slaat/garmin-connect-workouts-mcp
- Changelog RSS feed: https://verifymcp.io/servers/slaat-garmin-connect-workouts-mcp/garmin-connect-workouts-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/slaat-garmin-connect-workouts-mcp/garmin-connect-workouts-mcp.json
- HTML version of this page: https://verifymcp.io/servers/slaat-garmin-connect-workouts-mcp/garmin-connect-workouts-mcp