Skip to main content
Glama
Garmin MCP Server

Garmin MCP Server

by nitinmms

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GARMIN_PERSONAL_API_KEYYesYour Garmin Connect Personal API key, created at https://connect.garmin.com/app/settings/personalApiToken. The server uses it to obtain and renew access tokens.

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_activitiesB

Search recorded activities (runs, rides, swims, strength, ...), newest first.

Args: start_date: Earliest activity date, YYYY-MM-DD. end_date: Latest activity date, YYYY-MM-DD. activity_type: Garmin activity type key, e.g. "running", "cycling", "lap_swimming". search: Free-text match on activity name. limit: Page size (1-100). start: Offset for pagination.

get_activityB

Get one activity's summary, metadata, measurements and split summaries.

get_activity_workoutsC

Get the structured workouts performed during an activity.

get_daily_summaryB

Get one day's wellness summary: steps, calories, stress, Body Battery, intensity minutes, resting HR.

get_daily_summariesA

Get daily wellness summaries for a date range (up to a year). Best for trends across many days.

get_stepsC

Get daily step totals and step goals for a date range.

get_stressC

Get daily stress levels for a date range.

get_heart_rateA

Get one day's heart rate: resting, min, max, 7-day resting average.

Set include_samples=true for the intraday heart rate time series (large).

get_body_batteryB

Get daily Body Battery reports (charged, drained, events) for a date range.

Set include_samples=true for the intraday Body Battery values (large).

get_spo2A

Get one day's blood oxygen (SpO2): average, lowest, sleep average, 7-day average.

Set include_samples=true for individual and hourly readings (large).

get_hydrationB

Get daily hydration intake and goals for a date range.

get_wellness_activitiesC

Get wellness activity summaries (e.g. auto-detected moves) for a date range.

get_sleepB

Get one night's sleep: duration, stages, sleep score, SpO2, respiration, sleep stress.

date is the calendar day the sleep ended on (the morning you woke up).

get_sleep_summariesA

Get nightly sleep summaries for a date range. Best for sleep trends.

get_hrvA

Get one night's heart rate variability (HRV) summary and status.

Set include_samples=true for the individual overnight HRV readings.

get_hrv_rangeB

Get daily HRV summaries for a date range. Best for HRV trends.

get_fitness_ageB

Get the latest Fitness Age as of a date, with the factors that drive it.

get_weightA

Get weight and body composition for a date range: daily latest weights and range average.

Weights are in grams.

get_weight_goalsC

Get the weight goals in effect over a date range.

get_heart_rate_zonesB

Get the user's configured heart rate zones per sport.

get_profile_settingsA

Get profile settings: units, time zone, height, birth date, activity level, etc.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 21 tools

Disambiguation4/5

Most tools target clearly distinct Garmin data domains and actions, such as activities, sleep, HRV, weight, and profile settings. The main ambiguity comes from singular/range pairs like get_daily_summary vs. get_daily_summaries and get_sleep vs. get_sleep_summaries, though the descriptions clarify their intended use.

Naming Consistency4/5

The tool set is overwhelmingly consistent snake_case and mostly follows a get_<resource> pattern, with search_activities as the main verb deviation. Singular/plural naming variants like summary/summaries and range-specific suffixes are readable but slightly inconsistent.

Tool Count4/5

At 21 tools, the surface is somewhat large but reflects the broad Garmin wellness and activity domain. Each metric group is reasonably scoped, though some singular/range pairs could potentially be consolidated.

Completeness4/5

The server covers a wide range of read-only Garmin data: activities, workouts, daily wellness, sleep, HRV, SpO2, hydration, weight, and profile settings. Some secondary areas such as devices, training status, VO2 max, or personal records are absent, but core health and activity workflows are well covered.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues