Sports Tracker MCP Server
This server lets AI assistants query your Sports Tracker account for training data and metrics.
Workouts: Fetch recent workouts (
get_recent_workouts) and detailed analysis of any workout (get_workout_details) β including HR, pace, distance, elevation, HR zones, gear, TSS, PTE, EPOC, and recovery time.Training load & recovery: Get current recovery status, cumulative recovery hours, TSS, PTE, and EPOC from the latest workout (
get_training_load_and_recovery).Summary & stats: Aggregate training volume/distance/time/calories over the past N days (
get_training_summary), lifetime and per-sport totals (get_user_stats), and activity frequency over a period (get_recent_activities_summary).Fitness trends: View VO2Max and fitness age history (
get_vo2_max_history).Social: Retrieve feed items from followed athletes (
get_social_feed).Formatting: Outputs both metric and imperial units, formatted distances/durations/pace, and interactive HTML cards where supported.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Sports Tracker MCP Server What's my current recovery and training load?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Sports Tracker MCP Server (Unofficial)
Ask your AI assistant about your training: workouts, VO2Max trends, training load, recovery, and lifetime stats β answered with interactive cards.
Unofficial Project: This project is an independent, open-source Model Context Protocol (MCP) server. It is not affiliated with, endorsed by, sponsored by, or associated with Sports Tracking Technologies Ltd, Amer Sports, Suunto, or any of their affiliates or subsidiaries. All registered trademarks, product names, and company logos are the property of their respective owners.
Runs locally, always. The server talks to Sports Tracker with a session key taken from your own browser. That key is tied to your account and never leaves your machine β so there is no hosted version of this server, and there cannot be one.
π Quick start
1. Get your session key
Log in to Sports Tracker Web, open DevTools (F12 / Cmd+Option+I) β Network, refresh the page, click any request to api.sports-tracker.com, and copy the value of the STTAuthorization request header.
Treat this key like a password β it grants full access to your Sports Tracker account. Never paste it into an issue, a gist, or a shared config. It alsoexpires: when tools start failing with an authentication error, repeat this step to get a fresh one.
2. Add the server
Claude Code β one command:
claude mcp add sports-tracker -e STT_SESSION_KEY=your_session_key_here \
-- uvx --from git+https://github.com/wilkar/sports-tracker-mcp sport-tracker-mcpClaude Desktop β add to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json, Windows: %APPDATA%\Claude\claude_desktop_config.json):
{
"mcpServers": {
"sports-tracker": {
"command": "uvx",
"args": ["--from", "/path/to/the/repo", "sport-tracker-mcp"],
"env": {
"STT_SESSION_KEY": "your_session_key_here"
}
}
}
}Cursor / Antigravity β add the same JSON block to your MCP settings (mcp_config.json).
Nothing to clone and no virtualenv to manage: uv fetches and runs the server on demand. If your client reports uvx: command not found, use the absolute path from which uvx (e.g. /opt/homebrew/bin/uvx).
3. Ask it something
"How far did I run in the last 7 days?"
That's it. If you get an answer, you're done.
Related MCP server: GC-MCP
π οΈ Available MCP Tools
Tool | UI Card | Description | Parameters |
| β | Fetch recent workouts with interactive sport and limit filters, clickable workout rows, and metrics. |
|
| β | In-depth workout analysis with interactive time series charts (HR, altitude, speed), HR zones, ascent/descent, and Suunto extensions. |
|
| β | Recovery gauge, cumulative recovery hours, TSS, PTE, and EPOC metrics. | None |
| β | Aggregated volume, distance, time, and calories across sports for the past N days. |
|
| β | Aerobic capacity (VO2Max) trendline and fitness age progression extracted from workouts. |
|
| β | Lifetime aggregate statistics and per-sport totals (distance, duration, calories, count). |
|
| β | Breakdown of sport frequency, total duration, and last performed dates over the past N days with interval selector. |
|
| β (data-only) | Retrieve feed items from followed athletes or community members. |
|
Cards render as interactive HTML in hosts that support MCP Apps (io.modelcontextprotocol/ui); every tool also returns plain structured data, so clients without UI support lose nothing.
More things to ask
"How much running and cycling have I logged over the past 14 days? Break it down by distance, time, and pace."
"Give me a detailed breakdown of my latest workout, including heart rate zones, elevation gain, and Suunto metrics in imperial units."
"What is my current recovery time, TSS, and EPOC? Am I ready for a tempo run today?"
"Plot my VO2Max and fitness age progression over my last 20 workouts."
βοΈ Configuration reference
Variable | Required | Default | Description |
| Yes | β | Your session token (the |
| No |
| Sports Tracker API base endpoint. |
Pass both through your MCP client's env block (as in Quick start); the server reads them from the process environment at startup.
On STT_BASE_URL: your session token is sent as a header to whatever host this names. Leave it at the default unless you are deliberately pointing at a trusted local debugging proxy.
π§βπ» Development
git clone https://github.com/wilkar/sports-tracker-mcp.git
cd sports-tracker-mcp
uv syncRun the server from the clone:
STT_SESSION_KEY="your_key" uv run sport-tracker-mcp
# or keep it in a local .env (cp .env.example .env):
uv run --env-file .env sport-tracker-mcpPoint an MCP client at your working copy by swapping the --from target for an absolute path:
claude mcp add sports-tracker-dev -e STT_SESSION_KEY=your_key \
-- uvx --from /absolute/path/to/sports-tracker-mcp sport-tracker-mcpTests, types and formatting:
uv run pytest
uv run mypy .
uv run isort --check .
uv run black --check .Inspect the tool schemas:
uv run fastmcp list src/sport_tracker_mcp/server.py
uv run fastmcp dev inspector src/sport_tracker_mcp/server.pyProject structure
src/sport_tracker_mcp/
βββ client.py # Async HTTP client with TTL cache & error handling
βββ config.py # Environment variable resolution
βββ constants.py # Activity ID mappings
βββ formatting.py # Unit conversions (metric/imperial), pace, duration
βββ models.py # Pydantic schemas for workouts, stats, load & recovery
βββ server.py # FastMCP server, tool registration & UI cards
βββ tools.py # Tool implementations
βββ ui.py # HTML rendering for tool-result cardsπΊοΈ Roadmap
get_routes: List saved and recorded GPS routes with distances, speeds, and activity types.get_route_details: GPS track waypoints, elevation profiles, and polyline coordinates for a route.export_workout_gpx: Download standardized GPX XML track files for activities.get_user_following: Retrieve followers and followed athlete profiles.
π License
This project is licensed under the MIT License.
Available Tools
8 toolsget_recent_activities_summaryGet Recent Activities SummaryC
Get a breakdown of activity frequency, total time spent, and last performed dates over the past N days.
Inputs: days, now_ts. Returns: days, activities, total_sessions
get_recent_workoutsGet Recent WorkoutsB
Get recent workouts with formatted distance, duration, pace, and HR.
Inputs: limit, imperial. Returns: result
get_social_feedGet Social FeedB
Get social feed items from followed athletes or community.
Inputs: limit, imperial. Returns: result
get_training_load_and_recoveryGet Training Load And RecoveryA
Get current training load, recovery hours, TSS, PTE, EPOC, and recovery status from the latest workout.
Inputs: no named parameters. Returns: peak_epoc, impact_tag, latest_sport, recovery_status, +6 more
get_training_summaryGet Training SummaryB
Get aggregated training volume, distance, time, and calories across sports for the past N days.
Inputs: days, now_ts, imperial. Returns: days, sports, workouts_count, total_distance_km, +3 more
get_user_statsGet User StatsA
Get lifetime totals and per-sport breakdown stats for the logged-in user or specified username.
Inputs: imperial, username. Returns: sports, total_days, total_workouts, total_distance_km, +3 more
get_vo2_max_historyGet Vo2 Max HistoryB
Get VO2Max and fitness age history extracted from recent workouts.
Inputs: limit. Returns: records, latest_vo2_max, average_vo2_max, latest_fitness_age
get_workout_detailsGet Workout DetailsC
Get detailed workout metrics including ascent, descent, HR zones, gear, and Suunto extensions.
Inputs: workout_key (required), imperial. Returns: gear, sport, avg_hr, max_hr, +20 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
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.
Maintenance
Related MCP Connectors
Your Garmin, Oura, WHOOP, Hevy and 35 more fitness apps, queryable from your own AI.
Ask your AI about your fitness: activities and data from Garmin, COROS, Strava, GPX and more
Garmin watch data for AI assistants: activities, sleep, HRV, recovery. Never writes to Garmin.
Your endurance training data in your AI assistant: activities, recovery, plan, workout edits.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables users to interact with their Strava data through natural language to analyze workouts, track fitness progress, and explore routes. It supports retrieving detailed activity stats, heart rate data, and segment insights directly within AI assistants.26MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to access and query Garmin Connect health and fitness data, including sleep, HRV, training load, and activities, with an optional coaching plugin for personalized training plans.4-
- AlicenseAqualityDmaintenanceEnables AI assistants to directly access and analyze Strava activity data, including runs, rides, and swims, through natural language queries.417 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query live Garmin Connect health and fitness data, including daily metrics, activities, sleep analysis, and trends via natural language.MIT