cronometer-mcp 2.0.0__tar.gz → 2.0.2__tar.gz

{cronometer_mcp-2.0.0 → cronometer_mcp-2.0.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cronometer-mcp
-Version: 2.0.0
+Version: 2.0.2
 Summary: MCP server for Cronometer nutrition data — pull food logs, macros, and micronutrients via the Model Context Protocol
 Project-URL: Homepage, https://github.com/cphoskins/cronometer-mcp
 Project-URL: Repository, https://github.com/cphoskins/cronometer-mcp
@@ -26,7 +26,7 @@ Description-Content-Type: text/markdown
 
 <!-- mcp-name: io.github.cphoskins/cronometer -->
 
-An [MCP (Model Context Protocol)](https://modelcontextprotocol.io/) server that provides access to your [Cronometer](https://cronometer.com/) nutrition data. Pull detailed food logs, daily macro/micro summaries, and raw CSV exports directly into Claude, Cursor, or any MCP-compatible client.
+An [MCP (Model Context Protocol)](https://modelcontextprotocol.io/) server that provides access to your [Cronometer](https://cronometer.com/) 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).
 
@@ -35,6 +35,11 @@ An [MCP (Model Context Protocol)](https://modelcontextprotocol.io/) server that
 - **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
 
@@ -108,31 +113,76 @@ If you installed from source with `pip install -e .`, you can also use the full
 
 ## 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 |
-| `get_food_details` | Get full nutrition info and measure IDs for a food |
+| `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 |
-| `get_macro_targets` | Get current daily macro targets (or weekly schedule with `target_date="all"`) |
+| `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:
+All date parameters use `YYYY-MM-DD` format. Most tools default to today or the last 7 days when dates are omitted.
 
-- `get_food_log(start_date?, end_date?)` — defaults to today
-- `get_daily_nutrition(start_date?, end_date?)` — defaults to last 7 days
-- `get_micronutrients(start_date?, end_date?)` — defaults to last 7 days
-- `export_raw_csv(export_type, start_date?, end_date?)` — type is one of: `servings`, `daily_summary`, `exercises`, `biometrics`, `notes`
-- `get_macro_targets(target_date?)` — defaults to today; pass `"all"` for weekly schedule
-- `set_macro_targets(protein_grams?, fat_grams?, carbs_grams?, calories?, target_date?, template_name?)` — reads current targets first, merges provided values
-- `sync_cronometer(start_date?, end_date?, days?, diet_label?)` — `days` defaults to 14; `diet_label` is optional text for the markdown header
+Key parameter patterns:
+- `diary_group` — one of `"Breakfast"`, `"Lunch"`, `"Dinner"`, `"Snacks"` (case-insensitive)
+- `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
 
@@ -158,6 +208,9 @@ Cronometer does not have a public API for individual users. This server uses the
 3. Calls GWT-RPC `authenticate` to get a user ID
 4. Calls GWT-RPC `generateAuthorizationToken` for short-lived export tokens
 5. Downloads CSV exports using the token
+6. 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
 
@@ -204,6 +257,22 @@ 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,       # Breakfast
+    days_of_week=[1, 2, 3, 4, 5],
+)
+
+# Log a biometric
+client.add_biometric("weight", 218.5, date.today())
 ```
 
 ## License

{cronometer_mcp-2.0.0 → cronometer_mcp-2.0.2}/README.md

@@ -2,7 +2,7 @@
 
 <!-- mcp-name: io.github.cphoskins/cronometer -->
 
-An [MCP (Model Context Protocol)](https://modelcontextprotocol.io/) server that provides access to your [Cronometer](https://cronometer.com/) nutrition data. Pull detailed food logs, daily macro/micro summaries, and raw CSV exports directly into Claude, Cursor, or any MCP-compatible client.
+An [MCP (Model Context Protocol)](https://modelcontextprotocol.io/) server that provides access to your [Cronometer](https://cronometer.com/) 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).
 
@@ -11,6 +11,11 @@ An [MCP (Model Context Protocol)](https://modelcontextprotocol.io/) server that
 - **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
 
@@ -84,31 +89,76 @@ If you installed from source with `pip install -e .`, you can also use the full
 
 ## 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 |
-| `get_food_details` | Get full nutrition info and measure IDs for a food |
+| `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 |
-| `get_macro_targets` | Get current daily macro targets (or weekly schedule with `target_date="all"`) |
+| `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:
+All date parameters use `YYYY-MM-DD` format. Most tools default to today or the last 7 days when dates are omitted.
 
-- `get_food_log(start_date?, end_date?)` — defaults to today
-- `get_daily_nutrition(start_date?, end_date?)` — defaults to last 7 days
-- `get_micronutrients(start_date?, end_date?)` — defaults to last 7 days
-- `export_raw_csv(export_type, start_date?, end_date?)` — type is one of: `servings`, `daily_summary`, `exercises`, `biometrics`, `notes`
-- `get_macro_targets(target_date?)` — defaults to today; pass `"all"` for weekly schedule
-- `set_macro_targets(protein_grams?, fat_grams?, carbs_grams?, calories?, target_date?, template_name?)` — reads current targets first, merges provided values
-- `sync_cronometer(start_date?, end_date?, days?, diet_label?)` — `days` defaults to 14; `diet_label` is optional text for the markdown header
+Key parameter patterns:
+- `diary_group` — one of `"Breakfast"`, `"Lunch"`, `"Dinner"`, `"Snacks"` (case-insensitive)
+- `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
 
@@ -134,6 +184,9 @@ Cronometer does not have a public API for individual users. This server uses the
 3. Calls GWT-RPC `authenticate` to get a user ID
 4. Calls GWT-RPC `generateAuthorizationToken` for short-lived export tokens
 5. Downloads CSV exports using the token
+6. 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
 
@@ -180,6 +233,22 @@ 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,       # Breakfast
+    days_of_week=[1, 2, 3, 4, 5],
+)
+
+# Log a biometric
+client.add_biometric("weight", 218.5, date.today())
 ```
 
 ## License

{cronometer_mcp-2.0.0 → cronometer_mcp-2.0.2}/cronometer_mcp/__init__.py

@@ -1,6 +1,6 @@
 """Cronometer MCP Server — nutrition data from Cronometer via MCP."""
 
-__version__ = "2.0.0"
+__version__ = "2.0.2"
 
 from .client import CronometerClient
 from .markdown import generate_food_log_md

{cronometer_mcp-2.0.0 → cronometer_mcp-2.0.2}/cronometer_mcp/client.py

@@ -2401,8 +2401,8 @@ class CronometerClient:
         if days_of_week is None:
             days_of_week = [0, 1, 2, 3, 4, 5, 6]
 
-        # Build day entries: "10|{day}|" for each day
-        day_entries = "".join(f"10|{d}|" for d in days_of_week)
+        # Build day entries: "10|{day}" for each day, joined by "|"
+        day_entries = "|".join(f"10|{d}" for d in days_of_week)
 
         # Format quantity
         qty_str = str(int(quantity)) if quantity == int(quantity) else str(quantity)

{cronometer_mcp-2.0.0 → cronometer_mcp-2.0.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "cronometer-mcp"
-version = "2.0.0"
+version = "2.0.2"
 description = "MCP server for Cronometer nutrition data — pull food logs, macros, and micronutrients via the Model Context Protocol"
 readme = "README.md"
 license = "MIT"

{cronometer_mcp-2.0.0 → cronometer_mcp-2.0.2}/server.json

@@ -1,17 +1,17 @@
 {
   "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.cphoskins/cronometer",
-  "description": "MCP server for Cronometer — food logs, macros, and micronutrient tracking",
+  "description": "MCP server for Cronometer — food logs, macros, fasting, biometrics, and recurring foods",
   "repository": {
     "url": "https://github.com/cphoskins/cronometer-mcp",
     "source": "github"
   },
-  "version": "2.0.0",
+  "version": "2.0.2",
   "packages": [
     {
       "registryType": "pypi",
       "identifier": "cronometer-mcp",
-      "version": "2.0.0",
+      "version": "2.0.2",
       "transport": {
         "type": "stdio"
       },