# Garmin Connect (treinos) MCP server

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

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-mcp-dir-garmin-mcp
- Repository: https://github.com/mcp-dir/garmin-mcp

## Install
- Endpoint: https://api.mcp.ai/p_garmin
- Auth: Not captured

## Setup notes
- Remote endpoint: https://api.mcp.ai/p_garmin

## Tools
- garmin_list_accounts - List all Garmin logins linked to this install (id, email, label, created_at). Endpoint: https://api.mcp.ai/p_garmin
- garmin_list_workouts - List saved workouts from Garmin Connect (workout-service). Returns summaries plus raw_data (full JSON string from Garmin). Endpoint: https://api.mcp.ai/p_garmin
- garmin_get_workout - 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. Endpoint: https://api.mcp.ai/p_garmin
- garmin_submit_workout - 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. Endpoint: https://api.mcp.ai/p_garmin
- garmin_edit_workout - 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. Endpoint: https://api.mcp.ai/p_garmin
- garmin_delete_workout - Delete a workout template from Garmin Connect by workout_id.

Bulk support: accepts workout_ids for batched execution. Endpoint: https://api.mcp.ai/p_garmin
- garmin_schedule_workout - 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. Endpoint: https://api.mcp.ai/p_garmin
- garmin_list_scheduled_workouts - List calendar scheduled workouts for a given month/year from Garmin calendar-service. Endpoint: https://api.mcp.ai/p_garmin
- garmin_get_scheduled_workout - Get one scheduled workout entry by scheduled_workout_id.

Bulk support: accepts scheduled_workout_ids for batched execution. Endpoint: https://api.mcp.ai/p_garmin
- garmin_unschedule_workout - Remove workout from calendar by scheduled_workout_id (does not delete the workout template).

Bulk support: accepts scheduled_workout_ids for batched execution. Endpoint: https://api.mcp.ai/p_garmin
- show_version - Show the current MCP platform and adapter versions. Endpoint: https://api.mcp.ai/p_garmin
- report_bug - Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction. Endpoint: https://api.mcp.ai/p_garmin
- connect - 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. Endpoint: https://api.mcp.ai/p_garmin
- toolkit_info - Returns the current toolkit state: installed MCPs, their connection status, and how many catalog tools each exposes. Endpoint: https://api.mcp.ai/p_garmin
- marketplace - 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. Endpoint: https://api.mcp.ai/p_garmin
- authenticate - 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. Endpoint: https://api.mcp.ai/p_garmin

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.mcp-dir
- Version: 0.1.0
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Jun 10, 2026
- Source: https://registry.modelcontextprotocol.io