garmin-mcp
by knahsirV
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Server port (default: 8000; Cloud Run injects 8080) | 8000 |
| LOG_LEVEL | No | DEBUG, INFO (default), WARNING, or ERROR | INFO |
| LOG_FORMAT | No | json or text. Defaults to json on Cloud Run (detected via K_SERVICE), text elsewhere. | |
| GARMIN_EMAIL | No | Your Garmin Connect email | |
| READYZ_TOKEN | No | Required. Bearer token guarding /readyz, checked independently of OAuth so it still answers when the OAuth layer itself is broken. | |
| GARMIN_PASSWORD | No | Optional. Only used to re-authenticate if the stored tokens expire. | |
| PUBLIC_BASE_URL | No | Required. The service's externally reachable URL, e.g. https://garmlink-moz6szqd6q-uc.a.run.app. OAuth callback URLs (/auth/callback) are derived from it. | |
| GITHUB_CLIENT_ID | No | Required (unless ALLOW_UNAUTHENTICATED=1). Client ID of the GitHub OAuth App backing the claude.ai connector. | |
| GARMIN_TOKENS_JSON | No | Base64-encoded token file (from garmlink-auth). A seed, not the live credential: Garmin rotates the refresh token, and rotations are persisted to Firestore, which then takes precedence. Re-seed only to bootstrap a new deployment or recover a stored blob that has gone bad. | |
| GITHUB_ALLOWED_USERS | No | Required. Comma-separated GitHub logins allowed to use the server — the only access control once OAuth is on, so it fails closed: a blank value or a list naming nobody (e.g. ,,) both abort startup. | |
| GITHUB_CLIENT_SECRET | No | Required. That app's client secret. | |
| ALLOW_UNAUTHENTICATED | No | Set to 1 to run with no authentication, skipping the five variables above. Localhost development only — never on a public address. |
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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/knahsirV/garmlink'
If you have feedback or need assistance with the MCP directory API, please join our Discord server