cronometer-api-mcp 0.1.3__tar.gz → 0.1.4__tar.gz

cronometer_api_mcp-0.1.4/.env.example

@@ -0,0 +1,2 @@
+CRONOMETER_USERNAME=
+CRONOMETER_PASSWORD=

{cronometer_api_mcp-0.1.3 → cronometer_api_mcp-0.1.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cronometer-api-mcp
-Version: 0.1.3
+Version: 0.1.4
 Summary: MCP server for Cronometer nutrition data using the mobile REST API
 Author: Randy
 License-Expression: MIT
@@ -15,6 +15,7 @@ Classifier: Topic :: Scientific/Engineering :: Medical Science Apps.
 Requires-Python: >=3.14
 Requires-Dist: httpx>=0.27.0
 Requires-Dist: mcp>=1.0.0
+Requires-Dist: python-dotenv>=1.0.0
 Requires-Dist: uvicorn>=0.30.0
 Description-Content-Type: text/markdown
 
@@ -97,7 +98,7 @@ export CRONOMETER_PASSWORD="your-password"
 
 | Tool | Description |
 |------|-------------|
-| `get_food_log` | Diary entries for a date with food names, amounts, and meal groups |
+| `get_food_log` | Diary entries for a date with food names, amounts, and meal groups, plus an energy_summary (target/consumed/remaining kcal) |
 | `get_daily_nutrition` | Daily macro and micronutrient totals |
 | `get_nutrition_scores` | Category scores (Vitamins, Minerals, etc.) with per-nutrient consumed amounts and confidence levels |
 
@@ -177,6 +178,18 @@ When deployed remotely with OAuth configured, connect from Claude.ai using:
 
 Claude.ai will open a browser tab for authorization. Click **Authorize** to complete the connection.
 
+## Development
+
+For local development, copy `.env.example` to `.env` and fill in your credentials:
+
+```bash
+cp .env.example .env
+# edit .env
+uv 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:

{cronometer_api_mcp-0.1.3 → cronometer_api_mcp-0.1.4}/README.md

@@ -77,7 +77,7 @@ export CRONOMETER_PASSWORD="your-password"
 
 | Tool | Description |
 |------|-------------|
-| `get_food_log` | Diary entries for a date with food names, amounts, and meal groups |
+| `get_food_log` | Diary entries for a date with food names, amounts, and meal groups, plus an energy_summary (target/consumed/remaining kcal) |
 | `get_daily_nutrition` | Daily macro and micronutrient totals |
 | `get_nutrition_scores` | Category scores (Vitamins, Minerals, etc.) with per-nutrient consumed amounts and confidence levels |
 
@@ -157,6 +157,18 @@ When deployed remotely with OAuth configured, connect from Claude.ai using:
 
 Claude.ai will open a browser tab for authorization. Click **Authorize** to complete the connection.
 
+## Development
+
+For local development, copy `.env.example` to `.env` and fill in your credentials:
+
+```bash
+cp .env.example .env
+# edit .env
+uv 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:

{cronometer_api_mcp-0.1.3 → cronometer_api_mcp-0.1.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "cronometer-api-mcp"
-version = "0.1.3"
+version = "0.1.4"
 description = "MCP server for Cronometer nutrition data using the mobile REST API"
 readme = "README.md"
 license = "MIT"
@@ -25,6 +25,7 @@ dependencies = [
     "mcp>=1.0.0",
     "httpx>=0.27.0",
     "uvicorn>=0.30.0",
+    "python-dotenv>=1.0.0",
 ]
 
 [project.scripts]

{cronometer_api_mcp-0.1.3 → cronometer_api_mcp-0.1.4}/server.json

@@ -6,12 +6,12 @@
     "url": "https://github.com/rwestergren/cronometer-api-mcp",
     "source": "github"
   },
-  "version": "0.1.3",
+  "version": "0.1.4",
   "packages": [
     {
       "registryType": "pypi",
       "identifier": "cronometer-api-mcp",
-      "version": "0.1.3",
+      "version": "0.1.4",
       "transport": {
         "type": "stdio"
       },

{cronometer_api_mcp-0.1.3 → cronometer_api_mcp-0.1.4}/src/cronometer_api_mcp/client.py

@@ -371,7 +371,10 @@ class CronometerClient:
 
         Args:
             food_id: Cronometer food ID.
-            measure_id: Measure/unit ID (from get_food). 0 for gram-based.
+            measure_id: Measure/unit ID. Get this from search_food() results
+                        (measureId field) or get_food() (defaultMeasureId or measures[].id).
+                        0 is only valid for user-created custom foods; database-sourced
+                        foods (CRDB/NCCDB/FDC) require a real measure ID.
             grams: Weight in grams.
             translation_id: Translation ID (from search results, usually 0).
             day: Date to log to. Defaults to today.

{cronometer_api_mcp-0.1.3 → cronometer_api_mcp-0.1.4}/src/cronometer_api_mcp/server.py

@@ -88,6 +88,18 @@ def get_food_log(date: str | None = None) -> str:
     Returns every food entry logged for the day, including food names,
     amounts, meal groups, and nutrient data.
 
+    Also returns a top-level energy_summary field with pre-computed
+    values most relevant to the user:
+
+      - total_target_kcal: daily calorie target dynamically adjusted
+        for expenditure and weight goal (equivalent to Cronometer's
+        "Total Target" in the Energy Summary screen)
+      - consumed_kcal: total calories consumed
+      - remaining_kcal: calories remaining to stay on target
+        (total_target_kcal - consumed_kcal). Always report this
+        when summarizing the user's day. Prefer this over manually
+        deriving values from the burn breakdown fields.
+
     Args:
         date: Date as YYYY-MM-DD (defaults to today).
     """
@@ -95,9 +107,22 @@ def get_food_log(date: str | None = None) -> str:
         client = _get_client()
         day = _parse_date(date)
         data = client.get_diary(day)
+
+        summary = (data or {}).get("summary") or {}
+        target = (summary.get("macros") or {}).get("energy")
+        consumed = (summary.get("consumed") or {}).get("total")
+        energy_summary: dict | None = None
+        if target is not None and consumed is not None:
+            energy_summary = {
+                "total_target_kcal": target,
+                "consumed_kcal": consumed,
+                "remaining_kcal": int(round(target - consumed)),
+            }
+
         return _ok(
             {
                 "date": date or str(date_module_today()),
+                "energy_summary": energy_summary,
                 "diary": data,
             }
         )
@@ -977,6 +1002,15 @@ class OAuthAuthorizationMiddleware:
 
 
 def main():
+    # Load .env for local development. No-op if the file is missing.
+    # override=False keeps real environment variables (Docker, systemd,
+    # MCP client `env` blocks, etc.) authoritative over .env.
+    from dotenv import find_dotenv, load_dotenv
+
+    dotenv_path = find_dotenv(usecwd=True)
+    if dotenv_path and load_dotenv(dotenv_path, override=False):
+        logger.info("Loaded .env from %s", dotenv_path)
+
     transport = os.getenv("MCP_TRANSPORT", "stdio")
 
     if transport == "stdio":

{cronometer_api_mcp-0.1.3 → cronometer_api_mcp-0.1.4}/uv.lock

@@ -102,6 +102,7 @@ source = { editable = "." }
 dependencies = [
     { name = "httpx" },
     { name = "mcp" },
+    { name = "python-dotenv" },
     { name = "uvicorn" },
 ]
 
@@ -114,6 +115,7 @@ dev = [
 requires-dist = [
     { name = "httpx", specifier = ">=0.27.0" },
     { name = "mcp", specifier = ">=1.0.0" },
+    { name = "python-dotenv", specifier = ">=1.0.0" },
     { name = "uvicorn", specifier = ">=0.30.0" },
 ]