Skip to main content
Glama
rmc8

Garmin Connect MCP Server

by rmc8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GARMINTOKENSNoOptional path to token cache directory (defaults to ~/.garminconnect)
GARMIN_EMAILYesYour Garmin Connect login email
GARMIN_PASSWORDYesYour Garmin Connect login password

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
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_steps_dataC

Get detailed steps data for a specific date.

Args:
    cdate: Target date in YYYY-MM-DD format.
get_heart_ratesB

Get heart rate readings for a specific date.

Args:
    cdate: Target date in YYYY-MM-DD format.
get_daily_stepsC

Get summarized daily steps over a specified period.

Args:
    start: Start date in YYYY-MM-DD format.
    end: End date in YYYY-MM-DD format.
get_body_batteryB

Get Body Battery data for a specified period.

Args:
    start: Start date in YYYY-MM-DD format.
    end: Optional end date in YYYY-MM-DD format.
get_hydration_dataA

Get hydration intake data for a specific date.

Args:
    cdate: Target date in YYYY-MM-DD format.
get_last_activityB

Get information about the most recent logged activity.

get_sleep_dataB

Get detailed sleep analysis and scoring for a specific date.

Args:
    cdate: Target date in YYYY-MM-DD format.
get_stress_dataC

Get stress level details for a specific date.

Args:
    cdate: Target date in YYYY-MM-DD format.
get_all_day_stressB

Get comprehensive all-day stress readings for a specific date.

Args:
    cdate: Target date in YYYY-MM-DD format.
get_user_summaryB

Get the user's daily activity summary (steps, calories, heart rate ranges, etc.).

Args:
    cdate: Target date in YYYY-MM-DD format.
get_respiration_dataA

Get daily respiration rate readings (breaths per minute).

Args:
    cdate: Target date in YYYY-MM-DD format.
get_spo2_dataC

Get daily SpO2 (blood oxygen saturation) measurements.

Args:
    cdate: Target date in YYYY-MM-DD format.
get_body_compositionB

Get body composition data for a date range.

Includes weight, body fat, muscle mass, and hydration.

Args:
    startdate: Start date in YYYY-MM-DD format.
    enddate: Optional end date in YYYY-MM-DD format.
        Defaults to startdate if not provided.
get_activitiesB

Get a list of logged fitness activities with pagination.

Args:
    start: Offset index to start retrieving activities. Defaults to 0.
    limit: Maximum number of activities to return. Defaults to 20.
get_devicesA

Get a list of all registered Garmin devices connected to the account.

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

B3.4/5.0

Scored across 15 tools

Disambiguation4/5

Most tools target distinct health metrics, but get_daily_steps vs get_steps_data and get_stress_data vs get_all_day_stress could confuse an agent due to overlapping purposes.

Naming Consistency5/5

All tools use snake_case with a consistent 'get_<resource>' pattern. Minor deviations like 'get_all_day_stress' vs 'get_stress_data' are inconsequential.

Tool Count4/5

15 tools is slightly above the typical sweet spot but still reasonable for covering diverse health metrics without feeling overly burdensome.

Completeness3/5

The tool set covers many health metrics but lacks write operations (e.g., logging activities) and misses common Garmin data like workouts or courses, leaving notable gaps.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources