What can you do with this server?

Access and manage a Cronometer Gold account's nutrition data through any MCP-compatible client. * Read food logs, daily macro totals, micronutrient breakdowns, and raw CSV exports. * Search foods, view food details, add/remove diary entries, copy days, and mark days complete. * Manage recurring foods, macro targets/templates/weekly schedules, fasting history/stats, and biometrics. * Sync exports to local JSON files and generate a markdown food log. * Run read-only or over streamable HTTP, depending on configuration.

How do I use cronometer-mcp?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@cronometer-mcp show me my food log and macro summary for today" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

cronometer-mcp

by cphoskins

Overview Schema Source Related Servers Discussions Admin

Python

Remote

cronometer-mcp

An MCP (Model Context Protocol) server that provides access to your Cronometer nutrition data. Pull detailed food logs, daily macro/micro summaries, manage diary entries, fasting, biometrics, and recurring foods — all from Claude, Cursor, or any MCP-compatible client.

Requires a Cronometer Gold account (or any paid tier that supports web login).

Features

Food log — individual food entries with full macro and micronutrient breakdown
Daily nutrition — daily calorie, protein, carb, fat, and fiber totals
Micronutrients — detailed vitamin/mineral breakdown with period averages
Diary management — add/remove food entries, copy entire days, mark days complete
Recurring foods — create, list, and delete repeat items that auto-log on selected days
Macro targets — read/write daily targets, create templates, set weekly schedules
Fasting — view history and stats, cancel or delete fasts
Biometrics — log and remove weight, blood glucose, heart rate, body fat
Raw CSV export — servings, daily summary, exercises, biometrics, or notes
Sync to disk — download JSON exports and generate a markdown food log

Related MCP server: MacroMCP

Quick Start

1. Install

pip install cronometer-mcp

Or install from source:

git clone https://github.com/cphoskins/cronometer-mcp.git
cd cronometer-mcp
pip install -e .

2. Set credentials

export CRONOMETER_USERNAME="your@email.com"
export CRONOMETER_PASSWORD="your-password"

Or add them to a .env file in your project root (if your MCP client supports it).

3. Configure your MCP client

Claude Code (`.mcp.json`)

{
  "mcpServers": {
    "cronometer": {
      "command": "cronometer-mcp",
      "env": {
        "CRONOMETER_USERNAME": "your@email.com",
        "CRONOMETER_PASSWORD": "your-password"
      }
    }
  }
}

Claude Desktop (`claude_desktop_config.json`)

{
  "mcpServers": {
    "cronometer": {
      "command": "cronometer-mcp",
      "env": {
        "CRONOMETER_USERNAME": "your@email.com",
        "CRONOMETER_PASSWORD": "your-password"
      }
    }
  }
}

If you installed from source with pip install -e ., you can also use the full Python path:

{
  "command": "/path/to/venv/bin/python",
  "args": ["-m", "cronometer_mcp.server"]
}

Read-only mode

Set CRONOMETER_READ_ONLY=1 (also accepts true or yes) in the server's env to expose only the read tools. The 13 tools that change your Cronometer account are not registered at all, so the client never sees them: adding or removing food entries, macro targets, schedules and templates, fasts, biometrics, copy day, mark day complete, and repeat items. sync_cronometer stays available; it only writes files on your machine.

This limits what the server offers, not what your credentials can do. Cronometer has no read-only login, so the password in env still has full access to the account.

Remote access (streamable HTTP)

By default the server talks to its client over stdio. To run it on another machine or in a container, set CRONOMETER_TRANSPORT=streamable-http and it serves the MCP endpoint at http://<host>:<port>/mcp instead.

Variable	Default	Meaning
`CRONOMETER_TRANSPORT`	`stdio`	`stdio` or `streamable-http`
`CRONOMETER_HOST`	`127.0.0.1`	Interface to bind. Use `0.0.0.0` inside a container.
`CRONOMETER_PORT`	`8000`	TCP port, 1 to 65535
`CRONOMETER_ALLOWED_HOSTS`	unset	Comma-separated `Host` header values clients may use, as `host:port` or `host:*`. Set it whenever the bind host is not loopback.

In Docker, against the published package, reachable as your-server on your network:

docker run --rm -p 8000:8000 \
  -e CRONOMETER_USERNAME=your@email.com \
  -e CRONOMETER_PASSWORD=your-password \
  -e CRONOMETER_TRANSPORT=streamable-http \
  -e CRONOMETER_HOST=0.0.0.0 \
  -e CRONOMETER_ALLOWED_HOSTS=your-server:8000 \
  python:3.12-slim sh -c "pip install -q cronometer-mcp && cronometer-mcp"

CRONOMETER_ALLOWED_HOSTS matters: the MCP SDK checks Host and Origin headers on its own only when bound to loopback. On any other bind it accepts every Host, which lets a web page you happen to open on the same network reach the server through DNS rebinding. With the allowlist set, requests whose Host or Origin is not on it get 421 or 403. Without it the server logs a warning at startup and runs anyway.

Then point the client at the URL. Claude Code (.mcp.json):

{
  "mcpServers": {
    "cronometer": {
      "type": "http",
      "url": "http://your-server:8000/mcp"
    }
  }
}

The endpoint has no authentication. Anyone who can reach the port can read and change the Cronometer account whose credentials the server holds. Keep it bound to 127.0.0.1, or put it on a network only you can reach (a VPN or Tailscale keeps strangers out; it does not stop the DNS rebinding case above, so set the allowlist as well) or behind a reverse proxy that authenticates. Adding CRONOMETER_READ_ONLY=1 narrows what a remote client can do, with the same caveat as above: the credentials themselves keep full access.

Available Tools

Food Log & Nutrition

Tool	Description
`get_food_log`	Individual food entries with macros + micros for a date range
`get_daily_nutrition`	Daily macro totals (calories, protein, carbs, fat, fiber)
`get_micronutrients`	Detailed vitamin/mineral breakdown with period averages
`export_raw_csv`	Raw CSV export for any data type (servings, exercises, biometrics, etc.)

Food Search & Diary Management

Tool	Description
`search_foods`	Search the Cronometer food database
`list_diary_groups`	List this account's diary groups and the values `diary_group` accepts
`get_food_details`	Get full nutrition info and serving measure IDs for a food
`add_food_entry`	Add a food entry to the diary
`remove_food_entry`	Remove a food entry from the diary
`copy_day`	Copy all diary entries from one date to another
`set_day_complete`	Mark a diary day as complete or incomplete

Recurring Foods (Repeat Items)

Tool	Description
`get_repeated_items`	List all recurring food entries
`add_repeat_item`	Add a recurring food entry that auto-logs on selected days
`delete_repeat_item`	Delete a recurring food entry

Macro Targets & Templates

Tool	Description
`get_macro_targets`	Get daily macro targets (or full weekly schedule with `target_date="all"`)
`set_macro_targets`	Update daily macro targets (partial updates supported)
`list_macro_templates`	List all saved macro target templates
`create_macro_template`	Create a new saved macro target template
`set_weekly_macro_schedule`	Assign a template to days of the week as the recurring default

Fasting

Tool	Description
`get_fasting_history`	View all fasts or fasts within a date range
`get_fasting_stats`	Aggregate fasting statistics (total hours, longest, averages)
`cancel_active_fast`	Cancel an in-progress fast while preserving the recurring schedule
`delete_fast`	Delete a fast entry

Biometrics

Tool	Description
`get_recent_biometrics`	Get recently logged biometric entries
`add_biometric`	Log weight (lbs), blood glucose (mg/dL), heart rate (bpm), or body fat (%)
`remove_biometric`	Remove a biometric entry

Sync

Tool	Description
`sync_cronometer`	Download JSON exports + generate food-log.md to disk

Tool Parameters

All date parameters use YYYY-MM-DD format. Most tools default to today or the last 7 days when dates are omitted.

Key parameter patterns:

diary_group — a diary group name (case-insensitive) or a 0-based index. Cronometer Gold gives every account 8 diary group slots and lets you rename and enable them freely, so the names are account-specific and are not always Breakfast/Lunch/Dinner/Snacks. Call list_diary_groups to see yours. On an untouched account the four standard meals are indices 1–4 (index 0 is a slot that ships disabled). Unknown names, disabled groups, and out-of-range indices are rejected rather than silently defaulting — Cronometer itself accepts a bad index without complaint and the entry becomes unreachable.
days_of_week — "all", "weekdays", "weekends", or comma-separated day numbers (0=Sun through 6=Sat)
measure_id — pass 0 to use the universal gram-based measure (works for all food sources)
target_date — pass "all" on get_macro_targets to get the full weekly schedule

Sync Output

The sync_cronometer tool saves files to ~/.local/share/cronometer-mcp/ by default. Override with the CRONOMETER_DATA_DIR environment variable:

export CRONOMETER_DATA_DIR="/path/to/your/project/data/cronometer"

Output files:

exports/servings_{start}_{end}.json
exports/daily_summary_{start}_{end}.json
exports/servings_latest.json
exports/daily_summary_latest.json
food-log.md

How It Works

Cronometer does not have a public API for individual users. This server uses the same GWT-RPC (Google Web Toolkit Remote Procedure Call) protocol that the Cronometer web app uses internally:

Fetches the login page to get an anti-CSRF token
POSTs credentials to authenticate
Calls GWT-RPC authenticate to get a user ID
Calls GWT-RPC generateAuthorizationToken for short-lived export tokens
Downloads CSV exports using the token
Calls GWT-RPC methods directly for diary edits, fasting, biometrics, macro targets, and repeat items

Session cookies are persisted to ~/.local/share/cronometer-mcp/.session_cookies so that subsequent invocations reuse the session without re-authenticating (Cronometer has aggressive login rate limiting).

GWT Magic Values

The GWT protocol uses a permutation hash and header value that are baked into each Cronometer web deploy. These values are hardcoded in the client and may break when Cronometer pushes a new build.

Current values (as of February 2026):

Permutation: 7B121DC5483BF272B1BC1916DA9FA963
Header: 2D6A926E3729946302DC68073CB0D550

If authentication starts failing with GWT errors, these values likely need updating. You can find the current values by:

Opening Cronometer in your browser
Going to Developer Tools → Network tab
Looking for requests to cronometer.com/cronometer/app
Checking the x-gwt-permutation header and the payload structure

You can override them via the CronometerClient constructor:

from cronometer_mcp import CronometerClient

client = CronometerClient(
    gwt_permutation="NEW_PERMUTATION_HASH",
    gwt_header="NEW_HEADER_VALUE",
)

Python API

You can also use the client directly in Python:

from datetime import date, timedelta
from cronometer_mcp import CronometerClient

client = CronometerClient()  # reads from env vars

# Get today's food log
foods = client.get_food_log()

# Get last 7 days of daily summaries
start = date.today() - timedelta(days=7)
summaries = client.get_daily_summary(start)

# Raw CSV export
csv_text = client.export_raw("exercises", start, date.today())

# Copy a day's diary entries
client.copy_day(date(2026, 3, 1), date(2026, 3, 8))

# Add a recurring food entry (every weekday)
client.add_repeat_item(
    food_source_id=12345,
    measure_id=0,        # universal gram-based measure
    quantity=200,
    food_name="Oatmeal",
    diary_group=1,       # 0-based wire index; 1 == Breakfast on a default account
    days_of_week=[1, 2, 3, 4, 5],
)

# Diary groups are user-configured - check what this account actually has
for g in client.diary_groups:
    print(g["wire_index"], g["name"], g["enabled"])

# Log a biometric
client.add_biometric("weight", 218.5, date.today())

License

MIT

Available Tools

27 tools

add_biometricA

Add a biometric entry to Cronometer.

Supported metric types: weight (lbs), blood_glucose (mg/dL), heart_rate (bpm), body_fat (%).

Args: metric_type: One of 'weight', 'blood_glucose', 'heart_rate', 'body_fat'. value: The value in display units (lbs, mg/dL, bpm, %). entry_date: Date as YYYY-MM-DD.

Inputs: value (required), entry_date (required), metric_type (required). Returns: result

add_food_entryA

Add a food entry to the Cronometer diary.

Use search_foods to find food_id and food_source_id, then get_food_details for measure_id and weight_grams.

For CRDB/custom foods, you can omit measure_id (defaults to a universal NCCDB measure that works for all food sources). When measure_id is omitted, quantity is set to weight_grams.

Args: food_id: Numeric food ID from search_foods results. food_source_id: Food source ID from search_foods results. weight_grams: Weight of the serving in grams. date: Date to log the entry as YYYY-MM-DD (e.g. "2026-03-04"). measure_id: Measure/unit ID. Pass 0 (default) to use the universal measure that works for all food sources. quantity: Number of servings. Defaults to weight_grams when measure_id is 0 (universal gram-based measure). diary_group: Diary group name (case-insensitive) or 0-based index. Names are user-configured and are not always Breakfast/Lunch/Dinner/Snacks — call list_diary_groups to see this account's groups. Defaults to a time-of-day choice among enabled groups if omitted.

Inputs: date (required), food_id (required), weight_grams (required), food_source_id (required), +3 more. Returns: result

add_repeat_itemA

Add a recurring food entry that auto-logs on selected days.

Quantity is in default servings for the food (e.g., for coffee where the default serving is 1 cup, quantity=12 means 12 cups).

Use search_foods to find food_id and food_source_id.

Args: food_id: Numeric food ID from search_foods results. food_source_id: Food source ID from search_foods results. quantity: Number of default servings. food_name: Display name for the food. diary_group: Diary group name (case-insensitive) or 0-based index. Names are user-configured — call list_diary_groups to see this account's groups. Defaults to a time-of-day choice among enabled groups if omitted. days_of_week: Comma-separated day numbers (0=Sun, 1=Mon, ..., 6=Sat), or "all" for every day (default), or "weekdays", or "weekends".

Inputs: food_id (required), quantity (required), food_name (required), food_source_id (required), +2 more. Returns: result

cancel_active_fastA

Cancel an active (in-progress) fast while preserving the recurring schedule.

Use get_fasting_history to find active fasts (is_active=true).

Args: fast_id: The fast ID of the active fast to cancel.

Inputs: fast_id (required). Returns: result

copy_dayA

Copy all diary entries from one date to another.

Server-side operation that copies ALL entries (food, exercise, notes, biometrics) from source to destination. Additive — does not remove existing entries on the destination date.

Args: source_date: Date to copy FROM as YYYY-MM-DD. destination_date: Date to copy TO as YYYY-MM-DD.

Inputs: source_date (required), destination_date (required). Returns: result

create_macro_templateA

Create a new saved macro target template in Cronometer.

Optionally assigns it to all days of the week as the recurring default.

Args: template_name: Name for the new template (e.g. "Retatrutide GI-Optimized"). protein_grams: Protein target in grams. fat_grams: Fat target in grams. carbs_grams: Net carbs target in grams. calories: Calorie target in kcal. assign_to_all_days: If True, also set this as the recurring weekly schedule for all 7 days (default False).

Inputs: calories (required), fat_grams (required), carbs_grams (required), protein_grams (required), +2 more. Returns: result

delete_fastA

Delete a fast entry from Cronometer.

Use get_fasting_history first to find the fast_id.

Args: fast_id: The fast ID to delete.

Inputs: fast_id (required). Returns: result

delete_repeat_itemA

Delete a recurring food entry.

Use get_repeated_items to find the repeat_item_id.

Args: repeat_item_id: The ID of the repeat item to delete.

Inputs: repeat_item_id (required). Returns: result

export_raw_csvA

Export raw CSV data from Cronometer for any data type.

Useful when you need the full unprocessed export.

Args: export_type: One of 'servings', 'daily_summary', 'exercises', 'biometrics', 'notes'. start_date: Start date as YYYY-MM-DD (defaults to today). end_date: End date as YYYY-MM-DD (defaults to today).

Inputs: export_type (required), end_date, start_date. Returns: result

get_daily_nutritionA

Get daily nutrition summary with macro totals per day.

Returns calorie, protein, carb, fat, and fiber totals for each day. Use this for quick daily overviews and trend analysis.

Args: start_date: Start date as YYYY-MM-DD (defaults to 7 days ago). end_date: End date as YYYY-MM-DD (defaults to today).

Inputs: end_date, start_date. Returns: result

get_fasting_historyA

Get fasting history from Cronometer.

Returns all fasts (or fasts within a date range) with their status, names, recurrence rules, and timestamps.

Args: start_date: Start date as YYYY-MM-DD (omit for all history). end_date: End date as YYYY-MM-DD (omit for all history).

Inputs: end_date, start_date. Returns: result

get_fasting_statsA

Get aggregate fasting statistics from Cronometer.

Returns total fasting hours, longest fast, 7-fast average, and completed fast count.

Inputs: no named parameters. Returns: result

get_food_detailsA

Get detailed food information including available serving measures.

Use this after search_foods to get the measure_id needed for add_food_entry. Returns all available serving sizes with their numeric IDs and gram weights.

Args: food_source_id: Food source ID from search_foods results.

Inputs: food_source_id (required). Returns: result

get_food_logA

Get detailed food log with individual food entries and full nutrition.

Returns every food entry with macros and micronutrients. Great for analyzing what was eaten and spotting nutrient gaps.

Args: start_date: Start date as YYYY-MM-DD (defaults to today). end_date: End date as YYYY-MM-DD (defaults to today).

Inputs: end_date, start_date. Returns: result

get_macro_targetsA

Get current daily macro targets from Cronometer.

Returns the effective macro targets (protein, fat, carbs, calories) and the template name for a specific date or all days of the week. A macro with no target set in Cronometer is null.

Args: target_date: Date as YYYY-MM-DD to get targets for (defaults to today). Pass "all" to get the full weekly schedule.

Inputs: target_date. Returns: result

get_micronutrientsB

Get detailed micronutrient breakdown for meal planning.

Shows vitamins, minerals, and other micronutrients per day with period averages. Use this to identify nutrient gaps and plan meals.

Args: start_date: Start date as YYYY-MM-DD (defaults to 7 days ago). end_date: End date as YYYY-MM-DD (defaults to today).

Inputs: end_date, start_date. Returns: result

get_recent_biometricsA

Get the most recently logged biometric entries from Cronometer.

Returns recent values for weight, blood glucose, blood pressure, heart rate, body fat, and other tracked biometrics.

Inputs: no named parameters. Returns: result

get_repeated_itemsA

List all recurring food entries.

Returns all repeat items configured in Cronometer, including their food name, quantity, measure, diary group, and which days of the week they repeat on.

Inputs: no named parameters. Returns: result

list_diary_groupsA

List this account's diary groups, with the values add_food_entry accepts.

Diary group names are user-configured in Cronometer, so they are NOT always Breakfast/Lunch/Dinner/Snacks. Call this before assuming a name exists — an account may rename any slot or enable extra ones.

Returns each group's wire_index (the 0-based value add_food_entry takes), its name, and whether it is enabled. Only enabled groups can be written to.

Inputs: no named parameters. Returns: result

list_macro_templatesA

List all saved macro target templates in Cronometer.

Returns template names, IDs, and their macro values. Use this to find the template_name for set_weekly_macro_schedule.

Inputs: no named parameters. Returns: result

remove_biometricA

Remove a biometric entry from Cronometer.

Use get_recent_biometrics to find biometric_id values.

Args: biometric_id: The biometric entry ID (e.g. "BXW0DA").

Inputs: biometric_id (required). Returns: result

remove_food_entryA

Remove a food entry from the Cronometer diary.

Args: serving_id: The serving ID returned by add_food_entry (e.g. "D80lp$").

Inputs: serving_id (required). Returns: result

search_foodsA

Search Cronometer's food database by name.

Returns matching foods with their IDs and source information needed to add a serving (food_id, food_source_id, measure_id).

Args: query: Food name or keyword to search for (e.g. "eggs", "chicken breast").

Inputs: query (required). Returns: result

set_day_completeA

Mark a diary day as complete or incomplete.

Args: date: Date to mark as YYYY-MM-DD. complete: True to mark complete, False to mark incomplete.

Inputs: date (required), complete. Returns: result

set_macro_targetsA

Update daily macro targets in Cronometer.

Reads current targets first, then updates only the provided values. Omitted values remain unchanged.

Args: protein_grams: Protein target in grams. fat_grams: Fat target in grams. carbs_grams: Net carbs target in grams. calories: Calorie target in kcal. target_date: Date as YYYY-MM-DD (defaults to today). template_name: Template name (defaults to "Custom Targets").

Inputs: calories, fat_grams, carbs_grams, target_date, +2 more. Returns: result

set_weekly_macro_scheduleA

Set the recurring weekly macro schedule by assigning a template to days.

This updates the DEFAULT schedule that applies to all future dates, not just a specific date override.

First finds the template by name (from existing saved templates or from a recently created per-date template), then assigns it to the specified days of the week.

Args: template_name: Name of a saved macro target template (e.g. "Retatrutide GI-Optimized", "Keto Rigorous"). days: Comma-separated day names or "all" (default). E.g. "Monday,Wednesday,Friday" or "all".

Inputs: template_name (required), days. Returns: result

sync_cronometerA

Download Cronometer data and save locally as JSON + food-log.md.

Downloads servings and daily summary data, saves JSON exports, and regenerates food-log.md.

Output directory defaults to ~/.local/share/cronometer-mcp/ but can be overridden with the CRONOMETER_DATA_DIR environment variable.

Args: start_date: Start date as YYYY-MM-DD (defaults to days ago). end_date: End date as YYYY-MM-DD (defaults to today). days: Number of days to look back if start_date not specified (default 14). diet_label: Optional diet label for the markdown header (e.g., "Keto Rigorous").

Inputs: days, end_date, diet_label, start_date. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored 2026-10-04 02:15 across 27 tools

Disambiguation4/5

Most tools target a distinct resource+action, and descriptions clarify granularity (get_daily_nutrition = macro totals, get_micronutrients = micros, get_food_log = individual entries). However, these three nutrition-report tools plus export_raw_csv (daily_summary) overlap enough that an agent could reasonably pick the wrong one for 'get my nutrition data'.

Naming Consistency5/5

Every tool follows a predictable snake_case verb_noun pattern (get_/set_/add_/remove_/delete_/list_/search_/create_/cancel_/sync_/copy_). Consistent across all 27 tools with no convention mixing.

Tool Count3/5

27 tools is on the heavy side and sits at the borderline where separate subdomains (food logging, macros/templates, fasting, biometrics, repeat items, sync/export) each pull in their own tools. Defensible for a feature-rich domain but feels somewhat bloated.

Completeness4/5

Food entries, biometrics, macros/templates, fasting, repeat items, day copy/complete, sync and export are well covered. Minor gaps: no way to start a fast (only delete/cancel exist) and no update operations for food entries or biometrics, only add/remove.

Maintenance

ActivityNo data

ResponsivenessOutdated data

Resources

Related MCP Connectors

CoKarTa
io.github.AndresMuelas2004
Log meals and read your nutrition diary from Claude or ChatGPT.
Health & Wellness Note Taking
1
https://app.cokarta.com/mcp
Kairo
com.kairocalories
Calorie tracker app for ChatGPT and Claude: read meals, macros, weight and log meals from chat.
Health & Wellness Fitness Tracking
1
https://mcp.kairocalories.com/mcp
Withings Health Data
io.github.akutishevsky
MCP server for Withings health data — sleep, activity, heart, and body metrics.
Health & Wellness Research & Data
245
https://withings-mcp.com/mcp
web2md
org.web2md
MCP Server for Web2MD — convert URLs to Markdown from Claude Desktop, Cursor, etc.
Browser Automation Web Scraping
1
https://web2md.org/api/mcp

Related MCP Servers

foodvisor-mcp
Health & Wellness Fitness Tracking
cldt-fr
A
license
Not graded
quality
D
maintenance
MCP server integrating Foodvisor nutrition API for food search, meal logging, daily summaries, and progress tracking via LLM agents like Claude.
Updated 6 months ago (2026-05-09 09:43 UTC)
MIT
MacroMCP
Health & Wellness Fitness Tracking
lukew0824
F
license
Not graded
quality
C
maintenance
Remote MCP server for natural-language calorie/macro and weight tracking, designed to connect to Claude.ai as a custom connector.
Updated 4 months ago (2026-07-19 02:45 UTC)
-
io.github.rwestergren/cronomet
Health & Wellness Fitness Tracking
rwestergren
A
license
A
quality
A
maintenance
MCP server for Cronometer nutrition tracking, enabling food diary management, nutrition data retrieval, food search, and biometric tracking via Cronometer's mobile REST API.
Updated 4 days ago (2026-11-08 23:02 UTC)
19
71
MIT
cronometer-api-mcp
Health & Wellness Fitness Tracking
firaskudsy
A
license
A
quality
D
maintenance
MCP server for Cronometer nutrition tracking using the mobile API. Enables food logging, nutrition data retrieval, diary management, and fasting tracking.
Updated 3 months ago (2026-08-06 20:02 UTC)
13
1
MIT

cronometer-mcp

Features

Quick Start

1. Install

2. Set credentials

3. Configure your MCP client

Claude Code (.mcp.json)

Claude Desktop (claude_desktop_config.json)

Read-only mode

Remote access (streamable HTTP)

Available Tools

Food Log & Nutrition

Food Search & Diary Management

Recurring Foods (Repeat Items)

Macro Targets & Templates

Fasting

Biometrics

Sync

Tool Parameters

Sync Output

How It Works

GWT Magic Values

Python API

License

Available Tools

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

foodvisor-mcp

MacroMCP

io.github.rwestergren/cronomet

cronometer-api-mcp

Claude Code (`.mcp.json`)

Claude Desktop (`claude_desktop_config.json`)