suunto-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUUNTO_FTP | No | Athlete profile, needed only for %HRmax / %FTP targets | |
| SUUNTO_OWNER | No | Creator name. Must match the OAuth app name for the Cloud API | |
| SUUNTO_MAX_HR | No | Athlete profile, needed only for %HRmax / %FTP targets | |
| SUUNTO_REST_HR | No | Athlete profile, needed only for %HRmax / %FTP targets | |
| SUUNTOOL_BINARY | No | Path to suuntool, if not on PATH | |
| SUUNTO_CLIENT_ID | No | Enables refresh of the 24h token | |
| SUUNTO_MCP_BACKEND | No | file (default), cloud, or private (reuses a suuntool session) | |
| SUUNTO_ACCESS_TOKEN | No | Static bearer token, for trying the API by hand | |
| SUUNTO_THRESHOLD_HR | No | Athlete profile, needed only for %HRmax / %FTP targets | |
| SUUNTO_CLIENT_SECRET | No | Enables refresh of the 24h token | |
| SUUNTO_MCP_OUTPUT_DIR | No | Where the file backend writes; defaults under ~/.local/share | |
| SUUNTO_SUBSCRIPTION_KEY | No | Ocp-Apim-Subscription-Key, required for cloud backend | |
| SUUNTO_TRAINING_CONTEXT | No | suuntool to enable get_recent_training, off (default) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| preview_workoutA | Compile a structured workout into the SuuntoPlus guide format and return it WITHOUT uploading. Use this first: it surfaces unit conversions, truncated titles and validation errors, so mistakes are caught before anything reaches the watch. |
| list_workoutsB | List structured workouts stored on the configured backend. |
| describe_backendA | Report which backend is active and which operations it supports. Check this before planning a sequence of changes — backends differ in what they can do. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: preview_workout compiles and validates without uploading, list_workouts retrieves stored workouts, and describe_backend reports backend capabilities. There is no ambiguity or overlap between them.
All tool names follow a consistent verb_noun pattern in snake_case: preview_workout, list_workouts, describe_backend. This is predictable and easy to navigate.
With only 3 tools, the server is at the lower end of the ideal range, but each tool earns its place. The count feels slightly thin for a full workout management workflow, yet is appropriate for a focused validation and overview server.
The server lacks core operations such as create, update, delete, or upload for workouts. It only supports previewing and listing, with describe_backend to check capabilities, leaving significant gaps for any actual modification or synchronization workflow.