cronometer-api-mcp — Claude Code MCP server: install guide
Connects your Cronometer nutrition log to an AI assistant via mobile REST endpoints. Tracks daily calories, macros, biometrics, and diary entries right in chat.
claude mcp add --env CRONOMETER_USERNAME=<CRONOMETER_USERNAME> --env CRONOMETER_PASSWORD=<CRONOMETER_PASSWORD> --env CRONOMETER_TOTP_SECRET=<CRONOMETER_TOTP_SECRET> --env CRONOMETER_ACCOUNT_TZ=<CRONOMETER_ACCOUNT_TZ> --transport stdio cronometer-api-mcp -- uvx cronometer-api-mcpWhat cronometer-api-mcp does
The server communicates with the mobile JSON endpoints used by the Cronometer Android app rather than the web interface. It gives the assistant tools to inspect food logs (get_food_log), calculate nutrient sums (get_daily_nutrition), search items (search_foods), and record meals. It also handles recipe creation from text lists, fasting intervals, and biometric metrics such as weight or heart rate.
Running the tool requires uvx alongside CRONOMETER_USERNAME and CRONOMETER_PASSWORD in the environment. If two-factor authentication is active on the account, omitting CRONOMETER_TOTP_SECRET results in an authentication failure with TOTP_CODE_REQUIRED. You can also configure an explicit IANA zone through CRONOMETER_ACCOUNT_TZ to keep diary timestamps accurate.
What it helps with
- log meals and food portions into the daily diary
- inspect daily macro and micronutrient intake
- search the Cronometer food database for nutritional breakdowns
- retrieve fasting logs and biometric trends over time
Example prompts for the agent
- What are my total calories and protein intake logged for yesterday?
- Add 150 grams of cooked brown rice to my lunch diary.
- Show my weight and body fat trends for the past two weeks.
How to install cronometer-api-mcp
Platform CLI
claude mcp add --env CRONOMETER_USERNAME=<CRONOMETER_USERNAME> --env CRONOMETER_PASSWORD=<CRONOMETER_PASSWORD> --env CRONOMETER_TOTP_SECRET=<CRONOMETER_TOTP_SECRET> --env CRONOMETER_ACCOUNT_TZ=<CRONOMETER_ACCOUNT_TZ> --transport stdio cronometer-api-mcp -- uvx cronometer-api-mcpReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from cronometer-api-mcp <command>
Platform CLI
codex mcp add cronometer-api-mcp --env CRONOMETER_USERNAME=<CRONOMETER_USERNAME> --env CRONOMETER_PASSWORD=<CRONOMETER_PASSWORD> --env CRONOMETER_TOTP_SECRET=<CRONOMETER_TOTP_SECRET> --env CRONOMETER_ACCOUNT_TZ=<CRONOMETER_ACCOUNT_TZ> -- uvx cronometer-api-mcpReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from cronometer-api-mcp <command>
Config file
{
"mcpServers": {
"cronometer-api-mcp": {
"command": "uvx",
"args": [
"cronometer-api-mcp"
],
"env": {
"CRONOMETER_USERNAME": "<CRONOMETER_USERNAME>",
"CRONOMETER_PASSWORD": "<CRONOMETER_PASSWORD>",
"CRONOMETER_TOTP_SECRET": "<CRONOMETER_TOTP_SECRET>",
"CRONOMETER_ACCOUNT_TZ": "<CRONOMETER_ACCOUNT_TZ>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from cronometer-api-mcp <command>
Config file
{
"servers": {
"cronometer-api-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"cronometer-api-mcp"
],
"env": {
"CRONOMETER_USERNAME": "<CRONOMETER_USERNAME>",
"CRONOMETER_PASSWORD": "<CRONOMETER_PASSWORD>",
"CRONOMETER_TOTP_SECRET": "<CRONOMETER_TOTP_SECRET>",
"CRONOMETER_ACCOUNT_TZ": "<CRONOMETER_ACCOUNT_TZ>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from cronometer-api-mcp <command>
Platform CLI
gemini mcp add -e CRONOMETER_USERNAME=<CRONOMETER_USERNAME> -e CRONOMETER_PASSWORD=<CRONOMETER_PASSWORD> -e CRONOMETER_TOTP_SECRET=<CRONOMETER_TOTP_SECRET> -e CRONOMETER_ACCOUNT_TZ=<CRONOMETER_ACCOUNT_TZ> cronometer-api-mcp uvx cronometer-api-mcpReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from cronometer-api-mcp <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about cronometer-api-mcp
How do I install cronometer-api-mcp in Claude Code?
Run `claude mcp add --env CRONOMETER_USERNAME=<CRONOMETER_USERNAME> --env CRONOMETER_PASSWORD=<CRONOMETER_PASSWORD> --env CRONOMETER_TOTP_SECRET=<CRONOMETER_TOTP_SECRET> --env CRONOMETER_ACCOUNT_TZ=<CRONOMETER_ACCOUNT_TZ> --transport stdio cronometer-api-mcp -- uvx cronometer-api-mcp in your terminal. Make sure uv` is installed on your system.
What does cronometer-api-mcp do?
It exposes Cronometer tools to your MCP client. You can inspect nutritional totals, add or edit logged meals, create custom recipes, and monitor biometric metrics.
How do I handle two-factor authentication?
Pass your base32 setup key into CRONOMETER_TOTP_SECRET. The server generates the 6-digit RFC 6238 code automatically whenever a login attempt runs.
