Cronometer runs on your own machine — the client starts it, so there is no endpoint to ping. 1 431 installs a week from pypi. Last commit 1 Nov 2026.
MCP server for Cronometer — food logs, macros, fasting, biometrics, and recurring foods
What the code does
We read the source, 22 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
data = pickle.loads(self._cookie_path.read_bytes())
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add cronometer -e 'CRONOMETER_USERNAME=<CRONOMETER_USERNAME>' -e 'CRONOMETER_PASSWORD=<CRONOMETER_PASSWORD>' -- uvx cronometer-mcp{
"mcpServers": {
"cronometer": {
"command": "uvx",
"args": [
"cronometer-mcp"
],
"env": {
"CRONOMETER_PASSWORD": "<CRONOMETER_PASSWORD>",
"CRONOMETER_USERNAME": "<CRONOMETER_USERNAME>"
}
}
}
}[mcp_servers.cronometer]
command = "uvx"
args = ["cronometer-mcp"]
env = { CRONOMETER_USERNAME = "<CRONOMETER_USERNAME>", CRONOMETER_PASSWORD = "<CRONOMETER_PASSWORD>" }{
"mcpServers": {
"cronometer": {
"command": "uvx",
"args": [
"cronometer-mcp"
],
"env": {
"CRONOMETER_PASSWORD": "<CRONOMETER_PASSWORD>",
"CRONOMETER_USERNAME": "<CRONOMETER_USERNAME>"
}
}
}
}{
"servers": {
"cronometer": {
"type": "stdio",
"command": "uvx",
"args": [
"cronometer-mcp"
],
"env": {
"CRONOMETER_PASSWORD": "<CRONOMETER_PASSWORD>",
"CRONOMETER_USERNAME": "<CRONOMETER_USERNAME>"
}
}
}
}Put your own values in place of
<CRONOMETER_USERNAME> (Your Cronometer account email), <CRONOMETER_PASSWORD> (Your Cronometer account password).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
CRONOMETER_DATA_DIR (Directory for sync output (defaults to ~/.local/share/cronometer-mcp/)).
Alternatives to Cronometer
same job, measured the same wayMCP server for Cronometer nutrition tracking — food logs, diary, macros, fasting
MCP server for Dynatrace Managed to access logs, events, and metrics.
MCP server for managing Fly.io machines, apps, logs, and Docker images.
MCP server for Yandex Metrika API — counters, goals, reports, segments, logs
An MCP server for analyzing startup financial health and generating metrics reports locally.
Unofficial MCP server for the Polish Fitatu app. Search foods and manage meals, recipes, and logs.
Syslog receiver and MCP server for homelab log intelligence.
MCP server for petroleum engineering: LAS logs, decline curves, PVT, petrophysics, volumetrics.
Cronometer — questions
Answers built from our own checks of this server.