Spec Driven Development
de formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Se ejecuta en tu computadora★ 440MITActualizado hace 14 meses
Instalar
Body Lab
Resumen
Descripción del creador (original en inglés)
Body Lab training: today's prescribed session and why, load, recovery, activities and strength.
Los tres pilares de PopNx MCP
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
- Opinión de usuariosiAún no hay reseñasLas reseñas se abrirán junto con las cuentas en una etapa posterior
- Nuestras revisiones básicasi1 de 1 superadasRevisado con información pública; el código aún no se ha escaneado
- UsoiAún sin medir★ –
Qué puedes hacer con él
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
- Conexión: Se ejecuta en la nube
- Transporte: Streamable HTTP
- Categoría: Otros
Instalación
Elige la app de IA que usas y copia la configuración.
Antes de instalar
- Revisiones básicas: 1 de 1 superadas
- Se ejecuta en el servidor del creador: lo que le pidas pasa por su servidor.
- El registro no indica ninguna clave que completar.
Necesitas
- Se ejecuta en la nubeNo hay nada que instalar; se conecta por internet
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Funciona en Claude para web, escritorio y móvil:
- Abre Settings → Connectors
- Presiona Add custom connector
- Pega la dirección de abajo y presiona Add
- Si te pide iniciar sesión, inicia sesión en el servicio del creador
https://bodylab.lol/mcpEjecuta esto en tu terminal
claude mcp add --transport http body-lab https://bodylab.lol/mcpO copia la configuración tú
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"body-lab": {
"url": "https://bodylab.lol/mcp"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
O copia la configuración tú
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"body-lab": {
"type": "http",
"url": "https://bodylab.lol/mcp"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
ChatGPT solo se conecta a servidores en internet:
- Abre ChatGPT en la web → Settings → Connectors (Apps)
- Presiona Create o Add (en algunos planes primero hay que activar Developer mode en Advanced)
- Pega la dirección de abajo, ponle un nombre y guarda
- Si te pide iniciar sesión, inicia sesión en el servicio del creador
https://bodylab.lol/mcpLos nombres de los menús pueden variar un poco según el plan y con el tiempo.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Qué puede hacer
Todavía no hemos leído la lista de herramientas de este servidor; revisamos los endpoints por turnos.
Revisiones básicasi
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 8 nov 2026
- ✓ Superada
El creador coincide con el repo
El nombre en el registro se verificó con el dominio bodylab.lol (el registro comprueba quién es dueño del dominio)
- … Aún sin revisar
Sigue en mantenimiento
Todavía no hemos leído este repo en GitHub
- … Aún sin revisar
Tiene licencia
Todavía no hemos leído este repo en GitHub
- … Aún sin revisar
El endpoint responde
Aún sin revisar; revisamos los endpoints por turnos
- … Aún sin revisar
Inicio de sesión con OAuth
Aún sin revisar; revisamos los endpoints por turnos
- … Aún sin revisar
Sin instrucciones ocultas en las descripciones de herramientas
Aún sin revisar; leemos la lista de herramientas cuando revisamos el endpoint
Comparado con otros en Otrosi
- Más estrellas que el 0% de los otros 18386 servidores de esta categoría
- Publicado en el registro más recientemente que el 45% de los otros 18386 servidores de esta categoría
- Revisiones básicas iguales o mejores que el 100% de los otros 18386 servidores de esta categoría
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Preguntas frecuentes
¿Es seguro Body Lab?
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
¿Qué claves o códigos necesita?
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
¿Se ejecuta en mi computadora o en la nube?
Se ejecuta en la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.
¿Sigue en mantenimiento?
El repo de GitHub cambió por última vez –, y la última versión (1.0.0) llegó al registro hace 2 meses.
¿Qué apps pueden usarlo?
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.
¿Qué puedo usar en su lugar?
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Tethered Trust
Alternativas
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Remote Desktop Commander
de desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Se ejecuta en la nube★ 211Actualizado anteayer
Instalar
Tethered Trust
de tetheredtrust.com
Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.
Se ejecuta en la nubeActualizado hoy
Instalar
README del creador
Abrir el README
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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-lol
VS 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 pub
Solo se muestra el principio; lee el resto en el repo