官方说明7 个来源MCP 服务8 天前
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.
在 GitHub 查看 ↗直链 · 无中转页
配置模板（请按你的客户端调整）
claude mcp add macrofactor-mcp -- npx -y macrofactor-mcp
这是根据仓库名生成的可粘贴骨架，命令行参数与包名请以该项目 README 为准。
- ★ 数取值
- 2 ★ · NasserAlbusaidi/macrofactor-mcp · 取自 GitHub 搜索 API · （2026-10-16 20:00:20 核对）
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
- 收录与活跃
- 收录于 2026-10-09 · 最近见到 2026-10-16 · 共见到 32 次 · 被 7 个来源列出
- 评分构成
- 综合分 703 · 2 ★ · 7 个来源 · mcp
常见问题（答案都来自我们的记录）
怎么安装？
我们【没有】从该仓库取到安装命令（我们的 install 覆盖率只有约 4%）。请看它的 README 或 releases 页。
它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
NasserAlbusaidi/macrofactor-mcp；我们收录于 2026-10-09；最近见到 2026-10-16。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。第三方质量标记
**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
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
- 来源
- awesome · https://github.com/NasserAlbusaidi/macrofactor-mcp
- 按领域浏览
- MCP 服务
- Traction
- 2 ★
- 收录于
- 昨天
更多MCP 服务
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。