MCP Tools DirectoryAbout this integration
MCP server for Cronometer nutrition tracking — food logs, diary, macros, fasting
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.2.3
- Package
- cronometer-api-mcp
- Last compatibility test
- Not independently tested
Connect your agent
cronometer-api-mcpPublisher documentation and manifest only; no package, personal health account, credential, or API was executed. The documented API is reverse-engineered and can expose or mutate sensitive health data.
Capabilities: Read food logs and nutrient totals, Manage diary foods, recipes, and day state, Read targets, fasting history, and biometrics
Connected profiles
Additional details
io.github.rwestergren/cronometer-api-mcp
Source ↗ · Checked 2026-09-170.2.3
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17CRONOMETER_USERNAME, CRONOMETER_PASSWORD
Source ↗ · Checked 2026-09-17cronometer-api-mcp
Source ↗ · Checked 2026-09-190.1.0
Source ↗ · Checked 2026-09-19The Python project exposes a console script, and the publisher documents stdio-only operation launched on demand through uvx.
Source ↗ · Checked 2026-09-19Cronometer account credentials are required, with an optional TOTP secret for accounts using two-factor authentication; this account-login flow is outside the native auth taxonomy.
Source ↗ · Checked 2026-09-19The server connects to Cronometer's mobile REST API; remote wrapping is explicitly separate and requires an authenticating gateway.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19