MCP server for Cronometer — food logs, macros, and micronutrient tracking
If you already use Cronometer, the cronometer mcp server is the piece that lets your assistant work with it directly. MCP server for Cronometer — food logs, macros, and micronutrient tracking.
Or add them to a .env file in your project root (if your MCP client supports it).
cronometer-mcp on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Fasting — The Fasting tool exposed by this serverBiometrics — The Biometrics tool exposed by this serverSync — The Sync tool exposed by this serverConfiguration is passed through the environment: CRONOMETER_USERNAME, CRONOMETER_PASSWORD, CRONOMETER_DATA_DIR. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Cronometer's toolset — Fasting, Biometrics, Sync — is a fair guide to whether it matches your workflow. It is maintained by cphoskins; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Fasting | The Fasting tool exposed by this server. |
| Biometrics | The Biometrics tool exposed by this server. |
| Sync | The Sync tool exposed by this server. |
{
"mcpServers": {
"cronometer": {
"command": "uvx",
"args": ["cronometer-mcp"],
"env": {
"CRONOMETER_USERNAME": "your-value",
"CRONOMETER_PASSWORD": "your-value",
"CRONOMETER_DATA_DIR": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| CRONOMETER_USERNAME | Configuration value read at startup. | Optional |
| CRONOMETER_PASSWORD | Configuration value read at startup. | Optional |
| CRONOMETER_DATA_DIR | Filesystem location the server is allowed to use. | Optional |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.