Skip to main content
Glama
marcelfortmann

garmin-mcp

by marcelfortmann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
whoamiA

Check the Garmin connection and return the logged-in account profile (display name, full name).

get_daily_healthA

Daily wellness metrics for a date. Pick one or more via metrics: summary, sleep, stress, heart_rate, hrv, spo2, respiration, hydration, steps, floors, intensity_minutes, body_battery, body_battery_events, stats_and_body.

get_trainingA

Training metrics for a date. Pick via metrics: readiness, morning_readiness, status, vo2max, fitness_age.

get_fitnessA

Fitness/performance metrics. Pick via metrics: race_predictions, cycling_ftp, lactate_threshold, personal_records (all latest, date-agnostic), and endurance_score, hill_score, resting_heart_rate, weekly_intensity_minutes (over the given date range).

get_weightA

Body weight & body composition (weight, BMI, body-fat %) over a date range. Set include_raw for the individual weigh-in entries too. Default range: the last ~4 weeks.

get_steps_history

Step totals over a date range. granularity 'daily' (Garmin caps the span at 28 days) or 'weekly'. Default: daily, last ~4 weeks.

get_activity

Data for a single activity by activityId. Pick via include: summary, splits, weather, details (GPS/HR/power streams), hr_zones, exercise_sets.

list_activities

List activities. Without dates: the most recent ones (use limit=1 for the last activity). With startDate/endDate and/or type: activities in that range, optionally filtered by type (e.g. running, cycling, swimming).

get_devicesA

Garmin devices paired to the account (model, firmware, last sync).

get_user_profileA

User profile & settings: units, preferences, activity level, etc.

get_goals

Goals filtered by status (active, future, or past).

get_workouts

Saved workouts on the account.

get_scheduled_workouts

Scheduled workouts / calendar for a month (defaults to the current month).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 7 tools

Disambiguation5/5

Each tool targets a distinct aspect of Garmin data: account info, weight, profile, daily health, training metrics, fitness/performance, and devices. No overlapping purposes.

Naming Consistency5/5

All tools use consistent snake_case verb_noun pattern (e.g., get_weight, get_user_profile), with 'whoami' as a minor but acceptable variation.

Tool Count5/5

7 tools cover a broad health/fitness domain without being excessive. The count is well-scoped for the server's purpose.

Completeness4/5

Covers major data categories (profile, weight, daily health, training, fitness, devices). Minor gaps like detailed activity logs are absent, but overall surface is solid for a read-only server.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources