# Garmin Connect (treinos) (remote · api.mcp.ai)

List, fetch, create, edit (replace), delete and schedule structured workouts on Garmin Connect (runn

- Trust score: 63/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.mcp.ai`: 63/100 (this document), [markdown](https://verifymcp.io/servers/mcp-dir-garmin-mcp/p-garmin.md), [page](https://verifymcp.io/servers/mcp-dir-garmin-mcp/p-garmin)

## Channel facts

- Endpoint: `https://api.mcp.ai/p_garmin`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 1448 tokens (~90/item across 16 items; 16 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http mcp-dir-garmin-mcp https://api.mcp.ai/p_garmin
```

### Codex

```toml
[mcp_servers.mcp-dir-garmin-mcp]
url = "https://api.mcp.ai/p_garmin"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mcp-dir-garmin-mcp": {
      "type": "remote",
      "url": "https://api.mcp.ai/p_garmin",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mcp-dir-garmin-mcp --url https://api.mcp.ai/p_garmin --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mcp-dir-garmin-mcp:
    url: "https://api.mcp.ai/p_garmin"
```

### Other

```json
{
  "mcpServers": {
    "mcp-dir-garmin-mcp": {
      "type": "http",
      "url": "https://api.mcp.ai/p_garmin"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-08-03 (score 63, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 0.9.200 → 0.9.201

### 2026-08-02 (score 62, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 0.9.197 → 0.9.200

### 2026-08-01 (score 62, +1)

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

### 2026-07-31 (score 61, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 58, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 58, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 0.9.184 → 0.9.194

### 2026-07-28 (score 57, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 0.9.180 → 0.9.184

### 2026-07-27 (score 56, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (16)

### `garmin_list_accounts` (~36 tokens)

List all Garmin logins linked to this install (id, email, label, created_at).

Input parameters:

- `account` (string)

### `garmin_list_workouts` (~55 tokens)

List saved workouts from Garmin Connect (workout-service). Returns summaries plus raw_data (full JSON string from Garmin).

Input parameters:

- `account` (string)
- `limit` (number)
- `start` (number)

### `garmin_get_workout` (~68 tokens)

Get one workout template by workout_id (full structure: segments, steps, targets). Includes raw_data JSON string.

Bulk support: accepts workout_ids for batched execution.

Input parameters:

- `account` (string)
- `workout_id` (string, required)
- `workout_ids` (array)

### `garmin_submit_workout` (~118 tokens)

Create a new structured workout on Garmin Connect. Body must match Garmin API (workoutName, sportType, workoutSegments with ExecutableStepDTO / RepeatGroupDTO). You may omit displayOrder/displayable everywhere and the endCondition on RepeatGroupDTO — the server normalizes them automatically (see workout.description). Multi-sport: sportTypeKey multi_sport (typically sportTypeId 5) with one segment per discipline. Returns workout_id and raw_data.

Input parameters:

- `account` (string)
- `workout` (object, required)

### `garmin_edit_workout` (~82 tokens)

Replace a workout: uploads a new workout from payload, then deletes workout_id (no native PUT). Returns new workout_id and previous_workout_id.

Bulk support: accepts workout_ids for batched execution.

Input parameters:

- `account` (string)
- `workout` (object, required)
- `workout_id` (string, required)
- `workout_ids` (array)

### `garmin_delete_workout` (~56 tokens)

Delete a workout template from Garmin Connect by workout_id.

Bulk support: accepts workout_ids for batched execution.

Input parameters:

- `account` (string)
- `workout_id` (string, required)
- `workout_ids` (array)

### `garmin_schedule_workout` (~83 tokens)

Schedule an existing workout onto the calendar. date must be YYYY-MM-DD (or ISO-8601 date prefix). Returns Garmin schedule response as raw_data.

Bulk support: accepts workout_ids for batched execution.

Input parameters:

- `account` (string)
- `date` (string, required)
- `workout_id` (string, required)
- `workout_ids` (array)

### `garmin_list_scheduled_workouts` (~48 tokens)

List calendar scheduled workouts for a given month/year from Garmin calendar-service.

Input parameters:

- `account` (string)
- `month` (number, required)
- `year` (number, required)

### `garmin_get_scheduled_workout` (~64 tokens)

Get one scheduled workout entry by scheduled_workout_id.

Bulk support: accepts scheduled_workout_ids for batched execution.

Input parameters:

- `account` (string)
- `scheduled_workout_id` (string, required)
- `scheduled_workout_ids` (array)

### `garmin_unschedule_workout` (~69 tokens)

Remove workout from calendar by scheduled_workout_id (does not delete the workout template).

Bulk support: accepts scheduled_workout_ids for batched execution.

Input parameters:

- `account` (string)
- `scheduled_workout_id` (string, required)
- `scheduled_workout_ids` (array)

### `show_version` (~17 tokens)

Show the current MCP platform and adapter versions.

### `report_bug` (~50 tokens)

Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

Input parameters:

- `context` (string)
- `conversation` (string)
- `message` (string, required)

### `connect` (~42 tokens)

Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.

### `toolkit_info` (~30 tokens)

Returns the current toolkit state: installed MCPs, their connection status, and how many catalog tools each exposes.

### `marketplace` (~402 tokens)

The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin.

Input parameters:

- `action` (string)
- `arguments` (string)
- `cancel_comment` (string)
- `cancel_reason` (string)
- `conversation` (string)
- `immediate` (boolean)
- `limit` (number)
- `mcp_id` (string)
- `message` (string)
- `query` (string)
- `report_context` (string)
- `request_details` (string)
- `request_name` (string)
- `tier_slug` (string)
- `tool_id` (string)

### `authenticate` (~99 tokens)

MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.

Input parameters:

- `token` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mcp-dir-garmin-mcp/p-garmin#diagnostics

## Score history

- 2026-08-03: 63
- 2026-08-02: 62
- 2026-08-01: 62
- 2026-07-31: 61
- 2026-07-30: 58
- 2026-07-29: 58
- 2026-07-28: 57
- 2026-07-27: 56
- 2026-07-26: 56

## Links

- Remote endpoint: https://api.mcp.ai/p_garmin
- Repository: https://github.com/mcp-dir/garmin-mcp
- Changelog RSS feed: https://verifymcp.io/servers/mcp-dir-garmin-mcp/p-garmin/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/mcp-dir-garmin-mcp/p-garmin/changelog.json
- HTML version of this page: https://verifymcp.io/servers/mcp-dir-garmin-mcp/p-garmin