Garmin MCP Gateway
by VelkyVenik
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Listen port. | 8080 |
| DB_PATH | No | Override the DB path (default: $DATA_DIR/gateway.db). | |
| DATA_DIR | No | Where the SQLite DB and per-user token dirs live. | /data |
| PUBLIC_URL | Yes | Public URL used in OAuth metadata + redirects. | http://localhost:8080 |
| MAX_WORKERS | No | Max concurrent per-user workers. | 10 |
| OPERATOR_NAME | No | Shown on the landing page. | |
| GARMIN_MCP_CMD | No | Command to spawn the worker. Use a `uvx …` invocation when `garmin-mcp` isn't on PATH. | garmin-mcp |
| GARMIN_MCP_REF | No | Docker build arg: commit/ref of `garmin_mcp` to install. Pin to a SHA. | main |
| GATEWAY_SECRET | Yes | ≥32-char key for token encryption. Generate with `openssl rand -base64 48`. | |
| OPERATOR_EMAIL | No | Shown on the landing page. | |
| WORKER_IDLE_TTL | No | Seconds before an idle worker is reaped. | 900 |
| WORKER_PORT_END | No | End of port range for per-user workers. | 9099 |
| GATEWAY_LOG_FILE | No | If set, tees structured + stdlib logs to this file. | |
| GATEWAY_LOG_LEVEL | No | `debug`|`info`|`warning`|`error`|`critical`. `debug` is verbose. | info |
| WORKER_PORT_START | No | Start of port range for per-user workers. | 9000 |
| WORKER_STARTUP_TIMEOUT | No | Seconds to wait for a worker to become healthy. | 20 |
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
- 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/VelkyVenik/garmin-mcp-gateway'
If you have feedback or need assistance with the MCP directory API, please join our Discord server