mcpbeat

Fitfly Engine MCP Server

io.github.dropflyai/fitfly-engine
answering

Fitfly Engine is answering right now. Last checked 14 min ago. It exposes 10 tools.

Deterministic fitness coaching engine: adaptive programs, progression math, readiness autoregulation

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
10
Tools
read from the server
351 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add fitfly-engine --transport http https://workout-engine-production-5dd7.up.railway.app/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "fitfly-engine": {
      "url": "https://workout-engine-production-5dd7.up.railway.app/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.fitfly-engine]
url = "https://workout-engine-production-5dd7.up.railway.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "fitfly-engine": {
      "url": "https://workout-engine-production-5dd7.up.railway.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "fitfly-engine": {
      "url": "https://workout-engine-production-5dd7.up.railway.app/mcp"
    }
  }
}

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

swap
list_swap_options
Valid alternatives for an exercise — same muscle group, filtered to the athlete's equipment/level/injuries. Use before swap_exercise.
swap_exercise
Replace an exercise with a valid same-area alternative. scope 'today' = just this session; scope 'program' = going forward. The new lift starts fresh (day-one calibration).
changelog
changelog
The 'what changed & why' feed — the engine's coaching decisions (volume bumps, deloads, swaps) in Coach Fly's voice. Use to explain to the athlete why their plan evolved.
log
log_workout
Record what the athlete actually lifted. The engine runs progression (double-progression, e1RM), detects PRs, and returns per-exercise outcomes (established/progressed/held/deloaded) with next-time targets. Weights are in kg.
meal
meal_plan
A day of meals hitting the athlete's targets, USDA truth-checked (flags feasible=false with a note when macros are approximate). Slow (~15s AI call).
nutrition
nutrition_targets
The athlete's daily calorie + macro targets, computed from body stats, activity, and goal.
program
get_program
The athlete's current multi-day program (render-ready).
readiness
readiness_checkin
Record how the athlete feels today (energy, sleep, soreness — each 1–5). The engine scores readiness and, on the next get_todays_session, reshapes the workout accordingly (reduce volume / reduce intensity / recovery day). Returns the readiness score + modifier.
regenerate
regenerate_program
Rebuild the whole program from the stored profile (~20s AI generation). Use after a profile change or a plateau.
todays
get_todays_session
Today's workout: exercises, sets/reps, per-exercise load guidance and concrete target weights, plus nutrition targets and cycle status. Auto-applies the user's readiness check-in (autoregulation) if they've done one today. Call this to see what the athlete should do now.

Endpoints

URLTransportStateLatencyChecked
https://workout-engine-production-5dd7.up.railway.app/mcp streamable-http answering 351 ms 14 min ago

Fitfly Engine — questions

Answers built from our own checks of this server.

What can Fitfly Engine do?
It exposes 10 tools, read directly from the server on our last check. Among them: changelog, get_program, get_todays_session, list_swap_options, log_workout, meal_plan and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Fitfly Engine working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 351 ms. The bar chart above shows every period we have measured.
How do I connect Fitfly Engine?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Fitfly Engine need an API key?
No. Fitfly Engine completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Fitfly Engine?
It answers our handshake in 351 ms on average, which is faster than 40% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.