Pelaris MCP Server

Most developer tooling work still happens through a UI a human drives. Pelaris MCP server moves it into the conversation instead. AI fitness coaching through any MCP-compatible AI assistant. Plan training, log workouts, track benchmarks, manage goals, and get coaching insights — all through natural conversation.

The tools it exposes

The server publishes 14 tools. What each one is for:

• get_training_overview — View your training context, active programs, and recent sessions
• get_active_program — View current program with phase, weekly structure, and session details
• get_session_details — View a specific session's exercises, sets, targets, and feedback
• resolve_exercise_ids — Resolve exercise names to canonical exercise IDs before planning or logging
• get_benchmarks — View benchmark values, progress history, and trends
• get_body_analysis — View body composition data and measurement trends
• search_training_resources — Search curated training articles and resources
• get_coach_insight — Get data-driven coaching insights based on your training
• get_onboarding_status — Check profile setup completion status
• get_weekly_debrief — View weekly training summary and coaching focus
• get_generation_status — Check the status of an in-progress program-generation job
• get_program_status — Check the status and progress of your training programs

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Pelaris's toolset — get_training_overview, get_active_program, get_session_details and 11 more — is a fair guide to whether it matches your workflow. It is maintained by thedonk; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Pelaris.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.