# cronometer

Connect an agent to Cronometer food logs, nutrition summaries and diary controls. A paid Cronometer account with web login is required.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 26
- Author: cphoskins
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/cphoskins/cronometer-mcp
- Updated: 2026-10-03
- HTML: https://affpapa.org/en/nevibecode/mcp/cronometer

## What it does

The server lets an agent read food entries across a date range, daily calorie and macro totals, and vitamin and mineral details. It can search Cronometer’s food database, edit diary entries, copy a day, and manage foods scheduled to recur. Other tools cover fasting records, biometrics and data exports.

Set `CRONOMETER_USERNAME` and `CRONOMETER_PASSWORD` for account access. Cronometer Gold or another paid plan with web login is required. You can expose read tools only with `CRONOMETER_READ_ONLY=1`. The remote HTTP endpoint has no authentication, so anyone who can reach it could read or change the account held by the server.

For Claude Code, add the server with `claude mcp add` and run it through `uvx cronometer-mcp`. The second installation command also accepts `CRONOMETER_DATA_DIR`; both commands require the Cronometer login credentials.

## Requirements
- Needs: Python and uv (commands run via uvx)
- Environment variables: `CRONOMETER_USERNAME`, `CRONOMETER_PASSWORD`, `CRONOMETER_DATA_DIR` — keys and tokens: ask the human for the values, never commit them or put them in shared files.

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add --env CRONOMETER_USERNAME=<CRONOMETER_USERNAME> --env CRONOMETER_PASSWORD=<CRONOMETER_PASSWORD> --env CRONOMETER_DATA_DIR=<CRONOMETER_DATA_DIR> --transport stdio cronometer -- uvx cronometer-mcp
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from cronometer-mcp <command>

### Codex

**Platform CLI**
```bash
codex mcp add cronometer --env CRONOMETER_USERNAME=<CRONOMETER_USERNAME> --env CRONOMETER_PASSWORD=<CRONOMETER_PASSWORD> --env CRONOMETER_DATA_DIR=<CRONOMETER_DATA_DIR> -- uvx cronometer-mcp
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from cronometer-mcp <command>

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "cronometer": {
            "command": "uvx",
            "args": [
                "cronometer-mcp"
            ],
            "env": {
                "CRONOMETER_USERNAME": "<CRONOMETER_USERNAME>",
                "CRONOMETER_PASSWORD": "<CRONOMETER_PASSWORD>",
                "CRONOMETER_DATA_DIR": "<CRONOMETER_DATA_DIR>"
            }
        }
    }
}
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from cronometer-mcp <command>

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "cronometer": {
            "type": "stdio",
            "command": "uvx",
            "args": [
                "cronometer-mcp"
            ],
            "env": {
                "CRONOMETER_USERNAME": "<CRONOMETER_USERNAME>",
                "CRONOMETER_PASSWORD": "<CRONOMETER_PASSWORD>",
                "CRONOMETER_DATA_DIR": "<CRONOMETER_DATA_DIR>"
            }
        }
    }
}
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from cronometer-mcp <command>

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add -e CRONOMETER_USERNAME=<CRONOMETER_USERNAME> -e CRONOMETER_PASSWORD=<CRONOMETER_PASSWORD> -e CRONOMETER_DATA_DIR=<CRONOMETER_DATA_DIR> cronometer uvx cronometer-mcp
```
Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from cronometer-mcp <command>

## When to use it
- review calories and macros across selected dates
- find a food and check its nutrition details
- add or remove diary entries
- inspect fasting history and biometric records
- export Cronometer data as CSV

## Example prompts
- Show my Cronometer food entries and calorie totals for the selected dates.
- Find a food in Cronometer and add it to today's diary.
- Compare my daily protein, fat and carbohydrate totals across these dates.

## Similar
- [World Monitor](https://affpapa.org/en/nevibecode/mcp/world-monitor.md) — MCP server · ★ 89408
- [Scrapling MCP Server](https://affpapa.org/en/nevibecode/mcp/scrapling-mcp-server.md) — MCP server · ★ 89433
- [MCP Toolbox for Databases](https://affpapa.org/en/nevibecode/mcp/googleapis-mcp-toolbox-for-databases.md) — MCP server · ★ 16717
- [PostHog MCP Server](https://affpapa.org/en/nevibecode/mcp/posthog-mcp-server.md) — MCP server · ★ 40409
- [dbx](https://affpapa.org/en/nevibecode/mcp/dbx.md) — MCP server · ★ 27669
- [Metabase](https://affpapa.org/en/nevibecode/mcp/metabase.md) — MCP server · ★ 49845

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md