An MCP server that connects to a user's Cronometer account and exposes nutrition diary, fasting, biometrics, macro targets, recurring foods, and export/sync operations. It authenticates with Cronometer web credentials and uses internal web-app protocols to read and modify data.
From the registry: MCP server for Cronometer — food logs, macros, fasting, biometrics, and recurring foods
$ pip install cronometer-mcpPlease install the `cronometer` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Cronometer Gold account** — Requires a paid Cronometer account (Gold or equivalent that supports web login). (https://cronometer.com)
- **Install cronometer-mcp** — Install the PyPI package. Run: `pip install cronometer-mcp` (https://pypi.org/project/cronometer-mcp/)
Canonical MCP server config (stdio transport):
- command: `cronometer-mcp`
- args: []
- required environment variables:
- `CRONOMETER_USERNAME`: Cronometer account email. (example: `<your@email.com>`)
- `CRONOMETER_PASSWORD`: Cronometer account password. (example: `<your-password>`)
- optional environment variables:
- `CRONOMETER_DATA_DIR`: Directory for JSON exports and food-log.md output. (example: `/path/to/data/cronometer`)
Note: Unofficial client — uses the GWT-RPC protocol scraped from Cronometer's web app. May break on Cronometer deploys (permutation hash hardcoded).
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.CRONOMETER_USERNAMErequiredCronometer account username/email used to authenticateCRONOMETER_PASSWORDrequiredCronometer account password used to authenticateAtlassian Rovo MCP Server