MCP Tools DirectoryAbout this integration
Fueling & recovery decision engine combining MacroFactor nutrition with Garmin training data
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- unknown
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.1
- Package
- macrofactor-mcp
- Last compatibility test
- Not independently tested
Connect your agent
macrofactor-mcpThe project is unofficial and not medical advice. Raw data stays in local DuckDB, but MCP tool results are sent to the configured client or model. Garmin is optional and requires a pre-existing token directory. Package behavior was not executed or independently security-audited.
Capabilities: Import MacroFactor workbook exports, Store local nutrition and activity data in DuckDB, Produce daily and weekly nutrition summaries, Optionally synchronize Garmin data, Compare nutrition with recovery signals
Connected profiles
Additional details
io.github.NasserAlbusaidi/macrofactor-mcp
Source ↗ · Checked 2026-09-170.1.1
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17macrofactor-mcp
Source ↗ · Checked 2026-09-190.1.1
Source ↗ · Checked 2026-09-19The publisher documents an uvx-launched stdio MCP process that imports new workbooks on startup. The package was not executed in this review.
Source ↗ · Checked 2026-09-19The core MacroFactor workflow uses local workbook exports and does not connect to a MacroFactor API. Optional Garmin support requires an existing local Garth/Garmin token directory, a mode outside the native authentication taxonomy.
Source ↗ · Checked 2026-09-19The MCP client launches macrofactor-mcp over stdio. MACROFACTOR_DATA_DIR selects the local export directory and MACROFACTOR_DB_PATH selects the local DuckDB file.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19