The read tools and the write tools point at the same record, so the programme responds to sessions you completed rather than sessions that were planned. Resolving exercise names to canonical ids before logging is what keeps a training history trendable instead of turning it into free text.
A hosted fitness coaching server at https://api.pelaris.io/mcp, with its tool set split between reads and writes. It holds your training profile, generates and manages programmes, plans and logs sessions, tracks benchmarks, body composition, goals and injuries, and returns coaching insight and a weekly debrief from what you have actually done.
- Training context, the active programme and recent sessions in one read (get_training_overview, get_active_program, get_session_details)
- A full programme generated from your profile and enrolled, with generation and programme status pollable (complete_intake, generate_program, get_generation_status, get_program_status, manage_program, get_onboarding_status)
- Sessions planned, modified, updated and deleted (create_planned_session, modify_training_session, update_session, delete_session, delete_sessions)
- Workouts logged as done, with exercises, sets and feedback (log_workout, log_completed_session), and exercise names resolved to canonical ids first (resolve_exercise_ids, swap_exercise)
- Benchmarks recorded and read back with history and trends (record_benchmark, get_benchmarks), alongside body composition and measurement trends (get_body_analysis)
- Goals listed and managed against linked benchmarks (list_goals, manage_goals)
- Coaching insight from your own training data, a generated weekly plan and a weekly debrief (get_coach_insight, generate_weekly_plan, get_weekly_debrief)
- Daily check-ins, injuries recorded, profile updates, feedback, and a search over curated training articles (daily_check_in, record_injury, update_profile, send_feedback, search_training_resources)
An MCP client that can add a remote server: point it at https://api.pelaris.io/mcp. It supports OAuth with PKCE and Dynamic Client Registration; Claude's connector setup also wants the client id pelaris-claude under advanced settings.