Body Lab
Body Lab training: today's prescribed session and why, load, recovery, activities and strength.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport http body-lab 'https://bodylab.lol/mcp'{
"mcpServers": {
"body-lab": {
"type": "http",
"url": "https://bodylab.lol/mcp"
}
}
}Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
Body Lab MCP server
Connect Claude, ChatGPT, or any assistant that speaks the Model Context Protocol to your Body Lab training. Ask what to do today and why, how last week went, whether you're recovered, or what your squat has been doing, and the answers come from your own data and Body Lab's engine.
https://bodylab.lol/mcpThis repository is the public home of the server: how to connect, the tool reference, the MCP Registry entry, and a Claude Code plugin. The server itself runs at the address above. It's hosted, so there's nothing to install or run.
Connect
You need a Body Lab account. The first time an assistant connects, it sends you to Body Lab to sign in and approve it.
Body Lab isn't listed in assistants' app directories yet, so you add it by its address.
Claude (web, desktop, mobile):
- On claude.ai or in Claude Desktop, open Customize → Connectors.
- Press +, choose Add custom connector, paste
https://bodylab.lol/mcpand press Add. - Press Connect, then sign in to Body Lab and allow Claude.
- In a chat, turn Body Lab on from + → Connectors. It's then available in the Claude mobile app too.
On a Team or Enterprise plan, an organization owner adds it first (Organization settings → Connectors). The free plan allows one custom connector. See Anthropic's custom connector guide.
ChatGPT (web; Plus, Pro, Business, Enterprise or Education):
- Open Settings → Security and login and turn on Developer mode.
- Open Plugins, press +, and create an app with
https://bodylab.lol/mcp, using OAuth. - Sign in to Body Lab and allow ChatGPT.
- In a chat, choose Body Lab from Developer mode in the message box.
See OpenAI's developer mode guide.
Claude Code:
claude mcp add --transport http body-lab https://bodylab.lol/mcpThen run /mcp inside Claude Code and choose Body Lab to sign in. Or install
the plugin, which adds the server and skills for using it well:
/plugin marketplace add bodylab-lol/mcp
/plugin install body-lab@bodylab-lolVS Code, Cursor and other clients: add a remote (Streamable HTTP) MCP
server with the URL https://bodylab.lol/mcp. For clients configured with
JSON:
{
"mcpServers": {
"body-lab": { "type": "http", "url": "https://bodylab.lol/mcp" }
}
}What it can do
An assistant can see your training. With your permission it can also tell Body Lab about today, put sessions you've arranged and strength routines you've chosen on your calendar and take them off again, add races and goals at priority B or C, see your lab results and add new ones, for example from a PDF or photo of a lab report, do the same with body composition scans such as DEXA, and read or record your daily updates: how you felt and what happened the night before, and the patterns Body Lab finds in them. It can't change your training history, delete anything, or make an event the A race your plan is built around — that's yours to do in Body Lab.
| Tool | For |
|---|---|
get_today | Today's (and tomorrow's) prescribed session, with heart-rate and power targets and, on runs once your critical speed is known, a pace; the reasons behind it, alternatives, readiness, and what Body Lab is calling out today: a pattern in sleep or recovery readings, a new best, a note about the plan, or missing data |
set_today_context | Tells Body Lab how long you have today, what equipment is to hand and which sports are out, and returns the re-prescribed session. Today only. Needs today:write |
get_week | The next seven days as the engine projects them: detailed through tomorrow, summarised after, and shifting each morning |
schedule_session | Puts a session you've arranged — a club ride, a run with a friend — on your calendar, one entry per occurrence, so Body Lab plans the week around it. The same session twice is stored once. Needs schedule:write |
schedule_strength_routine | Puts strength routines you've chosen — a program's days, a session a coach wrote — on your calendar: named exercises from Body Lab's catalogue with sets, reps, rest and a weight, a share of your max or reps in reserve. Leave a weight out and Body Lab fills it on the day from your own lifting; a weight you state is kept as given. A routine on its own is that day's session, and you run and log it in Body Lab's strength runner. The same routine twice on a day is stored once; an exercise Body Lab doesn't have is refused with suggestions. Needs schedule:write |
list_strength_routines | The strength routines on your calendar over up to 60 days, each with its exercises, sets, reps and weights as written |
withdraw_session | Takes a session you arranged, or a strength routine, off the calendar again. It's kept and marked withdrawn, never deleted; Body Lab's own sessions can't be touched. Needs schedule:write |
schedule_event | Adds a race or goal at priority B or C. It refuses to add an A event, and can't edit one: both are yours to do in Body Lab. Needs events:write |
remove_event | Takes off a race it added itself, after reading it back to you. It can't remove one you entered, and can't remove an A race even if it added it — promoting a race to A is your decision, so taking it back is too. Removing is permanent. Needs events:write |
get_weekly_review | How a complete week went against what was prescribed, load against the band, the strength floor, and whether training so far supports an upcoming event |
get_training_status | Fitness, fatigue, form, workload ratio, strain, intensity balance, week by week, and critical speed for runners: the pace at the edge of sustainable hard running, from your own recent hard runs, with its ± |
list_activities, get_activity | Your activities, and one in detail with load, zones, power and speed bests and plan adherence |
get_recovery | Morning resting HR, HRV, sleep and energy scores |
get_daily_steps | Steps counted each day, with the source each count came from and the mean of the last seven complete days. Each day is one source's count, never several devices added together; today's is marked as so far |
get_measurements | Any of your measurement series over a range, several at once: morning readings, steps, weight, VO2max, FTP and threshold values, and every blood pressure reading grouped into sittings. Up to two years per series, within a budget per answer |
get_strength | The strength session Body Lab would prescribe now, estimated maxes, recent sessions |
get_profile | Heart-rate anchors, FTP, weight, most recent blood pressure, strength equipment, test results, power curve |
find_exercises | The strength exercise catalogue, searched by name or by the other names an exercise goes by ("RDL", "skull crusher"), by movement pattern or by muscle, with the equipment each one needs |
suggest_routes | Routes you've done before that fit today's session |
get_patterns | What your daily updates add up to: for each thing you can note about a night (drinks, late caffeine, a stressful day, a late dinner, a warm bath, a hot bedroom), how the next morning compared with ordinary nights, with the previous day's training accounted for, and whether there's enough to say yet. Also a running 14-night experiment and the ones on offer. Comparisons of your own nights, never a claim about cause. Needs checkins:read |
record_daily_update | Records what you tell the assistant about this morning and last night: how you feel, what happened, or that it was an ordinary night. Today only; keeps anything you already noted in the app, and can't record an illness, an injury or a period start. It never changes today's session. Needs checkins:write |
get_lab_results | Your blood test results: each marker over time against the lab's range and guideline limits, and whether a change is beyond normal variation. Needs labs:read |
record_lab_results | Adds a blood draw and its results as the report prints them, after the assistant checks the values with you. It can't edit or delete results. Needs labs:write |
get_body_composition | Your body composition scans: total and regional fat, lean and bone mass, body fat percent, visceral fat, and whole-body bone density, as your report gave them. Needs body:read |
record_body_composition | Adds one scan as the report prints it, after the assistant reads every value back to you. It can't edit or delete scans. Needs body:write |
Prompts: What should I do today? (todays-session) and Review my week
(weekly-review).
Full reference, with every argument: TOOLS.md. Machine-readable, with input and output schemas: tools.json.
Your data and permissions
Every connection can see your training (training:read). Daily updates, lab
results and body composition scans are separate from it and from each other,
and each is off unless you turn it on when you approve an assistant:
| Scope | Lets the assistant |
|---|---|
training:read | See your training, recovery, activities and profile |
today:write | Tell Body Lab about today: your time, equipment and sports you can't do. It can't change your training history |
schedule:write | Put sessions and strength routines on your calendar — a routine's exercises, sets, reps and weights included — and take them off again. It can't change your training history |
events:write | Add and remove races and goals you give it. It can't make one an A race — that rebuilds months of your plan, and you do that in Body Lab |
checkins:read | See your daily updates: how you felt, what you noted about yesterday, including drinks and your cycle, and the patterns Body Lab found |
checkins:write | Record a daily update you give it. It can't change your training history |
labs:read | See your lab results |
labs:write | Add lab results you give it. It can't change or delete them |
body:read | See your body composition scans |
body:write | Add body composition scans you give it. It can't change or delete them |
schedule:write covers sessions you've arranged and strength routines you've
chosen, and nothing Body Lab prescribed: a withdrawn session stays on record,
marked withdrawn. A routine names exercises from Body Lab's catalogue only, so
an assistant can't add an exercise of its own, and any weight it states is
shown to you in the strength runner before you lift, with a note when it's
well above what you've logged. events:write adds races and goals at B or C
only; making one your A race, editing it, or removing it stays in Body Lab, so
an assistant can't restructure months of your plan or delete a race by
mistake. Every session or event an assistant adds is recorded as that
assistant's, and each assistant is held to a rolling limit on how much it can
schedule.
An assistant you already allowed to schedule sessions can put strength routines on your calendar too, without reconnecting: they come under the same permission. Otherwise, an assistant you connected before these existed doesn't get them automatically, and one you allowed for lab results doesn't get body composition. To allow any of them, connect it again (in Claude, disconnect and reconnect Body Lab) and tick those boxes when Body Lab asks. To correct or delete a lab result, to remove a scan, or to change or remove a race, use Body Lab on the web.
Body composition scans, including bone density, are measurements you recorded. Body Lab shows them back to you and nothing more: they are not a diagnosis, a whole-body scan is not a diagnostic bone density test, and nothing Body Lab prescribes reads them.
- When you approve an assistant, Body Lab shows who published it (or that it's unverified), where it will send you back to, and what it can do.
- What an assistant reads goes to that assistant's provider, and they handle it under their own terms.
- See and disconnect assistants any time in Body Lab under Settings → AI assistants. Disconnecting works immediately.
- Body Lab's recommendations are training guidance, not medical advice.
- Full details: Privacy Policy and Terms of Service.
For client developers
The server follows the MCP authorization spec (2026-07-28):
- Protected resource metadata:
https://bodylab.lol/.well-known/oauth-protected-resource/mcp - Authorization server metadata:
https://bodylab.lol/.well-known/oauth-authorization-server - Client registration: Client ID Metadata Documents (preferred), or dynamic
client registration at
/oauth/register. - Flow: authorization code with PKCE (S256 only). Include the
resourceparameter (https://bodylab.lol/mcp). Authorization responses carryiss. - Clients: public only (
token_endpoint_auth_method: none). Refresh tokens rotate. Revoke at/oauth/revoke. - Scopes:
training:read(every connection), plus the optionaltoday:write,schedule:write,events:write,checkins:read,checkins:write,labs:read,labs:write,body:readandbody:write. A 401 names all ten; the athlete chooses the optional ones on the consent page, and the token response'sscopesays what was granted.tools/listshows only the tools the grant covers. Atools/callfor a tool it doesn't cover gets403withWWW-Authenticate: Bearer error="insufficient_scope"and ascopenaming the grant's scopes plus the one needed, for step-up authorization. - Transport: Streamable HTTP, stateless, on protocol 2026-07-28 and the 2025
initializehandshake.
Registry name: lol.bodylab/body-lab.
Issues
Bugs, questions and tool requests: open an issue.
Questions fréquentes
Qu'est-ce que Body Lab ?
Body Lab training: today's prescribed session and why, load, recovery, activities and strength.
Comment installer Body Lab ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http body-lab 'https://bodylab.lol/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour Body Lab ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
Body Lab est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient Body Lab ?
Il est publié par bodylab-lol. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.