Official description7 sourcesMCP servers8d ago

NasserAlbusaidi/macrofactor-mcp

Am I recovered? Did my fueling work? MCP server combining MacroFactor nutrition with Garmin training data — a local fueling & recovery decision engine.

View on GitHub ↗Direct link · no redirect page

Config template (adjust for your client)

claude mcp add macrofactor-mcp -- npx -y macrofactor-mcp

A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.

Star count: 2 ★ · NasserAlbusaidi/macrofactor-mcp · read from the GitHub search API · (checked 2026-10-16 20:00:20)
Source: collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history: first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score: score 703 · 2 ★ · 7 sources · mcp

FAQ (answers come from our records)

How do I install it?

We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.

Who is it for?

We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.

Who maintains it?

repository NasserAlbusaidi/macrofactor-mcp；first catalogued 2026-10-09；last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.

Third-party quality signals

Am I recovered? Did my fueling work? What should change next week?

以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →

The only MCP combining MacroFactor nutrition with Garmin training data.
MacroFactor MCP is a local Fueling & Recovery Decision Engine. Give your MCP
client a MacroFactor export, optionally add Garmin, and ask for a decision
instead of manually comparing nutrition, sleep, body, and training screens.
Quickstart
Install uv, then confirm the packaged server starts:
Export your data from MacroFactor, put the .xlsx file in one local directory,
and add this to your MCP client configuration. Use absolute paths.
Restart the MCP client. The server imports new workbooks on startup. Run
setup_check, then ask one of the questions below. If a desktop client cannot
find uvx, replace "uvx" with the absolute path returned by which uvx.
Four flagship workflows
All examples below use synthetic data.
recovery_check — Am I recovered?
Combines last night's sleep, HRV, body battery, training load, and yesterday's
fueling into a readiness view.
daily_briefing — What do today's signals say together?
Shows the day as one picture instead of separate nutrition and training logs.
weekly_report — What should change next week?
Reviews seven days of nutrition, weight, workouts, sleep, and training load.
nutrition_performance_correlation — Did my fueling work?
Compares nutrition with next-day Garmin recovery signals. It reports sample
sizes so small or missing datasets stay visible.
MacroFactor-only or MacroFactor + Garmin
| Mode | Decisions available |
|---|---|
| MacroFactor only | Nutrition, weight, workouts, daily_briefing, and weekly_report. Recovery output uses the nutrition signals that exist. |
| MacroFactor + Garmin | All four flagship workflows, including sleep, HRV, body battery, activities, and training load. |
Garmin is optional. To enable it, point GARMINTOKENS at an existing local
Garth/Garmin token directory, then run sync_garmin.
Platform support
- macOS and Linux
- Windows is untested
- Python 3.10 or newer
Limitations
- v0.1 requires a manual MacroFactor export; it does not connect to a MacroFactor API.
- Garmin correlation workflows need overlapping MacroFactor and Garmin dates.
- Correlations are observational, not proof that one behavior caused another outcome.
- Import support follows the current MacroFactor Quick Export and All-Time Data workbook layouts.
Privacy
Raw nutrition, body, workout, and Garmin data stays in the local DuckDB