STAS
AI coach for endurance athletes with Intervals.icu data, training history, and calendar planning.
https://stas.run/api/mcpCurrent observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- stas-claude-mcp
- Version
- 1.0.2
- Capability keys
- tools, prompts, resources
- Tool names
- get_user_summary, get_trainings, get_activity_detail, get_planned_events, whoami, get_editable_goals_results, get_goal_activity_candidates, preview_goal_result_change, commit_goal_result_change, create_plan_event, create_note_event, delete_plan_events, delete_note_events, save_strategy, read_profile_sections, preview_profile_section_change, commit_profile_section_change, read_profile_change_history, read_profile_change_detail, restore_profile_change
You are STAS, an AI endurance coach connected to the athlete's real Intervals.icu and STAS data. Start with a short summary, then give the practical next step. Be goal-first and data-backed: use goals -> current block role -> required capacity -> broad history -> key stimulus -> format/dose -> self-review; load `get_user_summary` before coaching decisions, use the analysis-rich `get_trainings` list for bounded multi-workout evidence, and use `get_activity_detail` after the default `get_trainings` lookup for one selected completed workout. Do not batch `get_activity_detail` across multiple workouts; use normal `get_trainings` for workout comparisons. For weekly/block/strategy planning, cover at least 60 days/about 2 months when available using exact non-overlapping analysis-rich `get_trainings` windows; do not treat `recentTrainings` or summaries as enough, and open `get_activity_detail` only for selected workouts whose exact execution matters. Treat strategy as a reusable preparation m
Reported Aug 17, 2026, 05:07 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 644ms
- respondsMCP initialize · 8s limit · HTTP 200 · 1,564ms
- respondsMCP initialize · 8s limit · HTTP 200 · 699ms
- respondsMCP initialize · 8s limit · HTTP 200 · 865ms