Garmin Connect MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EMAIL_PORT | No | IMAP port for email-based MFA | 993 |
| EMAIL_USER | No | Email address for automated MFA retrieval (e.g. Gmail) | |
| NTFY_TOKEN | No | Authentication token for the ntfy server | |
| NTFY_TOPIC | No | ntfy topic for notifications | |
| NTFY_SERVER | No | ntfy server for notifications | https://ntfy.sh |
| EMAIL_SERVER | No | IMAP server for email-based MFA | imap.gmail.com |
| GARMINTOKENS | No | Directory path for storing Garmin session tokens | ~/.garminconnect |
| GARMIN_EMAIL | Yes | Garmin Connect account email address | |
| EMAIL_PASSWORD | No | App password for email account (if not using OAuth2) | |
| GARMIN_MFA_CODE | No | Manual MFA code entry for 2FA authentication | |
| GARMIN_PASSWORD | Yes | Garmin Connect account password | |
| GMAIL_TOKEN_FILE | No | Path to the file where Gmail OAuth2 tokens are stored | |
| GARMIN_MFA_WEBHOOK | No | Webhook URL for automated MFA retrieval | |
| GARMINTOKENS_BASE64 | No | Directory path for storing base64-encoded Garmin session tokens | ~/.garminconnect_base64 |
| GOOGLE_CLIENT_SECRET_FILE | No | Path to the client_secret.json file for Google OAuth2 authentication |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessSyncing