pushinglimits-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pl_statusA | Login check against Pushing Limits Club. Returns logged_in, user_name, checked_at. |
| pl_get_pmcA | Performance management chart (CTL/ATL/TSB/TSS per day). Dates YYYY-MM-DD, Europe/Berlin. |
| pl_get_workoutsA | Planned and completed workouts between two dates (YYYY-MM-DD, inclusive, Europe/Berlin). |
| pl_get_weekB | Monday-Sunday week containing the date: TSS sums plus workouts with status erledigt/offen/ausgelassen. |
| pl_get_thresholdsB | Current thresholds: ftp, threshold_run, threshold_swim, weight, max_hr, resting_hr, updated_at. |
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 5 tools
pl_get_workouts and pl_get_week both expose workout data, with pl_get_week adding TSS aggregation, so an agent may need to read descriptions carefully. The other three tools are clearly distinct.
All tools share the pl_ prefix and most use pl_get_<resource>; pl_status breaks the pattern slightly but is still predictable.
Five tools is well-scoped for a read-only training-data server; each endpoint covers a distinct data area without bloat.
Core athlete data is covered: auth status, performance management chart, workouts, weekly summaries, and thresholds. Missing write operations or single-workout detail are not significant if the server is intentionally read-only, but the overlap between workouts and week leaves a small gap for more granular queries.