Cronometer Api Mcp

cronometer-api-mcp

[License: MIT] [CI] [Build Docker image] [PyPI]

Hosted version for Claude.ai, ChatGPT, and Grok coming soon. Join the waitlist →

An MCP (Model Context Protocol) server for Cronometer nutrition tracking, built on the reverse-engineered mobile REST API.

Unlike cronometer-mcp, which takes a comprehensive GWT-RPC approach against Cronometer's web backend, this server talks to the same JSON REST API used by the Cronometer Android app -- with clean payloads and stable, versioned endpoints.

Features

• Food log -- diary entries with food names, amounts, meal groups
• Nutrition data -- daily macro/micro totals and nutrition scores with per-nutrient confidence
• Food search -- search the Cronometer food database, get detailed nutrition info
• Diary management -- add/remove entries, copy days, mark days complete
• Custom foods -- create foods with custom nutrition data
• Macro targets -- read weekly schedule and saved templates
• Fasting -- view history and aggregate statistics
• Biometrics -- weight, body fat, heart rate, and other tracked metrics over a date range

Quick Start

1. Install uv

curl -LsSf https://astral.sh/uv/install.sh | sh

2. Set credentials

export CRONOMETER_USERNAME="[email protected]"export CRONOMETER_PASSWORD="your-password"

Optional: two-factor authentication

If the account has two-factor authentication enabled, /api/v2/login answers TOTP_CODE_REQUIRED unless the request carries the current 6-digit code. Give the server the base32 key that Cronometer showed when 2FA was set up (the same key you scanned into your authenticator app) and it derives the code itself at every login (RFC 6238, SHA-1, 30 s period):

export CRONOMETER_TOTP_SECRET="ABCD EFGH IJKL MNOP QRST UVWX YZ23 4567"

Spaces and lowercase are fine. Leave it unset for accounts without 2FA.

Optional: override the account timezone

Diary entries are stamped in your Cronometer account's timezone, which the server reports at login. If that zone is wrong (for example, an older build had reset it) you can force a specific IANA zone without changing your account settings:

export CRONOMETER_ACCOUNT_TZ="America/Los_Angeles"

When set, this takes precedence over both the value reported at login and any cached session, so it also overrides a stale cached timezone.

3. Configure your MCP client

uvx downloads and runs the server on demand -- no separate install step.

OpenCode (opencode.json)

{  "$schema": "https://opencode.ai/config.json",  "mcp": {    "cronometer": {      "type": "local",      "command": ["uvx", "cronometer-api-mcp"],      "environment": {        "CRONOMETER_USERNAME": "{env:CRONOMETER_USERNAME}",        "CRONOMETER_PASSWORD": "{env:CRONOMETER_PASSWORD}",        "CRONOMETER_TOTP_SECRET": "{env:CRONOMETER_TOTP_SECRET}",        "CRONOMETER_ACCOUNT_TZ": "{env:CRONOMETER_ACCOUNT_TZ}"      },      "enabled": true    }  }}

Claude Desktop (claude_desktop_config.json)

{  "mcpServers": {    "cronometer": {      "command": "uvx",      "args": ["cronometer-api-mcp"],      "env": {        "CRONOMETER_USERNAME": "[email protected]",        "CRONOMETER_PASSWORD": "your-password",        "CRONOMETER_TOTP_SECRET": "your-base32-key",        "CRONOMETER_ACCOUNT_TZ": "America/Los_Angeles"      }    }  }}

Available Tools

Food Log & Nutrition

Food Search & Details

Diary Management

Targets & Tracking

All date parameters use YYYY-MM-DD format and default to today when omitted.

Relative dates and recent days

get_food_log, get_daily_nutrition, and get_nutrition_scores also accept "today", "yesterday", and "N days ago" as their date. These are resolved at call time using your Cronometer account timezone, so Claude can pass relative inputs without relying on dates from earlier in a long conversation.

get_food_log and get_daily_nutrition accept days (1–31, default 1), counting back from the inclusive end date:

get_food_log(date="yesterday")get_nutrition_scores(date="3 days ago")get_daily_nutrition(days=3)  # Last 3 days, including todayget_daily_nutrition(date="yesterday", days=3)  # Previous 3 complete calendar daysget_food_log(days=7)  # Recent meals, including today

For “my calories the last few days,” use get_daily_nutrition(days=3). Single-day responses retain their existing shape. Multi-day responses contain start_date, end_date, and a days list of daily results, oldest first. Returned dates are always concrete YYYY-MM-DD values.

Transport

stdio only. For remote/hosted use, the stdio server is wrapped by supergateway (see Dockerfile), which owns the HTTP listener and exposes MCP streamable-HTTP at /mcp. The server has no built-in authentication — any remote deployment must sit behind an authenticating gateway or reverse proxy.

Development

For local development, copy .env.example to .env and fill in your credentials:

cp .env.example .env# edit .envuv run cronometer-api-mcp

The CLI auto-loads .env on startup (dev convenience only). Real environment variables always win over .env, so production deployments and MCP client env blocks are unaffected.

How It Works

This server communicates with mobile.cronometer.com -- the same REST API used by the Cronometer Android/Flutter app. The API was reverse-engineered through:

1. Static analysis of libapp.so (Dart AOT snapshot) from the APK to discover endpoint names
2. Traffic interception via Frida + mitmproxy to capture exact request/response formats
3. Trial-and-error against the live API to confirm payload shapes

The API uses two protocols:

• v2 (POST /api/v2/*) -- JSON-body auth, used for most operations (food search, diary read/write, nutrition, fasting, macros, biometrics)
• v3 (DELETE /api/v3/user/{id}/*) -- Header-based auth (x-crono-session), used for diary entry deletion

Recipe import is the one asynchronous operation: import_recipe returns a job id, and poll_async_result is polled until the server reports 100% progress and attaches the parsed ingredients.

Python API

You can use the client directly:

from cronometer_api_mcp.client import CronometerClientfrom datetime import date
client = CronometerClient()
# Search for foodsresults = client.search_food("chicken breast")
# Get food detailsfood = client.get_food(results[0]["id"])
# Log a servingclient.add_serving(    food_id=food["id"],    measure_id=food["defaultMeasureId"],    grams=200,)
# Get today's diarydiary = client.get_diary()
# Import a recipe from a free-text ingredient listrecipe = client.import_recipe("one hot dog\nketchup\nbun")print(recipe["food_id"], recipe["ingredients"])
# Parse without saving, to review the matches firstpreview = client.import_recipe("2 tbsp olive oil\n200g chicken", save=False)
# Get nutrition scoresscores = client.get_nutrition_scores()

License

MIT