cronometer-mcp 2.2.0__tar.gz → 2.3.0__tar.gz

{cronometer_mcp-2.2.0 → cronometer_mcp-2.3.0}/.gitignore

@@ -24,5 +24,8 @@ venv/
 # Data (generated by sync)
 data/
 
+# Logs written by local MCP tooling
+logs/
+
 # GWT capture notes (contain session secrets)
 gwt-captures.md

cronometer_mcp-2.3.0/AGENTS.md

@@ -0,0 +1,13 @@
+# AGENTS.md
+
+Instructions for coding agents working in this repo.
+
+## Releasing
+
+- Always release with `./release.sh <version>`. Never bump `pyproject.toml`,
+  `cronometer_mcp/__init__.py` or `server.json` by hand, and never hand-roll the bump commit, tag
+  or push. The script checks for a clean tree and an unused tag, bumps all three files, commits,
+  tags `v<version>` and pushes `main` with tags.
+- Before running it: the working tree is clean and `python -m pytest` passes.
+- The tag alone does not publish. Create a GitHub release from the tag; that triggers
+  `.github/workflows/publish.yml`, which builds the package and publishes it to PyPI.

cronometer_mcp-2.3.0/CLAUDE.md

@@ -0,0 +1 @@
+@AGENTS.md

{cronometer_mcp-2.2.0 → cronometer_mcp-2.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: cronometer-mcp
-Version: 2.2.0
+Version: 2.3.0
 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
@@ -18,7 +18,7 @@ Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
 Classifier: Topic :: Scientific/Engineering :: Medical Science Apps.
 Requires-Python: >=3.11
-Requires-Dist: mcp<2.0.0,>=1.0.0
+Requires-Dist: mcp<3.0.0,>=2.3.0
 Requires-Dist: requests>=2.28.0
 Description-Content-Type: text/markdown
 
@@ -111,6 +111,17 @@ If you installed from source with `pip install -e .`, you can also use the full
 }
 ```
 
+### 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.
+
 ## Available Tools
 
 ### Food Log & Nutrition

{cronometer_mcp-2.2.0 → cronometer_mcp-2.3.0}/README.md

@@ -87,6 +87,17 @@ If you installed from source with `pip install -e .`, you can also use the full
 }
 ```
 
+### 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.
+
 ## Available Tools
 
 ### Food Log & Nutrition

{cronometer_mcp-2.2.0 → cronometer_mcp-2.3.0}/cronometer_mcp/__init__.py

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