Skip to content
Body Lab logo

Body Lab

Reads your training load and morning recovery metrics, then prescribes one daily session with heart rate, power or lift targets.
At a glanceswept Oct 25, 2026

not read yet

Use

For
Endurance athletes and lifters training for the long run, with or without a race date.
Runs as
Mobile app
Used for
  • get daily session targets from training load and recovery
  • check whether recovery supports a hard session
  • review how a lift has progressed over several months
Worth knowingcomputed from what we read · each with its source
  • Has an MCP server (1 in the registry)public registry →
How a program reaches itfound, not claimed · read Oct 26, 2026
  • MCP serverlol.bodylab/body-labverified in the MCP registry
  • Stateanswers, requires sign-inchecked 2026-10-26
  • Address to connectbodylab.lol/mcp

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Most used in Analyticsby use, among tools still maintained — this tool shares no tags yet

Figure and bar: visits/mo, estimate · year: online since

Compare Body Lab with

Pick up to two.

All 10 alternatives to Body Lab →

All Analytics tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use Body Lab for?

Sign in to leave a note
Questions this page answers
  • What is Body Lab?

    Reads your training load and morning recovery metrics, then prescribes one daily session with heart rate, power or lift targets. It is listed in the Atlas under Analytics.

  • Who is Body Lab for?

    Endurance athletes and lifters training for the long run, with or without a race date.

  • Do people use Body Lab?

    Little sign of use.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk