garmin-mcp
by ctribuna
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GARMIN_TOKENS | No | Fallback when no Redis is configured: the contents of garmin_tokens.json (raw JSON or base64). Refreshed tokens then stay in memory only. You can produce the value with uv run scripts/garmin_login.py --print. | |
| MCP_AUTH_TOKEN | Yes | Secret that protects the MCP endpoint and the token upload endpoint. At least 24 characters. Generate with openssl rand -hex 32. It also derives the token encryption key. | |
| GARMIN_TIMEZONE | No | IANA timezone used to resolve "today". Set this to your own. | Europe/Lisbon |
| KV_REST_API_URL | No | Upstash Redis REST URL. Injected by Vercel when you connect Upstash for Redis. | |
| KV_REST_API_TOKEN | No | Upstash Redis REST token. Injected by Vercel. | |
| GARMIN_ENABLE_WRITE | No | Set to true to expose the tools that create, schedule, unschedule and delete workouts. | false |
| UPSTASH_REDIS_REST_URL | No | Accepted alternative to KV_REST_API_URL for the Upstash Redis REST URL. | |
| UPSTASH_REDIS_REST_TOKEN | No | Accepted alternative to KV_REST_API_TOKEN for the Upstash Redis REST token. |
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
ResponsivenessNo recent community issues