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.
Available components
Last scanned (4 hours ago)
Scores higher than 61% of npm servers
Category IoT and Hardware
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. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 34 of 119 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 63 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Oct 26 +1
- Stability: 0.97 → pass security
- 29 Oct 26 −1
- Stability: pass → 0.93 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 +1
- Stability: 0.97 → pass security
- 22 Oct 26 −1
- Stability: pass → 0.97 functional
- 16 Oct 26 +1
- Stability: 0.97 → pass security
- 13 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 11 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/garmin-connect-workouts-mcp@1.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 119 packages
| Packages resolved | 119 |
|---|---|
| Stale | 34 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
authenticate_garmin ~91
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
check_garmin_auth ~81
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_garmin_workout ~286
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:[...]}].
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | 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 | yes | The ordered list of steps and repeat blocks that make up the workout, in the order they should be performed. |
No output schema declared.
No examples provided.
delete_garmin_workout ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| workoutId | number | yes | The numeric Garmin workout id, as returned by create_garmin_workout or listed by list_garmin_workouts. |
No output schema declared.
No examples provided.
get_garmin_workout ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| workoutId | number | yes | The numeric Garmin workout id, as returned by create_garmin_workout or listed by list_garmin_workouts. |
No output schema declared.
No examples provided.
list_garmin_workouts ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of workouts to return, most recent first. Defaults to 20, capped at 100. |
No output schema declared.
No examples provided.
schedule_garmin_workout ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Calendar date to schedule the workout on, in YYYY-MM-DD format, e.g. '2026-09-15'. |
| workoutId | number | yes | The numeric Garmin workout id, as returned by create_garmin_workout or listed by list_garmin_workouts. |
No output schema declared.
No examples provided.
update_garmin_workout ~269
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | 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 | yes | Sport for this workout: running, cycling, or swimming. Governs which target types apply and whether stroke/equipment/poolLength are used. |
| steps | array | yes | The ordered list of steps and repeat blocks that make up the workout, in the order they should be performed. |
| workoutId | number | yes | The numeric Garmin workout id, as returned by create_garmin_workout or listed by list_garmin_workouts. |
No output schema declared.
No examples provided.
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.
npm · garmin-connect-workouts-mcp
claude mcp add slaat-garmin-connect-workouts-mcp -- npx -y garmin-connect-workouts-mcp
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 79 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 5 November 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.