Cronometer
Pull Cronometer food logs, macros, fasting windows, biometrics, and recurring foods into agent-assisted health or quantified-self app development.
Overview
Cronometer MCP is a MCP server for the Build phase that syncs Cronometer food logs, macros, fasting, biometrics, and recurring foods to agents over stdio.
What is this MCP server?
- PyPI package cronometer-mcp version 2.0.3 with stdio transport
- Covers food logs, macros, fasting, biometrics, and recurring foods
- Authenticates with CRONOMETER_USERNAME and CRONOMETER_PASSWORD
- Optional CRONOMETER_DATA_DIR for local sync output (default under ~/.local/share/cronometer-mcp/)
- Open-source cphoskins/cronometer-mcp for health-tracking agent workflows
- Server version 2.0.3
- 5 documented data domains: food logs, macros, fasting, biometrics, recurring foods
- 3 environment variables (2 required credentials plus optional data dir)
Community signal: 12 GitHub stars.
What problem does it solve?
Health-app builders waste time manually exporting Cronometer CSVs or retyping macros when agents could work from live account data instead.
Who is it for?
Indie devs building nutrition dashboards, coaching bots, or quantified-self tooling tied to Cronometer as the system of record.
Skip if: Teams without Cronometer accounts, clinical deployments needing HIPAA-grade pipelines, or products that only need static USDA food databases.
What do I get? / Deliverables
After configuring Cronometer credentials, your agent can query and analyze synced nutrition and biometric datasets while you implement features.
- Synced Cronometer datasets accessible as MCP tools
- Local sync directory for agent-readable nutrition and biometric exports
- Agent-grounded macro and meal analysis during feature development
Recommended MCP Servers
Journey fit
Nutrition and biometric data access is a third-party integration task completed while building apps that surface personal health dashboards. Integrations matches account-authenticated sync to Cronometer rather than SEO, ads, or production incident response.
How it compares
Personal nutrition-account MCP bridge, not a generic calorie database or fitness marketplace skill.
Common Questions / FAQ
Who is io.github.cphoskins/cronometer for?
Solo builders and health-tech hobbyists who log food in Cronometer and want MCP access for agent-assisted app development and analysis.
When should I use io.github.cphoskins/cronometer?
Use it during Build when integrating meal tracking, macro summaries, fasting stats, or biometric trends from Cronometer into your product or scripts.
How do I add io.github.cphoskins/cronometer to my agent?
Run the cronometer-mcp PyPI package with stdio in your MCP config, set CRONOMETER_USERNAME and CRONOMETER_PASSWORD, and optionally CRONOMETER_DATA_DIR for sync output.