Sports Tracker MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STT_BASE_URL | No | Sports Tracker API base endpoint. | https://api.sports-tracker.com/apiserver/v1 |
| STT_SESSION_KEY | Yes | Your session token (STTAuthorization header). Required to authenticate requests. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_recent_workoutsB | Get recent workouts with formatted distance, duration, pace, and HR. |
| get_social_feedB | Get social feed items from followed athletes or community. |
| get_workout_detailsC | Get detailed workout metrics including ascent, descent, HR zones, gear, and Suunto extensions. |
| get_user_statsA | Get lifetime totals and per-sport breakdown stats for the logged-in user or specified username. |
| get_vo2_max_historyB | Get VO2Max and fitness age history extracted from recent workouts. |
| get_training_summaryB | Get aggregated training volume, distance, time, and calories across sports for the past N days. |
| get_training_load_and_recoveryA | Get current training load, recovery hours, TSS, PTE, EPOC, and recovery status from the latest workout. |
| get_recent_activities_summaryC | Get a breakdown of activity frequency, total time spent, and last performed dates over the past N days. |
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 8 tools
Most tools have clearly distinct purposes: social feed, workout lists, detailed workout metrics, user stats, VO2Max history, and recovery are easy to tell apart. The only mild ambiguity is between get_training_summary and get_recent_activities_summary, since both aggregate data over the past N days, though their metric focus differs.
All tools follow a consistent get_<noun_phrase> snake_case pattern, making the set predictable and easy to navigate. There are no mixed conventions or vague verbs.
Eight tools is well-scoped for a read-only sports tracking analytics server. Each tool represents a meaningful query surface without unnecessary redundancy or overwhelming breadth.
The read-only query surface is quite complete for analytics: recent workouts, detailed workout metrics, summaries, user stats, VO2Max history, recovery, and social feed are all covered. The main gap is the total absence of write operations like logging a workout or updating user data, though that may be acceptable if the server is intended only as a data retrieval layer.