Garmin Connect MCP

.env.example•339 B

# Garmin Connect credentials (optional - used as fallback when no saved token exists)
GARMIN_EMAIL=your_email@example.com
GARMIN_PASSWORD=your_password

# Token storage directory (optional - default: ~/.garminconnect)
# GARMIN_TOKEN_DIR=~/.garminconnect

# Base64-encoded token data (optional - for Docker/CI environments)
# GARMINTOKENS=

Loading blob content...

Latest Blog Posts

Redis vs ioredis vs valkey-glide
By punkpeye on January 26, 2026.
benchmark
Redis
valkey
Quickstart: Publish an MCP Server to the MCP Registry
By punkpeye on January 24, 2026.
mcp
official reference mirror
Official MCP Registry Server.json Requirements
By punkpeye on January 24, 2026.
mcp
official reference mirror

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/leewnsdud/garmin-connect-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

.env.example•339 B

# Garmin Connect credentials (optional - used as fallback when no saved token exists)
GARMIN_EMAIL=your_email@example.com
GARMIN_PASSWORD=your_password

# Token storage directory (optional - default: ~/.garminconnect)
# GARMIN_TOKEN_DIR=~/.garminconnect

# Base64-encoded token data (optional - for Docker/CI environments)
# GARMINTOKENS=